| 12.x |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
Approved w/Constraints
[12, 16, 20, 23, 25, 26, 27, 28, 29] |
| | | | [1] | Cisco Data Center Network Manager (DCNM) can be supported on Oracle Database or PostgreSQL. User must not use PostgreSQL to support Cisco DCNM.
It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
1. Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices both at rest and in motion.
2. Ensure that the user executes
command-line interface (CLI) load balancing at a scheduled downtime, otherwise, the existing network traffic will be adversely affected.
3. Cisco Data Center Network Manager (DCNM) system administrators need to work closely with system owners and the VA Network & Security Operation Center (NSOC) to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules should be established and tested during the development phase to prevent disruption to the network infrastructure environment.
4. The software should be included on the list of applications being continuously monitored for published vulnerabilities, updates and patches.
5. If Cisco Data Center Network Manager is used to satisfy a VA project requirement, a FedRAMP compliant cloud service provider (CSP) must be utilized. The FedRAMP approved impact level of the cloud service must be in compliance with VA requirements for the system being leveraged. If the cloud solution is used to satisfy a VA mission requirement, VA should clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreement (MOU/ISA) contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. Further, only CSPs that has been approved TIC 2.0 compliant may be used within VA. All traffic to and from the CSP must traverse the VA Trusted Internet Connection (TIC) gateway. TIC compliance is a shared responsibility between the CSP and VA. The CSP is required to provide an architecture that supports TIC while VA enforces TIC routing and compliance.
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 be properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and Federal Information Processing Standards (FIPS) 140-2. | | | [2] | 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. | | | [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 ISO can advise on the ESCCB review process. | | | [4] | 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. | | | [5] | It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
1. Users must ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices both at rest and in motion.
2. Users must ensure that the user executes
command-line interface (CLI) load balancing at a scheduled downtime, otherwise, the existing network traffic will be adversely affected.
3. Cisco Data Center Network Manager (DCNM) system administrators must work closely with system owners and the VA Network & Security Operation Center (NSOC) to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules must be established and tested during the development phase to prevent disruption to the network infrastructure environment.
4. The software must be included on the list of applications being continuously monitored for published vulnerabilities, updates and patches.
5. If Cisco Data Center Network Manager is used to satisfy a VA project requirement, a FedRAMP compliant cloud service provider (CSP) must be utilized. The FedRAMP approved impact level of the cloud service must be in compliance with VA requirements for the system being leveraged. If the cloud solution is used to satisfy a VA mission requirement, VA must clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreement (MOU/ISA) contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. Further, only CSPs that has been approved TIC 2.0 compliant may be used within VA. All traffic to and from the CSP must traverse the VA Trusted Internet Connection (TIC) gateway. TIC compliance is a shared responsibility between the CSP and VA. The CSP is required to provide an architecture that supports TIC while VA enforces TIC routing and compliance. | | | [6] | 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). | | | [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] | Per the Initial Product Review, users must abide by the following constraints:
Users must ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices both at rest and in motion if applicable.
Users must ensure that the user executes CLI load balancing at a scheduled downtime, otherwise, the existing network traffic will be adversely affected.
Cisco DCNM system administrators must work closely with system owners and the VA NSOC to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules should be established and tested during the development phase to prevent disruption to the network infrastructure environment.
The software must be included on the list of applications being continuously monitored for published vulnerabilities, updates and patches.
If Cisco Data Center Network Manager projects require internet connection, a FedRAMP compliant CSP must be utilized. The FedRAMP approved impact level of the cloud service must be in compliant with VA requirements for the system being leveraged. | | | [9] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [10] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Microsoft Internet Explorer (IE), Oracle Database, and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices both at rest and in motion if applicable.
- Ensure that the user executes CLI load balancing at a scheduled downtime, otherwise, the existing network traffic will be adversely affected.
- Cisco DCNM system administrators need to work closely with system owners and the VA NSOC to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules should be established and tested during the development phase to prevent disruption to the network infrastructure environment.
- The software should be included on the list of applications being continuously monitored for published vulnerabilities, updates and patches.
- If Cisco Data Center Network Manager projects require internet connection, a FedRAMP compliant CSP must be utilized. The FedRAMP approved impact level of the cloud service must be in compliant with VA requirements for the system being leveraged. 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 for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [12] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [13] | This technology must use the latest TRM approved version of a Java Environment.
Users must ensure that Microsoft Internet Explorer (IE), Oracle Database, and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices both at rest and in motion if applicable.
- Ensure that the user executes CLI load balancing at a scheduled downtime, otherwise, the existing network traffic will be adversely affected.
- Cisco DCNM system administrators need to work closely with system owners and the VA NSOC to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules should be established and tested during the development phase to prevent disruption to the network infrastructure environment.
- The software should be included on the list of applications being continuously monitored for published vulnerabilities, updates and patches.
- If Cisco Data Center Network Manager projects require internet connection, a FedRAMP compliant CSP must be utilized. The FedRAMP approved impact level of the cloud service must be in compliant with VA requirements for the system being leveraged. 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).
| | | [14] | 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. | | | [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] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL 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 PostgreSQL Database TRM entry for more details. | | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [18] | This technology must use the latest TRM approved version of a Java Environment.
Users must ensure that Google Chrome, Oracle Database, and PostgreSQL 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.
Per the Initial Product Review, users must abide by the following constraints:
- Cisco NDFC will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Cisco NDFC system administrators need to work closely with system owners and the VA CSOC to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules should be established and tested during the development phase to prevent disruption to the network infrastructure environment.
- If Cisco NDFC projects require internet connection, a FedRAMP compliant CSP must be utilized. 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.
| | | [19] | 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). | | | [20] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | | [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] | 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] | 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. | | | [24] | 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). | | | [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] | This technology must use the latest TRM approved version of a Java Environment.
Users must ensure that Google Chrome, Microsoft Edge, Oracle Database, and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Cisco NDFC will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Cisco NDFC system administrators need to work closely with system owners and the VA CSOC to ensure that the monitoring of network assets does not have an adverse effect on VA systems and network availability. In addition, monitoring rules should be established and tested during the development phase to prevent disruption to the network infrastructure environment.
- If Cisco NDFC projects require internet connection, a FedRAMP compliant CSP must be utilized. 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.
| | | [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). | | | [29] | 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. |
|
