National Information Assurance Partnership
Common Criteria Evaluation and Validation Scheme
Validation Report
Cisco Secure Network Analytics (SNA) 7.4
Report Number: CCEVS-VR-VID11313-2023
Dated: February 22, 2023
Version: 1.0
National Institute of Standards and Technology Department of Defense
Information Technology Laboratory ATTN: NIAP, Suite 6982
100 Bureau Drive 9800 Savage Road
Gaithersburg, MD 20899 Fort Meade, MD 20755-6982
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
ii
ACKNOWLEDGEMENTS
Validation Team
Daniel Faigin
Viet Hung Le
Patrick Mallett, PhD
Marybeth Panock
Mike Quintos
The Aerospace Corporation
Common Criteria Testing Laboratory
Cody Cummins
Kevin Cummins
Katie Sykes
Gossamer Security Solutions, Inc.
Columbia, MD
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
iii
Table of Contents
1 Executive Summary.................................................................................................... 1
2 Identification............................................................................................................... 1
3 Architectural Information ........................................................................................... 2
3.1 TOE Evaluated Platforms ................................................................................... 3
3.2 TOE Architecture................................................................................................ 3
3.3 Physical Boundaries............................................................................................ 4
4 Security Policy............................................................................................................ 4
4.1 Security audit ...................................................................................................... 4
4.2 Communication................................................................................................... 4
4.3 Cryptographic support ........................................................................................ 5
4.4 Identification and authentication......................................................................... 5
4.5 Security management.......................................................................................... 6
4.6 Protection of the TSF.......................................................................................... 6
4.7 TOE access.......................................................................................................... 6
4.8 Trusted path/channels ......................................................................................... 7
5 Assumptions & Clarification of Scope ....................................................................... 7
6 Documentation............................................................................................................ 8
7 IT Product Testing ...................................................................................................... 9
7.1 Developer Testing............................................................................................... 9
7.2 Evaluation Team Independent Testing ............................................................... 9
8 Evaluated Configuration ............................................................................................. 9
9 Results of the Evaluation .......................................................................................... 10
9.1 Evaluation of the Security Target (ASE).......................................................... 10
9.2 Evaluation of the Development (ADV)............................................................ 11
9.3 Evaluation of the Guidance Documents (AGD) ............................................... 11
9.4 Evaluation of the Life Cycle Support Activities (ALC)................................... 11
9.5 Evaluation of the Test Documentation and the Test Activity (ATE) ............... 11
9.6 Vulnerability Assessment Activity (VAN)....................................................... 12
9.7 Summary of Evaluation Results........................................................................ 12
10 Validator Comments/Recommendations .................................................................. 12
11 Annexes..................................................................................................................... 12
12 Security Target.......................................................................................................... 13
13 Glossary .................................................................................................................... 13
14 Bibliography ............................................................................................................. 13
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
1
1 Executive Summary
This report documents the assessment of the National Information Assurance Partnership
(NIAP) validation team of the evaluation of Cisco Secure Network Analytics (SNA) solution
provided by Cisco Systems, Inc. It presents the evaluation results, their justifications, and the
conformance results. This Validation Report is not an endorsement of the Target of
Evaluation by any agency of the U.S. government, and no warranty is either expressed or
implied.
The evaluation was performed by the Gossamer Security Solutions (Gossamer) Common
Criteria Testing Laboratory (CCTL) in Columbia, MD, United States of America, and was
completed in February 2023. The information in this report is largely derived from the
Evaluation Technical Report (ETR) and associated test reports, all written by Gossamer
Security Solutions. The evaluation determined that the product is both Common Criteria Part
2 Extended and Part 3 Conformant and meets the assurance requirements of the collaborative
Protection Profile for Network Devices, version 2.2e, 23 March 2020.
The Target of Evaluation (TOE) is the Cisco Secure Network Analytics (SNA) 7.4.
The TOE identified in this Validation Report has been evaluated at a NIAP approved
Common Criteria Testing Laboratory using the Common Methodology for IT Security
Evaluation (Version 3.1, Rev 5) for conformance to the Common Criteria for IT Security
Evaluation (Version 3.1, Rev 5). This Validation Report applies only to the specific version
of the TOE as evaluated. The evaluation has been conducted in accordance with the
provisions of the NIAP Common Criteria Evaluation and Validation Scheme and the
conclusions of the testing laboratory in the evaluation technical report are consistent with the
evidence provided.
The validation team monitored the activities of the evaluation team, provided guidance on
technical issues and evaluation processes, and reviewed the individual work units and
successive versions of the ETR. The validation team found that the evaluation showed that
the product satisfies all of the functional requirements and assurance requirements stated in
the Security Target (ST). Therefore, the validation team concludes that the testing
laboratory’s findings are accurate, the conclusions justified, and the conformance results are
correct. The conclusions of the testing laboratory in the evaluation technical report are
consistent with the evidence produced.
The technical information included in this report was obtained from the Cisco Secure
Network Analytics (SNA) 7.4 Security Target, Version 1.2, February 20, 2023, and analysis
performed by the Validation Team.
2 Identification
The CCEVS is a joint National Security Agency (NSA) and National Institute of Standards
and Technology (NIST) effort to establish commercial facilities to perform trusted product
evaluations. Under this program, security evaluations are conducted by commercial testing
laboratories called Common Criteria Testing Laboratories (CCTLs) using the Common
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
2
Evaluation Methodology (CEM) in accordance with National Voluntary Laboratory
Assessment Program (NVLAP) accreditation.
The NIAP Validation Body assigns Validators to monitor the CCTLs to ensure quality and
consistency across evaluations. Developers of information technology products desiring a
security evaluation contract with a CCTL and pay a fee for their product’s evaluation. Upon
successful completion of the evaluation, the product is added to NIAP’s Validated Products
List.
Table 1 provides information needed to completely identify the product, including:
• The Target of Evaluation (TOE): the fully qualified identifier of the product as evaluated.
• The Security Target (ST), describing the security features, claims, and assurances of the
product.
• The conformance result of the evaluation.
• The Protection Profile to which the product is conformant.
• The organizations and individuals participating in the evaluation.
Table 1: Evaluation Identifiers
Item Identifier
Evaluation Scheme United States NIAP Common Criteria Evaluation and Validation Scheme
TOE Cisco Secure Network Analytics (SNA) 7.4
(Specific models identified in Section 8)
Protection Profile collaborative Protection Profile for Network Devices, version 2.2e, 23 March
2020
ST Cisco Secure Network Analytics (SNA) 7.4 Security Target, Version 1.2,
February 20, 2023
Evaluation Technical
Report
Evaluation Technical Report for Cisco Secure Network Analytics (SNA) 7.4,
version 1.0, February 21, 2023
CC Version Common Criteria for Information Technology Security Evaluation, Version 3.1,
rev 5
Conformance Result CC Part 2 extended, CC Part 3 extended
Sponsor Cisco Systems, Inc.
Developer Cisco Systems, Inc.
Common Criteria
Testing Lab (CCTL)
Gossamer Security Solutions, Inc.
Columbia, MD
CCEVS Validators Daniel Fagin, Viet Hung Le, Marybeth Panock, Patrick Mallett, Mike Quintos
3 Architectural Information
Note: The following architectural description is based on the description presented in the
Security Target.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
3
The Cisco Secure Network Analytics (SNA) TOE is a centrally managed system of
distributed components for collection, storage, analysis, of network telemetry data. The
evaluated configurations of the TOE consist of one SNA Management Console (SMC), one
or more Flow Collectors (FC), one or more Flow Sensors (FS), and one or more UDP
Directors (UDPD). Each of the TOE components is available as a stand-alone physical
appliance, or as a virtual appliance. The physical and virtual appliances provide equivalent
functionality, and a mixture of physical and virtual appliances can be deployed together.
3.1 TOE Evaluated Platforms
Detail regarding the evaluated configuration is provided in Section 8 below.
3.2 TOE Architecture
The TOE is a system comprised of four appliance types (SMC, FC, FS, and UDPD) described
below, each of which is comprised of both software and hardware. The software on each
appliance type is a proprietary build of Linux with Cisco SNA applications, where each
appliance type (SMC, FC, FS, and UDPD) contains its own set of applications specific to its
unique functionality. The hardware of each appliance (physical and virtual) is a Cisco UCS
server platform. The software running on each type of SNA appliance is software image
Release 7.4.
The Cisco Secure Network Analytics components that comprise the TOE have common
hardware characteristics. Any hardware differences, e.g., the amount of RAM or drive space,
of the number of network interfaces, affect only non-TSF relevant functionality such as
throughput and amount of storage, and therefore support security equivalency of the TOE
component models.
This TOE is considered a ‘distributed’ TOE as defined in NDcPP in that this TOE requires
multiple distinct TOE components to operate as a logical whole in order to fulfil the
requirements of NDcPP, and those TOE components are separated (distributed) across a
network. This TOE includes one management component (SMC), and three types of
managed network devices (FC, FS, and UDPD). In a distributed TOE not all requirements
need to be enforced by each TOE component.
The SNA Management Console (SMC) provides the administrative interface to manage all
TOE components. The SMC aggregates, organizes, and presents analysis from up to 25 Flow
Collectors, the Cisco Identity Services Engine, and other sources. It provides a graphical
representations of network traffic, identity information, customized summary reports, and
integrated security and network intelligence for comprehensive analysis.
The SNA Flow Collector (FC) receives telemetry data from SNA Flow Sensors and other
sources such as routers, switches, firewalls, and endpoint agents. The FC stores collected
data in its internal database, analyses the data, sends event notifications to SMC, and supports
further forensics and long-term data analysis via customized reporting provided by the SMC.
Multiple Flow Collectors may be managed by a single SMC and are available as hardware
appliances or as virtual machines.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
4
The Flow Sensor (FS) produces telemetry for segments of the switching and routing
infrastructure that can’t generate NetFlow natively. The Flow Sensors connect directly to a
mirroring port or network tap to monitor network traffic and generate telemetry data.
Multiple Flow Sensors can be managed by a single SMC and are available as hardware
appliances or as virtual appliances to monitor virtual machine environments.
The UDP Director (UDPD) simplifies the collection and distribution of network and security
data across the enterprise. It helps reduce the processing power on network routers and
switches by receiving essential network and security information from multiple locations and
then forwarding it to a single data stream to one or more destinations. Multiple UDP
Directors can be managed by a single SMC and are available as hardware appliances or as
virtual appliances to monitor virtual machine environments.
3.3 Physical Boundaries
The TOE is a hardware and software solution composed of four major components: SMC,
FC, FS, and UDPD. The network, on which they reside, is considered part of the
environment.
4 Security Policy
This section summaries the security functionality of the TOE:
1. Security audit
2. Communication
3. Cryptographic support
4. Identification and authentication
5. Security management
6. Protection of the TSF
7. TOE access
8. Trusted path/channels
4.1 Security audit
The Cisco Secure Network Analytics provides extensive auditing capabilities. The TOE can
audit events related to cryptographic functionality, identification and authentication, and
administrative actions. The Cisco Secure Network Analytics generates an audit record for
each auditable event. Each security relevant audit event has the date, timestamp, event
description, and subject identity. The administrator configures auditable events, configures
secure transmission of audit records to a remote audit server, and manages audit data storage.
The TOE provides the administrator with a local circular audit trail. Audit messages are
stored locally and transmitted over an encrypted channel to an external audit server.
4.2 Communication
The TOE allows authorized administrators to control which SNA appliance (FC, FS, and
UDPD) is managed by the SMC. This is performed through a registration process over TLS.
The administrator can also de-register an appliance if he or she wishes to no longer manage
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
5
it through the SMC. For this TOE the process of registration/joining a new managed
appliance (FC, FS, UDPD) to the SMC is manually initiated by the administrator installing
each appliance. The initial TLS connection is authenticated to the SMC using the SMC
administrator’s username/password, at which point the appliances exchange their X.509
certificates, and from that point forward all TLS communications among appliances are
authenticated using X.509 certificates.
4.3 Cryptographic support
The TOE provides cryptography in support of other Cisco SNA security functionality. This
cryptography has been validated by the NIST CAVP.
The TOE provides cryptography in support for TLS, which is used for remote administrative
management, and secure communication among TOE components, and connects from the
TOE to LDAP and syslog servers. The cryptographic services provided by the TOE are
described below.
Cryptographic Method Use within the TOE
AES Used to encrypt TLS session traffic.
ECDH Used to provide key exchange in TLS.
RSA Signature Services
X.509 certificate signing and verification.
Data signing and verification in TLS.
HMAC
Used for keyed hash, integrity services in TLS session
establishment.
DRBG
Used for random number generation
Used in TLS session establishment.
SHA Used to provide TLS traffic integrity verification
Transport Layer Security (TLS) Used in TLS session establishment.
During initial installation each TOE component generates its own unique self-signed
X.509v3 certificate, and during initial configuration all those certificates are replaced with
new CA-signed identity certificates which are then used for all TLS connections including
mutual authentication of TLS connections among TOE components. Each TOE component
generates its own unique keypair and its own certificate signing requests (CSR), and imports
TLS certificates that have been signed by an external CA server.
4.4 Identification and authentication
TOE components perform two types of authentication: password-based authentication of
administrators for remote administration of the TOE; and certificate-based authentication of
devices. Device-level authentication allows TOE components to establish secure channels
with other TOE components, and with external servers (LDAP and syslog).
The TOE provides administrator authentication against a local user database. Password-
based authentication can be performed on the serial console, and the GUI (accessible via
HTTPS/TLS). For authentication to the GUI, the TOE optionally supports use of a AAA
server (using LDAP over TLS), which would be outside the TOE boundary.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
6
The TOE requires Authorized Administrators to authenticate prior to being granted access to
any of the management functionality. The TOE can be configured to require a minimum
password length of 15 characters.
After a configurable number of incorrect login attempts at administrative interfaces where
authentication is processed locally (i.e. where LDAP is not used), the TOE will lock the
offending account until an Administrator defined time period has elapsed.
4.5 Security management
The TOE provides secure administrative services for management of general TOE
configuration and the security functionality provided by the TOE. All TOE administration
occurs either through a secure HTTPS/TLS session or via a local console connection. The
TOE provides the ability to securely manage all TOE administrative users; all identification
and authentication; all audit functionality of the TOE; all TOE cryptographic functionality;
the timestamps maintained by the TOE; and updates to the TOE.
When an administrative session is initially established, the TOE displays an administrator-
configurable warning banner. This is used to provide any information deemed necessary by
the administrator. After a set amount of time of inactivity, the administrator will be locked
out of the administrator interface.
4.6 Protection of the TSF
The TOE protects against interference and tampering by untrusted subjects by implementing
identification, authentication, and access controls to limit configuration to Authorized
Administrators. The TOE prevents reading of plaintext cryptographic keys and passwords.
The TOE internally maintains the date and time. This date and time is used as the timestamp
that is applied to audit records generated by the TOE. Administrators can update the TOE’s
clock manually.
The TOE is able to verify any software updates prior to the software updates being installed
on the TOE to avoid the installation of unauthorized software. The TOE performs self-
testing to verify correct operation of its cryptographic module. The TOE components are
not general-purpose operating systems; root access is not permitted, external software
applications cannot be installed, and access to memory space is restricted to TOE functions.
The TOE is distributed, including multiple appliances that communicate with each other over
a network. These internal TOE communications between TOE components are protected
within TLS and authenticated using X.509 certificates.
4.7 TOE access
The TOE can terminate inactive sessions after an Authorized Administrator configurable
time-period. Once a session has been terminated the TOE requires the user to re-authenticate
to establish a new session.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
7
The TOE can also display an Authorized Administrator specified banner on the CLI
management interface and the WebUI prior to allowing any administrative access to the
TOE.
4.8 Trusted path/channels
The TOE establishes a trusted path with syslog servers using TLS, and with LDAP servers
using TLS. Remote administration of the TOE uses TLS/HTTPS. All communications
between TOE components are protected within TLS; the initial joining of TOE components
is authenticated using a username and password that’s manually entered during the joining
process, and subsequent communications between TOE components are automatically
authenticated using X.509 certificates.
5 Assumptions & Clarification of Scope
Assumptions
The Security Problem Definition, including the assumptions, may be found in the following
documents:
• collaborative Protection Profile for Network Devices, version 2.2e, 23 March 2020
That information has not been reproduced here and the NDcPP22e should be consulted if
there is interest in that material.
The scope of this evaluation was limited to the functionality and assurances covered in the
NDcPP22e as described for this TOE in the Security Target. Other functionality included in
the product was not assessed as part of this evaluation. All other functionality provided by
the devices needs to be assessed separately, and no further conclusions can be drawn about
their effectiveness.
Clarification of scope
All evaluations (and all products) have limitations, as well as potential misconceptions that
need clarification. This text covers some of the more important limitations and clarifications
of this evaluation. Note that:
• As with any evaluation, this evaluation only shows that the evaluated configuration
meets the security claims made with a certain level of assurance (the assurance
activities specified in the collaborative Protection Profile for Network Devices and
performed by the evaluation team).
• This evaluation covers only the specific device models and software as identified in
this document, and not any earlier or later versions released or in process.
• Apart from the Admin Guide, additional customer documentation for the specific
Network Device models was not included in the scope of the evaluation and therefore
should not to be relied upon when configuring or operating the device as evaluated.
• This evaluation did not specifically search for, nor attempt to exploit, vulnerabilities
that were not “obvious” or vulnerabilities to objectives not claimed in the ST. The
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
8
CEM defines an “obvious” vulnerability as one that is easily exploited with a
minimum of understanding of the TOE, technical sophistication and resources.
• The functionality evaluated is scoped exclusively to the security functional
requirements specified in the NDcPP22e and applicable Technical Decisions. Any
additional security related functional capabilities of the TOE were not covered by this
evaluation.
The following Table list the functionality that is excluded from the evaluation. The exclusion
of this functionality does not affect compliance to the collaborative Protection Profile for
Network Devices (NDcPP).
Excluded Functionality
Excluded Functionality Exclusion Rationale
Non-FIPS 140-2 mode of operation This mode of operation includes non-FIPS allowed operations.
SNMP This feature is disabled by default and cannot be configured for
use in the evaluated configuration. Including this feature would
not meet the security policies as defined in the Security Target.
RADIUS and TACACS+ LDAP over TLS can be used instead of RADIUS and TACACS+,
which cannot be secured in TLS.
6 Documentation
The following documents were available with the TOE for evaluation:
• Cisco Secure Network Analytics (SNA) 7.4 Preparative Procedures & Operational
User Guide for the Common Criteria Certified Configuration, Version 1.1, February
16, 2023.
• Cisco Secure Network Analytics Data Sheet, August 5, 2021
• Cisco Secure Network Analytics Release Notes 7.4.0, Version 3.2
• Cisco Secure Network Analytics Smart Software Licensing Guide 7.4, Version 1.1
• Cisco Stealthwatch x210 Series Hardware Installation Guide, Version 2.0
• Cisco Secure Network Analytics Virtual Edition Appliance Installation Guide 7.4.1,
Version 2.2
• Cisco Secure Network Analytics Update Guide 7.4.1, Version 1.2
• Cisco Secure Network Analytics System Configuration Guide 7.4.1, Version 1.3
Any additional customer documentation provided with the product, or that is available
online was not included in the scope of the evaluation and therefore should not be relied
upon when configuring or operating the device as evaluated.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
9
To use the product in the evaluated configuration, the product must be configured as
specified in the Guidance Documentation listed above. Consumers are encouraged to
download the configuration guides from the NIAP website to ensure the device is
configured as evaluated.
7 IT Product Testing
This section describes the testing efforts of the developer and the Evaluation Team. It is
derived from information contained in the proprietary Detailed Test Report for Cisco Secure
Network Analytics (SNA), Version 1.1, February 20, 2023 (DTR), as summarized in the
evaluation Assurance Activity Report (AAR).
7.1 Developer Testing
No evidence of developer testing is required in the assurance activities for this product.
7.2 Evaluation Team Independent Testing
The evaluation team verified the product according to a Common Criteria Certification
document and ran the tests specified in the NDcPP22e including the tests associated with
optional requirements. The AAR, in sections 1.1 lists the tested devices, provides a list of
test tools, and has diagrams of the test environment.
8 Evaluated Configuration
The evaluated configuration consists of the physical devices as specified in the table below
and includes the Cisco SNA 7.4 software when configured in accordance with the
documentation specified in Section 6.
SNA Appliance Type Part Number Server platform
Entropy
Source
SNA appliances on UCS C-Series M5 servers
SNA Management Console
ST-SMC2210-K9
L-ST-SMC-VE-
K9
UCSC-C220-
M5SX
Intel®
Skylake
Scalable
Processor
SNA UDP Director
ST-UDP2210-K9
L-ST-UDP-VE-
K9
SNA Flow Sensor
ST-FS1210-K9
ST-FS3210-K9
ST-FS4210-K9
ST-FS4240-k9
L-ST-FS-VE-K9
SNA Flow Collector
ST-FC4210-K9
L-ST-FC-VE-K9
SNA Flow Collector Engine ST-FC5210E
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
10
SNA Flow Collector
Database
ST-FC5210D
UCSC-C240-
M5SX
SNA appliances on UCS C-Series M4 servers
SNA Management Console
ST-SMC2200-K9
L-ST-SMC-VE-
K9
UCSC-C220-M4S
Intel®
Xeon®
E5-26XX
SNA UDP Director
ST-UDP2200-K9
L-ST-UDP-VE-
K9
SNA Flow Sensor
ST-FS1200-K9
ST-FS2200-K9
ST-FS3200-K9
ST-FS4200-K9
L-ST-FS-VE-K9
SNA Flow Collector
ST-FC4200-K9, or
L-ST-FC-VE-K9
SNA Flow Collector Engine ST-FC5200E
SNA Flow Collector
Database
ST-FC5200D
UCSC-C240-
M4S2
9 Results of the Evaluation
The results of the assurance requirements are generally described in this section and are
presented in detail in the proprietary ETR. The reader of this document can assume that all
assurance activities and work units received a passing verdict.
A verdict for an assurance component is determined by the resulting verdicts assigned to the
corresponding evaluator action elements. The evaluation was conducted based upon CC
version 3.1 rev 5 and CEM version 3.1 rev 5. The evaluation determined the Secure Network
Analytics (SNA) TOE to be Part 2 extended, and to meet the SARs contained in the
NDcPP22e.
9.1 Evaluation of the Security Target (ASE)
The evaluation team applied each ASE CEM work unit. The ST evaluation ensured the ST
contains a description of the environment in terms of policies and assumptions, a statement
of security requirements claimed to be met by the Cisco Secure Network Analytics (SNA)
7.4 products that are consistent with the Common Criteria, and product security function
descriptions that support the requirements.
The validator reviewed the work of the evaluation team and found that sufficient evidence
and justification was provided by the evaluation team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the evaluation team was justified.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
11
9.2 Evaluation of the Development (ADV)
The evaluation team applied each ADV CEM work unit. The evaluation team assessed the
design documentation and found it adequate to aid in understanding how the TSF provides
the security functions. The design documentation consists of a functional specification
contained in the Security Target and Guidance documents. Additionally, the evaluator
performed the assurance activities specified in the NDcPP22e related to the examination of
the information contained in the TSS.
The validator reviewed the work of the evaluation team and found that sufficient evidence
and justification was provided by the evaluation team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the evaluation team was justified.
9.3 Evaluation of the Guidance Documents (AGD)
The evaluation team applied each AGD CEM work unit. The evaluation team ensured the
adequacy of the user guidance in describing how to use the operational TOE. Additionally,
the evaluation team ensured the adequacy of the administrator guidance in describing how
to securely administer the TOE. All of the guides were assessed during the design and testing
phases of the evaluation to ensure they were complete.
The validator reviewed the work of the evaluation team and found that sufficient evidence
and justification was provided by the evaluation team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the evaluation team was justified.
9.4 Evaluation of the Life Cycle Support Activities (ALC)
The evaluation team applied each ALC CEM work unit. The evaluation team found that the
TOE was identified.
The validator reviewed the work of the evaluation team and found that sufficient evidence
and justification was provided by the evaluation team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the evaluation team was justified.
9.5 Evaluation of the Test Documentation and the Test Activity (ATE)
The evaluation team applied each ATE CEM work unit. The evaluation team ran the set of
tests specified by the assurance activities in the NDcPP22e and recorded the results in a Test
Report, summarized in Section 3.4 of the AAR.
The validator reviewed the work of the evaluation team and found that sufficient evidence
and justification was provided by the evaluation team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the evaluation team was justified.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
12
9.6 Vulnerability Assessment Activity (VAN)
The evaluation team applied each AVA CEM work unit. The vulnerability analysis is in the
Detailed Test Report (DTR) prepared by the evaluator. The vulnerability analysis includes
a public search for vulnerabilities. The public search for vulnerabilities did not uncover any
residual vulnerability.
The evaluator searched the National Vulnerability Database
(https://web.nvd.nist.gov/view/vuln/search) and Vulnerability Notes Database
(http://www.kb.cert.org/vuls/) on 2/16/2023 with the following search terms: "Cisco",
"Cisco Secure Network Analytics", "SNA 7.4", "Cisco SSL FOM", "SNA Management
Console", "SNA Flow Collector", "SNA Flow Sensor", "SNA UDP Director", "ESXi",
"Intel Xeon Scalable Processor", "Intel Xeon E5", "Intel Xeon Gold", "Intel Xeon Bronze".
The validator reviewed the work of the evaluation team and found that sufficient evidence
and justification was provided by the evaluation team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the evaluation team was justified.
9.7 Summary of Evaluation Results
The evaluation team’s assessment of the evaluation evidence demonstrates that the claims in
the ST are met. Additionally, the evaluation team’s testing also demonstrated the accuracy
of the claims in the ST.
The validation team’s assessment of the evidence provided by the evaluation team is that it
demonstrates that the evaluation team followed the procedures defined in the CEM, and
correctly verified that the product meets the claims in the ST.
10 Validator Comments/Recommendations
The validation team notes that the evaluated configuration is dependent upon the TOE being
configured per the evaluated configuration instructions in the Administrator Guide document
listed in Section 6. No versions of the TOE and software, either earlier or later were
evaluated. Please note that the functionality evaluated is scoped exclusively to the security
functional requirements specified in the Security Target. Other functionality included in the
product was not assessed as part of this evaluation. Other functionality provided by devices
in the operational environment, such as the syslog server, need to be assessed separately and
no further conclusions can be drawn about their effectiveness.
11 Annexes
Not applicable
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
13
12 Security Target
The Security Target is identified as: Cisco Secure Network Analytics (SNA) 7.4 Security
Target, Version 1.2, February 20, 2023.
13 Glossary
The following definitions are used throughout this document:
• Common Criteria Testing Laboratory (CCTL). An IT security evaluation facility
accredited by the National Voluntary Laboratory Accreditation Program (NVLAP) and
approved by the CCEVS Validation Body to conduct Common Criteria-based
evaluations.
• Conformance. The ability to demonstrate in an unambiguous way that a given
implementation is correct with respect to the formal model.
• Evaluation. The assessment of an IT product against the Common Criteria using the
Common Criteria Evaluation Methodology to determine whether or not the claims made
are justified; or the assessment of a protection profile against the Common Criteria using
the Common Evaluation Methodology to determine if the Profile is complete, consistent,
technically sound and hence suitable for use as a statement of requirements for one or
more TOEs that may be evaluated.
• Evaluation Evidence. Any tangible resource (information) required from the sponsor or
developer by the evaluator to perform one or more evaluation activities.
• Feature. Part of a product that is either included with the product or can be ordered
separately.
• Target of Evaluation (TOE). A group of IT products configured as an IT system, or an
IT product, and associated documentation that is the subject of a security evaluation
under the CC.
• Validation. The process carried out by the CCEVS Validation Body leading to the issue
of a Common Criteria certificate.
• Validation Body. A governmental organization responsible for carrying out validation
and for overseeing the day-to-day operation of the NIAP Common Criteria Evaluation
and Validation Scheme.
14 Bibliography
The Validation Team used the following documents to produce this Validation Report:
[1] Common Criteria for Information Technology Security Evaluation: Part 1:
Introduction and General Model, Version 3.1, Revision 5, April 2017.
[2] Common Criteria for Information Technology Security Evaluation Part 2: Security
functional components, Version 3.1, Revision 5, April 2017.
Cisco Secure Network Analytics (SNA) Validation Report Version 1.0, February 22, 2023
14
[3] Common Criteria for Information Technology Security Evaluation Part 3: Security
assurance components, Version 3.1 Revision 5, April 2017.
[4] collaborative Protection Profile for Network Devices, version 2.2e, 23 March 2020.
[5] Cisco Secure Network Analytics (SNA) 7.4 Security Target, Version 1.2, February
20, 2023 (ST).
[6] Assurance Activity Report for Cisco Secure Network Analytics (SNA) 7.4, Version
1.0, February 21, 2023 (AAR).
[7] Detailed Test Report for Cisco Secure Network Analytics (SNA) 7.4, Version 1.1,
February 21, 2023 (DTR).
[8] Evaluation Technical Report for Cisco Secure Network Analytics (SNA), Version
1.0, February 21, 2023 (ETR)