Cisco Nexus Dashboard Fabric Controller

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Cisco Nexus Dashboard Fabric Controller , formerly Cisco Data Center Network Manager (DCNM), is software that offers network management system support for traditional or multiple-tenant local area network (LAN) and Storage Area Network (SAN) fabrics. It allows the user to provision, monitor, and troubleshoot the data center network infrastructure. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.2
Decision Date:	02/02/2024 at 03:13:44 UTC
Aliases:	DCNM
Introduced By:	TRM Request
Vendor Name:	Cisco Systems, Inc

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
4.x	08/07/2009	03/14/2015	03/31/2017
5.x	07/17/2011	03/14/2015	03/31/2017
6.x	04/15/2014	03/15/2017	03/31/2019
7.x	08/11/2014
10.x	10/31/2016
11.x	07/01/2018
12.x	10/19/2021

Current Decision Matrix (01/30/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2018

CY2019

CY2020

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

4.x

Unapproved

5.x

Unapproved

6.x

Unapproved

7.x

Divest
[1, 2, 4]

Divest
[2, 5, 6, 7]

Unapproved

10.x

Approved w/Constraints
[1, 2, 4]

Approved w/Constraints
[2, 5, 6, 7]

Unapproved

11.x

Unapproved

Approved w/Constraints
[2, 7, 9, 10, 11]

Approved w/Constraints
[2, 7, 10, 11, 12]

12.x

Unapproved

Decision Constraints


[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.

Note:

At the time of writing, version 12.1.3b is the most current version and released 09/11/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Systems Management Tools	Monitoring

Operating Systems Supported by the Technology

Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Java Runtime Environment (JRE) - Oracle
Microsoft Edge. - (required for some configurations)
Oracle Database - (required for some configurations)
PostgreSQL - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This is a well-documented technology.

Adoption Risks

This technology may transmit data over the VA Wide Area Network (WAN).
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Cisco NDFC can be implemented through any reputable Cloud Service Provider (CSP). Cisco NDFC is not listed as a Federal Risk and Authorization Management Program (FedRAMP) authorized, ready, or in-process product. Future implementation at VA would require a FedRAMP approved CSP from a select list.
Cisco NDFC is not Federal Information Processing standards (FIPS) 140-2 certified.
Use of this product may consume VA systems and enterprise network bandwidth resources due to the amount of traffic monitored in real time. This may lead to a Denial of Service (DoS) condition.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There are known Common Vulnerabilities and Exposures (CVEs) and VA Cyber Security Operations Center (CSOC) vulnerabilities. Please see https://nvd.nist.gov/vuln/search for more details.
This technology can integrate with and alter database technologies.
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.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/30/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/30/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES