| 14.x.x |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
Approved w/Constraints
[32, 34, 36, 37, 38, 39, 40] |
| | | | [1] | Product must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | | [2] | When hosted within VA, the system must be configured to use the FIPS 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest. In addition, the information system and its dependencies must go through the VA Assessment and Authorization (A&A) process to evaluate any associated risks and be granted an Authorization to Operate (ATO) as indicated. The use of externally hosted instances of this technology is not permitted without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or PII/PHI data are not compromised. Note that the use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. Due to several NIST security vulnerabilities, extra vigilance should be applied to ensure the product remains properly patched to mitigate known and future vulnerabilities. | | | [3] | 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.
| | | [4] | Product may only be used for Intranet applications. Use of this product to store PHI/PII/VA-sensitive information is not permitted due to the product`s dependency on MySQL. See the MySQL TRM entry for more information. | | | [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] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [7] | 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). | | | [8] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. 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 and ensure privacy of information compliance protections are in place. | | | [9] | 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. | | | [10] | Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of Vanderbilt University Research Electronic Data Capture (REDCap). It is advised that if this product is used within VA that the following constraints must be applied:
a. The system must be configured to use the The Federal Information Processing Standard (FIPS) 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
b. The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin their review.
c. The use of externally hosted instances of this technology is not permitted without ESCCB review and approval to ensure that confidential organization and/or PII/PHI data are not compromised.
d. Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | | [11] | 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. | | | [12] | Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of Vanderbilt University Research Electronic Data Capture (REDCap). It is advised that if this product is used within VA that the following constraints must be applied:
A. The system must be configured to use the The Federal Information Processing Standard (FIPS) 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
B. The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin their review.
C. The use of externally hosted instances of this technology is not permitted without ESCCB review and approval to ensure that confidential organization and/or PII/PHI data are not compromised.
D. Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | | [13] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | | [14] | 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). | | | [15] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | | [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, 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). | | | [18] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | | [19] | 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). | | | [20] | The system must be configured to use the Federal Information Processing Standard (FIPS) 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered. See the MySQL Database TRM entry for more details.
The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin a review.
The use of externally hosted instances of this technology is not permitted without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or Personally Identifiable Information (PII) or Protected Health information (PHI) data are not compromised.
Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [21] | 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. | | | [22] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered. See the MySQL Database TRM entry for more details
The system must be configured to use the FIPS 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin a review.
The use of externally hosted instances of this technology is not permitted without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or Personally Identifiable Information (PII) or Protected Health information (PHI) data are not compromised.
Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | | [23] | 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). | | | [24] | 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. | | | [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 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). | | | [26] | 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. | | | [27] | 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). | | | [28] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Internet Explorer (IE) and Microsoft Internet Information Services (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize My Structured Query Language (MySQL) Database - Community Editions as it is, at the time of writing, unapproved in the TRM.
Users must not utilize Maria Database (MariaDB) Server as it is, at the time of writing, unapproved in the TRM.
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
The system must be configured to use the FIPS 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin a review.
The use of externally hosted instances of this technology is not permitted without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or Personally Identifiable Information (PII) or Protected Health information (PHI) data are not compromised.
Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.
Per the Security Assessment Review, users must abide by the following constraints:
- REDCap will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- There are 18 pieces of information that are considered PHI identifiers. REDCap provides the means to identify the variables that contain PHI.
- When a new field is added in a project, make sure “Yes” is selected in the “Identifier?” property. Do this for all fields containing PHI. This way REDCap will know what data to limit to those who only have the clearance to see de-identified data.
- Set up User Rights to control who has access to PHI. The “User Rights” module is where who has access to what data is defined. Users permissions can be set to include either a full data set or a de-identified data set. Users can also be granted or denied access to specific instruments in a project. If a project contains PHI, it is imperative to limit who has access to that information in the project.
- MySQL is approved with restrictive constraints. Use of MySQL to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. It is strongly advised that only VA approved, hardened database applications be used with REDCap.
- 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.
| | | [29] | 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). | | | [30] | 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). | | | [31] | Users must ensure that Microsoft Internet Information Services (IIS) and Apache Hypertext Transfer Protocol (HTTP) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Maria Database (MariaDB) Server as it is, at the time of writing, unapproved in the TRM.
The system must be configured to use the FIPS 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin a review.
The use of externally hosted instances of this technology is not permitted without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or Personally Identifiable Information (PII) or Protected Health information (PHI) data are not compromised.
Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.
Per the Initial Product Review, users must abide by the following constraints:
- REDCap will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- There are 18 pieces of information that are considered PHI identifiers. REDCap provides the means to identify the variables that contain PHI.
- When a new field is added in a project, make sure “Yes” is selected in the “Identifier?” property. Do this for all fields containing PHI. This way REDCap will know what data to limit to those who only have the clearance to see de-identified data.
- Set up User Rights to control who has access to PHI. The “User Rights” module is where who has access to what data is defined. Users permissions can be set to include either a full data set or a de-identified data set. Users can also be granted or denied access to specific instruments in a project. If a project contains PHI, it is imperative to limit who has access to that information in the project.
- MySQL is approved with restrictive constraints. Use of MySQL to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. It is strongly advised that only VA approved, hardened database applications be used with REDCap.
- 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.
| | | [32] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details. | | | [33] | 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. | | | [34] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | | [35] | 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). | | | [36] | 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. | | | [37] | Users must ensure that My Structured Query Language Database - Commercial Editions, Microsoft Internet Information Services (IIS) and Apache Hypertext Transfer Protocol (HTTP) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Maria Database (MariaDB) Server as it is, at the time of writing, unapproved in the TRM.
The system must be configured to use the FIPS 140-2 encryption available in the underlying infrastructure to protect sensitive data at rest.
The information system and all of its dependencies must go through the VA Assessment and Authorization (A&A) process; it requires an official management decision, given by a senior agency official, to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls. The result of a successful A&A is an Authorization to Operate (ATO). This is required before the Enterprise Security Change Control Board (ESCCB) can begin a review.
The use of externally hosted instances of this technology is not permitted without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or Personally Identifiable Information (PII) or Protected Health information (PHI) data are not compromised.
Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.
Per the Initial Product Review, users must abide by the following constraints:
- REDCap will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- There are 18 pieces of information that are considered PHI identifiers. REDCap provides the means to identify the variables that contain PHI.
- When a new field is added in a project, make sure “Yes” is selected in the “Identifier?” property. Do this for all fields containing PHI. This way REDCap will know what data to limit to those who only have the clearance to see de-identified data.
- Set up User Rights to control who has access to PHI. The “User Rights” module is where who has access to what data is defined. Users permissions can be set to include either a full data set or a de-identified data set. Users can also be granted or denied access to specific instruments in a project. If a project contains PHI, it is imperative to limit who has access to that information in the project.
- Only TRM approved Commercial Edition of mySQL should be used and mySQL must be configured following the baseline configuration (Baseline).
- 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.
Systems owners and Administrators should ensure the latest approved version of this product is installed and must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
| | | [38] | 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. | | | [39] | 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. | | | [40] | 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). |
|
