Arbor Edge Defense 7.0.2.0 Security Target Version 1.11 January 2025 Document prepared by www.lightshipsec.com NETSCOUT Security Target Page 2 of 47 Document History Version Date Author Description 1.0 14 Sept 2023 M Baldock Published 1.1 25 Sept 2023 M Baldock Addressing QA. 1.2 13 Feb 2024 M Baldock Addressing OR01 1.3 27 Feb 2024 M Baldock Addressing OR02 1.4 12 Apr 2024 M Baldock Guidance Updates 1.5 23 May 2024 M Baldock Addressing OR03 1.6 02 Oct 2024 M Baldock Addressing OR05 1.7 21 Oct 2024 M Baldock Addressing OR05 and OR06 1.8 23 Oct 2024 M Baldock Addressing OR07 1.9 20 Nov 2024 M Baldock CAVP Updates 1.10 12 Dec 2024 M Baldock Addressing OR08 1.11 31 Jan 2025 M Baldock Addressing OR09 NETSCOUT Security Target Page 3 of 47 Table of Contents 1 Introduction ........................................................................................................................... 5 1.1 Overview ........................................................................................................................ 5 1.2 Identification ................................................................................................................... 5 1.3 Conformance Claims...................................................................................................... 5 1.4 Terminology.................................................................................................................... 7 2 TOE Description.................................................................................................................... 8 2.1 Type ............................................................................................................................... 8 2.2 Security Functions / Logical Scope................................................................................ 9 2.3 Physical Scope............................................................................................................. 10 3 Security Problem Definition............................................................................................... 12 3.1 Threats ......................................................................................................................... 12 3.2 Assumptions................................................................................................................. 13 3.3 Organizational Security Policies................................................................................... 15 4 Security Objectives............................................................................................................. 15 5 Security Requirements....................................................................................................... 16 5.1 Conventions ................................................................................................................. 16 5.2 Extended Components Definition................................................................................. 16 5.3 Functional Requirements ............................................................................................. 17 5.4 Assurance Requirements............................................................................................. 33 6 TOE Summary Specification.............................................................................................. 34 6.1 Security Audit ............................................................................................................... 34 6.2 Cryptographic Support ................................................................................................. 34 6.3 Identification and Authentication .................................................................................. 38 6.4 Security Management .................................................................................................. 40 6.5 Protection of the TSF ................................................................................................... 41 6.6 TOE Access ................................................................................................................. 43 6.7 Trusted Path/Channels ................................................................................................ 43 7 Rationale.............................................................................................................................. 44 7.1 Conformance Claim Rationale ..................................................................................... 44 7.2 Security Objectives Rationale ...................................................................................... 44 7.3 Security Requirements Rationale................................................................................. 44 List of Tables Table 1: Evaluation identifiers ......................................................................................................... 5 Table 2: NIAP Technical Decisions ................................................................................................. 5 Table 3: Terminology....................................................................................................................... 7 Table 4: CAVP Certificates............................................................................................................ 10 Table 5: TOE models..................................................................................................................... 10 Table 6: Threats............................................................................................................................. 12 Table 7: Assumptions .................................................................................................................... 13 Table 8: Organizational Security Policies...................................................................................... 15 Table 9: Security Objectives for the Operational Environment ..................................................... 15 Table 10: Summary of Extended Components ............................................................................. 16 Table 11: Summary of SFRs ......................................................................................................... 17 Table 12: Audit Events .................................................................................................................. 19 Table 13: Assurance Requirements .............................................................................................. 33 NETSCOUT Security Target Page 4 of 47 Table 14: Key Agreement Mapping............................................................................................... 35 Table 15: HMAC Characteristics ................................................................................................... 36 Table 16: Keys............................................................................................................................... 41 Table 17: Passwords ..................................................................................................................... 42 Table 18: CPP_ND_v2.2E SFR Rationale .................................................................................... 44 NETSCOUT Security Target Page 5 of 47 1 Introduction 1.1 Overview 1 This Security Target (ST) defines the NETSCOUT Arbor Edge Defense 7.0.2.0 (AED) Target of Evaluation (TOE) for the purposes of Common Criteria (CC) evaluation. 2 The TOE secures the internet data center edge from threats against availability — specifically from application-layer, distributed denial of service (DDoS) attacks. 1.2 Identification Table 1: Evaluation identifiers Target of Evaluation NETSCOUT Arbor Edge Defense 7.0.2.0 Build: 7.0.2.0 build NHQI Security Target NETSCOUT Arbor Edge Defense 7.0.2.0 Security Target, v1.11 1.3 Conformance Claims 3 This ST supports the following conformance claims: a) CC version 3.1 revision 5 b) CC Part 2 extended c) CC Part 3 conformant d) collaborative Protection Profile for Network Devices, v2.2e, 23 March 2020 (referenced within as CPP_ND_v2.2E) e) NIAP Technical Decisions per Table 2 Table 2: NIAP Technical Decisions TD # Name Rationale if n/a TD0527 Updates to Certificate Revocation Testing (FIA_X509_EXT.1) TD0528 NIT Technical Decision for Missing EAs for FCS_NTP_EXT.1.4 TD0536 NIT Technical Decision for Update Verification Inconsistency TD0537 NIT Technical Decision for Incorrect reference to FCS_TLSC_EXT.2.3 TD0546 NIT Technical Decision for DTLS - clarification of Application Note 63 FCS_DTLSC_EXT.1 not claimed TD0547 NIT Technical Decision for Clarification on developer disclosure of AVA_VAN NETSCOUT Security Target Page 6 of 47 TD # Name Rationale if n/a TD0555 NIT Technical Decision for RFC Reference incorrect in TLSS Test TD0556 NIT Technical Decision for RFC 5077 question TD0563 NiT Technical Decision for Clarification of audit date information TD0564 NiT Technical Decision for Vulnerability Analysis Search Criteria TD0569 NIT Technical Decision for Session ID Usage Conflict in FCS_DTLSS_EXT.1.7 TD0570 NiT Technical Decision for Clarification about FIA_AFL.1 TD0571 NiT Technical Decision for Guidance on how to handle FIA_AFL.1 TD0572 NiT Technical Decision for Restricting FTP_ITC.1 to only IP address identifiers TD0580 NIT Technical Decision for clarification about use of DH14 in NDcPPv2.2e TD0581 NIT Technical Decision for Elliptic curve-based key establishment and NIST SP 800-56Arev3 TD0591 NIT Technical Decision for Virtual TOEs and hypervisors TD0592 NIT Technical Decision for Local Storage of Audit Records TD0631 NIT Technical Decision for Clarification of public key authentication for SSH Server TD0632 NIT Technical Decision for Consistency with Time Data for vNDs TD0635 NIT Technical Decision for TLS Server and Key Agreement Parameters TD0636 NIT Technical Decision for Clarification of Public Key User Authentication for SSH FCS_SSHC_EXT.1 not claimed TD0638 NIT Technical Decision for Key Pair Generation for Authentication TD0639 NIT Technical Decision for Clarification for NTP MAC Keys NETSCOUT Security Target Page 7 of 47 TD # Name Rationale if n/a TD0670 NIT Technical Decision for Mutual and Non-Mutual Auth TLSC Testing FCS_TLSC_EXT.2 not claimed TD0738 NIT Technical Decision for Link to Allowed-With List TD0790 NIT Technical Decision: Clarification Required for testing IPv6 TD0792 NIT Technical Decision: FIA_PMG_EXT.1 - TSS EA not in line with SFR TD0800 Updated NIT Technical Decision for IPsec IKE/SA Lifetimes Tolerance FCS_IPSEC_EXT.1 not claimed 1.4 Terminology Table 3: Terminology Term Definition AED Arbor Edge Defense CC Common Criteria DDoS Distributed Denial of Service EAL Evaluation Assurance Level NDcPP collaborative Protection Profile for Network Devices PP Protection Profile TOE Target of Evaluation TSF TOE Security Functionality NETSCOUT Security Target Page 8 of 47 2 TOE Description 2.1 Type 4 The TOE is a network device. The AED secures the internet data center edge from threats against availability; specifically from application-layer, distributed denial of service (DDoS) attacks. 2.1.1 Deployment 5 The TOE is deployed as an inline security appliance at the network perimeter between the internet router and network firewall. The figure below depicts an example deployment of the TOE devices (enclosed in red). Figure 1: Example TOE Deployment NETSCOUT Security Target Page 9 of 47 2.1.2 Interfaces 6 The TOE management interfaces are shown in Figure 2. Figure 2: TOE interfaces 7 The TOE interfaces are as follows: a) CLI. Command line management interface via local Serial console, local VGA connection or remote SSH. b) Web GUI. HTTPS/TLS management interface. c) Syslog. Transmission of logs to a remote server via TLS. d) NTP. The TOE synchronizes time via NTP. e) OCSP. The TOE queries an OCSP responder for revocation status of X.509 certificates. 2.2 Security Functions / Logical Scope 8 The TOE provides the following security functions: a) Protected Communications. The TOE protects the integrity and confidentiality of communications as noted in section 2.1.2 above. b) Secure Administration. The TOE enables secure management of its security functions, including: i) Administrator authentication with passwords ii) Configurable password policies iii) Role Based Access Control iv) Access banners v) Management of critical security functions and data NETSCOUT Security Target Page 10 of 47 vi) Protection of cryptographic keys and passwords c) Trusted Update. The TOE ensures the authenticity and integrity of software updates through digital signatures. d) System Monitoring. The TOE generates logs of security relevant events. The TOE stores logs locally and is capable of sending log events to a remote audit server. e) Self-Test. The TOE performs a suite of self-tests to ensure the correct operation and enforcement of its security functions. f) Cryptographic Operations. The TOE implements a cryptographic module. Relevant Cryptographic Algorithm Validation Program (CAVP) certificates are shown in Table 4. Table 4: CAVP Certificates Algorithm Capability Certificate AES-CTR, AES-CBC, AES-GCM C2144 ECDSA Key Gen (186-4) ECDSA Sig Gen (186-4) ECDSA Sig Ver (186-4) SHA-1, SHA-256, SHA-384, SHA-512 HMAC-SHA-1, HMAC-SHA-256, HMAC-SHA-512 CTR_DRBG RSA SigGen / SigVer A6206 KAS-ECC-SSC A1882 2.3 Physical Scope 9 The physical boundary of the TOE includes all software and hardware shown in Table 5. The TOE is delivered via commercial courier. Table 5: TOE models Model CPU Software Differences AED2600 Intel Xeon E5-2608L v3 (Haswell) Arbor Edge Defense v7.0.2.0 on Processing speed, number of drives and supported ports. AED2800 Intel Xeon E5-2648L v3 (Haswell) NETSCOUT Security Target Page 11 of 47 Model CPU Software Differences AED8100 Intel Xeon Silver 4210T (Cascade Lake) ArbOS 7.3 2.3.1 Guidance Documents 10 The TOE includes the following guidance documents (PDF): a) Arbor Edge Defense 7.0.2.0 Common Criteria Guide, v1.4 12 Registered users download the guidance documents from NETSCOUT’s web portal. https://www.netscout.com/support-services 2.3.2 Non-TOE Components 11 The TOE operates with the following components in the environment: a) Audit Server. The TOE sends audit events to the Audit Server. b) OCSP Response. The TOE queries an OCSP responder for revocation status of X.509 certificates. c) NTP Server. The TOE synchronizes time via NTP. 2.3.3 Functions not included in the TOE Evaluation 12 REST API is out of scope. Only those functions listed at 2.2 have been evaluated. The REST API is inaccessible when API keys are not generated, and no API keys are present by default. Administrators are instructed not to generate API keys, leaving the API disabled. NETSCOUT Security Target Page 12 of 47 3 Security Problem Definition 13 The Security Problem Definition is reproduced from section 4 of the CPP_ND_v2.2E. 3.1 Threats Table 6: Threats Identifier Description T.UNAUTHORIZED_ ADMINISTRATOR_ ACCESS Threat agents may attempt to gain Administrator access to the Network Device by nefarious means such as masquerading as an Administrator to the device, masquerading as the device to an Administrator, replaying an administrative session (in its entirety, or selected portions), or performing man-in-the-middle attacks, which would provide access to the administrative session, or sessions between Network Devices. Successfully gaining Administrator access allows malicious actions that compromise the security functionality of the device and the network on which it resides. T.WEAK_ CRYPTOGRAPHY Threat agents may exploit weak cryptographic algorithms or perform a cryptographic exhaust against the key space. Poorly chosen encryption algorithms, modes, and key sizes will allow attackers to compromise the algorithms, or brute force exhaust the key space and give them unauthorized access allowing them to read, manipulate and/or control the traffic with minimal effort. T.UNTRUSTED_ COMMUNICATION_ CHANNELS Threat agents may attempt to target Network Devices that do not use standardized secure tunnelling protocols to protect the critical network traffic. Attackers may take advantage of poorly designed protocols or poor key management to successfully perform man-in-the-middle attacks, replay attacks, etc. Successful attacks will result in loss of confidentiality and integrity of the critical network traffic, and potentially could lead to a compromise of the Network Device itself. T.WEAK_ AUTHENTICATION_ ENDPOINTS Threat agents may take advantage of secure protocols that use weak methods to authenticate the endpoints – e.g. a shared password that is guessable or transported as plaintext. The consequences are the same as a poorly designed protocol, the attacker could masquerade as the Administrator or another device, and the attacker could insert themselves into the network stream and perform a man-in-the-middle attack. The result is the critical network traffic is exposed and there could be a loss of confidentiality and integrity, and potentially the Network Device itself could be compromised. T.UPDATE_ COMPROMISE Threat agents may attempt to provide a compromised update of the software or firmware which undermines the security functionality of the device. Non-validated updates or updates validated using non-secure or weak cryptography leave the update firmware vulnerable to surreptitious alteration. NETSCOUT Security Target Page 13 of 47 Identifier Description T.UNDETECTED_ ACTIVITY Threat agents may attempt to access, change, and/or modify the security functionality of the Network Device without Administrator awareness. This could result in the attacker finding an avenue (e.g., misconfiguration, flaw in the product) to compromise the device and the Administrator would have no knowledge that the device has been compromised. T.SECURITY_ FUNCTIONALITY_ COMPROMISE Threat agents may compromise credentials and device data enabling continued access to the Network Device and its critical data. The compromise of credentials includes replacing existing credentials with an attacker’s credentials, modifying existing credentials, or obtaining the Administrator or device credentials for use by the attacker. T.PASSWORD_ CRACKING Threat agents may be able to take advantage of weak administrative passwords to gain privileged access to the device. Having privileged access to the device provides the attacker unfettered access to the network traffic, and may allow them to take advantage of any trust relationships with other Network Devices. T.SECURITY_ FUNCTIONALITY_ FAILURE An external, unauthorized entity could make use of failed or compromised security functionality and might therefore subsequently use or abuse security functions without prior authentication to access, change or modify device data, critical network traffic or security functionality of the device. 3.2 Assumptions Table 7: Assumptions Identifier Description A.PHYSICAL_ PROTECTION The Network Device is assumed to be physically protected in its operational environment and not subject to physical attacks that compromise the security or interfere with the device’s physical interconnections and correct operation. This protection is assumed to be sufficient to protect the device and the data it contains. As a result, the cPP does not include any requirements on physical tamper protection or other physical attack mitigations. The cPP does not expect the product to defend against physical access to the device that allows unauthorized entities to extract data, bypass other controls, or otherwise manipulate the device. For vNDs, this assumption applies to the physical platform on which the VM runs. NETSCOUT Security Target Page 14 of 47 Identifier Description A.LIMITED_ FUNCTIONALITY The device is assumed to provide networking functionality as its core function and not provide functionality/services that could be deemed as general purpose computing. For example, the device should not provide a computing platform for general purpose applications (unrelated to networking functionality). If a virtual TOE evaluated as a pND, following Case 2 vNDs as specified in Section 1.2, the VS is considered part of the TOE with only one vND instance for each physical hardware platform. The exception being where components of a distributed TOE run inside more than one virtual machine (VM) on a single VS. In Case 2 vND, no non-TOE guest VMs are allowed on the platform. A.NO_THRU_ TRAFFIC_ PROTECTION A standard/generic Network Device does not provide any assurance regarding the protection of traffic that traverses it. The intent is for the Network Device to protect data that originates on or is destined to the device itself, to include administrative data and audit data. Traffic that is traversing the Network Device, destined for another network entity, is not covered by the NDcPP. It is assumed that this protection will be covered by cPPs and PP-Modules for particular types of Network Devices (e.g., firewall). A.TRUSTED_ ADMINISTRATOR The Security Administrator(s) for the Network Device are assumed to be trusted and to act in the best interest of security for the organization. This includes appropriately trained, following policy, and adhering to guidance documentation. Administrators are trusted to ensure passwords/credentials have sufficient strength and entropy and to lack malicious intent when administering the device. The Network Device is not expected to be capable of defending against a malicious Administrator that actively works to bypass or compromise the security of the device. For TOEs supporting X.509v3 certificate-based authentication, the Security Administrator(s) are expected to fully validate (e.g. offline verification) any CA certificate (root CA certificate or intermediate CA certificate) loaded into the TOE’s trust store (aka ‘root store’, ‘ trusted CA Key Store’, or similar) as a trust anchor prior to use (e.g. offline verification). A.REGULAR_ UPDATES The Network Device firmware and software is assumed to be updated by an Administrator on a regular basis in response to the release of product updates due to known vulnerabilities. A.ADMIN_ CREDENTIALS_ SECURE The Administrator’s credentials (private key) used to access the Network Device are protected by the platform on which they reside. A.RESIDUAL_ INFORMATION The Administrator must ensure that there is no unauthorized access possible for sensitive residual information (e.g. cryptographic keys, keying material, PINs, passwords etc.) on networking equipment when the equipment is discarded or removed from its operational environment. NETSCOUT Security Target Page 15 of 47 3.3 Organizational Security Policies Table 8: Organizational Security Policies Identifier Description P.ACCESS_BANNER The TOE shall display an initial banner describing restrictions of use, legal agreements, or any other appropriate information to which users consent by accessing the TOE. 4 Security Objectives 14 The security objectives are reproduced from section 5 of the CPP_ND_v2.2E. Table 9: Security Objectives for the Operational Environment Identifier Description OE.PHYSICAL Physical security, commensurate with the value of the TOE and the data it contains, is provided by the environment. OE.NO_GENERAL_ PURPOSE There are no general-purpose computing capabilities (e.g., compilers or user applications) available on the TOE, other than those services necessary for the operation, administration and support of the TOE. OE.NO_THRU_ TRAFFIC_ PROTECTION The TOE does not provide any protection of traffic that traverses it. It is assumed that protection of this traffic will be covered by other security and assurance measures in the operational environment. OE.TRUSTED_ADMIN Security Administrators are trusted to follow and apply all guidance documentation in a trusted manner. For vNDs, this includes the VS Administrator responsible for configuring the VMs that implement ND functionality. For TOEs supporting X.509v3 certificate-based authentication, the Security Administrator(s) are assumed to monitor the revocation status of all certificates in the TOE’s trust store and to remove any certificate from the TOE’s trust store in case such certificate can no longer be trusted. OE.UPDATES The TOE firmware and software is updated by an Administrator on a regular basis in response to the release of product updates due to known vulnerabilities. OE.ADMIN_ CREDENTIALS_ SECURE The Administrator’s credentials (private key) used to access the TOE must be protected on any other platform on which they reside. OE.RESIDUAL_ INFORMATION The Security Administrator ensures that there is no unauthorized access possible for sensitive residual information (e.g. cryptographic keys, keying material, PINs, passwords etc.) on networking equipment when the equipment is discarded or removed from its operational environment. NETSCOUT Security Target Page 16 of 47 5 Security Requirements 5.1 Conventions 15 This document uses the following font conventions to identify the operations defined by the CC: a) Assignment. Indicated with italicized text. b) Refinement. Indicated with bold text and strikethroughs. c) Selection. Indicated with underlined text. d) Assignment within a Selection: Indicated with italicized and underlined text. e) Iteration. Indicated by adding a string starting with “/” (e.g. “FCS_COP.1/Hash”). 16 Note: Operations performed within the Security Target are denoted within brackets []. Operations shown without brackets are reproduced from the CPP_ND_v2.2E. 5.2 Extended Components Definition 17 The following extended components are defined in Appendix C of the CPP_ND_v2.2E. Any applicable TDs for the extended SFR’s are defined in Table 2. Rationale is given if a TD need not apply. Table 10: Summary of Extended Components Requirement Title Source TDs/RFI FAU_STG_EXT.1 Protected Audit Event Storage NDcPP2.2e N/A FCS_HTTPS_EXT.1 HTTPS Protocol NDcPP2.2e N/A FCS_NTP_EXT.1 NTP Protocol NDcPP2.2e TD0528 FCS_RBG_EXT.1 Random Bit Generation NDcPP2.2e N/A FCS_SSHS_EXT.1 SSH Server Protocol NDcPP2.2e TD0631 FCS_TLSC_EXT.1 TLS Client Protocol without Mutual Authentication NDcPP2.2e TD0634, TD0670 FCS_TLSS_EXT.1 TLS Server Protocol without Mutual Authentication NDcPP2.2e TD0555, TD0556, TD0569, TD0635 FIA_PMG_EXT.1 Password Management NDcPP2.2e TD0571 FIA_UIA_EXT.1 User Identification and Authentication NDcPP2.2e N/A FIA_UAU_EXT.2 Password-based Authentication Mechanism NDcPP2.2e N/A NETSCOUT Security Target Page 17 of 47 Requirement Title Source TDs/RFI FIA_X509_EXT.1/Rev X509 Certificate Validation NDcPP2.2e TD0527 FIA_X509_EXT.2 X509 Certificate Authentication NDcPP2.2e TD0537 FIA_X509_EXT.3 X509 Certificate Requests NDcPP2.2e N/A FPT_SKP_EXT.1 Protection of TSF Data (for reading of all symmetric keys) NDcPP2.2e TD0639 FPT_APW_EXT.1 Protection of Administrator Passwords NDcPP2.2e N/A FPT_TST_EXT.1 TSF Testing NDcPP2.2e N/A FPT_TUD_EXT.1 Trusted Update NDcPP2.2e N/A FPT_STM_EXT.1 Reliable Time Stamps NDcPP2.2e TD0632 FTA_SSL_EXT.1 TSF-Initiated Session Locking NDcPP2.2e N/A 5.3 Functional Requirements Table 11: Summary of SFRs Requirement Title FAU_GEN.1 Audit Data Generation FAU_GEN.2 User Identity Association FAU_STG_EXT.1 Protected Audit Event Storage FCS_CKM.1 Cryptographic Key Generation FCS_CKM.2 Cryptographic Key Establishment FCS_CKM.4 Cryptographic Key Destruction FCS_COP.1/DataEncryption Cryptographic Operation (AES Data Encryption/Decryption) FCS_COP.1/SigGen Cryptographic Operation (Signature Generation and Verification) FCS_COP.1/Hash Cryptographic Operation (Hash Algorithm) FCS_COP.1/KeyedHash Cryptographic Operation (Keyed Hash Algorithm) FCS_HTTPS_EXT.1 HTTPS Protocol FCS_NTP_EXT.1 NTP Protocol NETSCOUT Security Target Page 18 of 47 Requirement Title FCS_RBG_EXT.1 Random Bit Generation FCS_SSHS_EXT.1 SSH Server Protocol FCS_TLSC_EXT.1 TLS Client Protocol FCS_TLSS_EXT.1 TLS Server Protocol FIA_AFL.1 Authentication Failure Management FIA_PMG_EXT.1 Password Management FIA_UIA_EXT.1 User Identification and Authentication FIA_UAU_EXT.2 Password-based Authentication Mechanism FIA_UAU.7 Protected Authentication Feedback FIA_X509_EXT.1/Rev Certificate Validation FIA_X509_EXT.2 Certificate Authentication FIA_X509_EXT.3 Certificate Requests FMT_MOF.1/ManualUpdate Management of Security Functions Behaviour FMT_MOF.1/Services Management of Security Functions Behaviour FMT_MTD.1/CoreData Management of TSF Data FMT_MTD.1/CryptoKeys Management of TSF Data FMT_SMF.1 Specification of Management Functions FMT_SMR.2 Restrictions on Security Roles FPT_SKP_EXT.1 Protection of TSF Data (for reading of all pre-shared, symmetric and private keys) FPT_APW_EXT.1 Protection of Administrator Passwords FPT_TST_EXT.1 TSF Testing FPT_TUD_EXT.1 Trusted Update FPT_STM_EXT.1 Reliable Time Stamps FTA_SSL_EXT.1 TSF-initiated Session Locking FTA_SSL.3 TSF-initiated Termination NETSCOUT Security Target Page 19 of 47 Requirement Title FTA_SSL.4 User-initiated Termination FTA_TAB.1 Default TOE Access Banners FTP_ITC.1 Inter-TSF trusted channel FTP_TRP.1/Admin Trusted Path 5.3.1 Security Audit (FAU) FAU_GEN.1 Audit Data Generation FAU_GEN.1.1 The TSF shall be able to generate an audit record of the following auditable events: a) Start-up and shutdown of the audit functions; b) All auditable events for the not specified level of audit; c) All administrative actions comprising: o Administrative login and logout (name of user account shall be logged if individual user accounts are required for Administrators). o Changes to TSF data related to configuration changes (in addition to the information that a change occurred it shall be logged what has been changed). o Generating/import of, changing, or deleting of cryptographic keys (in addition to the action itself a unique key name or key reference shall be logged). o Resetting passwords (name of related user account shall be logged). o [no other actions]; d) Specifically defined auditable events listed in Table 2 Table 12. Table 12: Audit Events Requirement Auditable Events Additional Audit Record Contents FAU_GEN.1 None. None. FAU_GEN.2 None. None. FAU_STG_EXT.1 None. None. FCS_CKM.1 None. None. FCS_CKM.2 None. None. NETSCOUT Security Target Page 20 of 47 Requirement Auditable Events Additional Audit Record Contents FCS_CKM.4 None. None. FCS_COP.1/DataEncryption None. None. FCS_COP.1/SigGen None. None. FCS_COP.1/Hash None. None. FCS_COP.1/KeyedHash None. None. FCS_HTTPS_EXT.1 Failure to establish a HTTPS Session. Reason for failure FCS_NTP_EXT.1 • Configuration of a new time server • Removal of configured time server Identity if new/removed time server FCS_RBG_EXT.1 None. None. FCS_SSHS_EXT.1 Failure to establish an SSH session Reason for failure FCS_TLSC_EXT.1 Failure to establish a TLS session Reason for failure FCS_TLSS_EXT.1 Failure to establish a TLS session Reason for failure FIA_AFL.1 Unsuccessful login attempts limit is met or exceeded. Origin of the attempt (e.g., IP address). FIA_PMG_EXT.1 None. None. FIA_UIA_EXT.1 All use of identification and authentication mechanism. Provided user identity, origin of the attempt (e.g., IP address). FIA_UAU_EXT.2 All use of identification and authentication mechanism. Origin of the attempt (e.g., IP address). FIA_UAU.7 None. None. FIA_X509_EXT.1/Rev • Unsuccessful attempt to validate a certificate • Any addition, replacement or removal of trust anchors in the TOE's trust store • Reason for failure of certificate validation • Identification of certificates added, replaced or removed as trust anchor in the TOE's trust store NETSCOUT Security Target Page 21 of 47 Requirement Auditable Events Additional Audit Record Contents FIA_X509_EXT.2 None. None. FIA_X509_EXT.3 None. None. FMT_MOF.1/ManualUpdate Any attempt to initiate a manual update None. FMT_MOF.1/Services None. None. FMT_MTD.1/CoreData None. None. FMT_MTD.1/CryptoKeys None. None. FMT_SMF.1 All management activities of TSF data. None. FMT_SMR.2 None. None. FPT_SKP_EXT.1 None. None. FPT_APW_EXT.1 None. None. FPT_TST_EXT.1 None. None. FPT_TUD_EXT.1 Initiation of update; result of the update attempt (success or failure) None. FPT_STM_EXT.1 Discontinuous changes to time - either Administrator actuated or changed via an automated process. (Note that no continuous changes to time need to be logged. See also application note on FPT_STM_EXT.1) For discontinuous changes to time: The old and new values for the time. Origin of the attempt to change time for success and failure (e.g., IP address). FTA_SSL_EXT.1 (if “terminate the session” is selected) The termination of a local session by the session locking mechanism. None. FTA_SSL.3 The termination of a remote session by the session locking mechanism. None. FTA_SSL.4 The termination of an interactive session. None. FTA_TAB.1 None. None. NETSCOUT Security Target Page 22 of 47 Requirement Auditable Events Additional Audit Record Contents FTP_ITC.1 Initiation of the trusted channel. Termination of the trusted channel. Failure of the trusted channel functions. Identification of the initiator and target of failed trusted channels establishment attempt. FTP_TRP.1/Admin Initiation of the trusted path. Termination of the trusted path. Failure of the trusted path functions. None. FAU_GEN.1.2 The TSF shall record within each audit record at least the following information: a) Date and time of the event, type of event, subject identity, and the outcome (success or failure) of the event; and b) For each audit event type, based on the auditable event definitions of the functional components included in the cPP/ST, information specified in column three of Table 2 Table 12. FAU_GEN.2 User Identity Association FAU_GEN.2.1 For audit events resulting from actions of identified users, the TSF shall be able to associate each auditable event with the identity of the user that caused the event. FAU_STG_EXT.1 Protected Audit Event Storage FAU_STG_EXT.1.1 The TSF shall be able to transmit the generated audit data to an external IT entity using a trusted channel according to FTP_ITC.1. FAU_STG_EXT.1.2 The TSF shall be able to store generated audit data on the TOE itself. In addition [ • The TOE shall consist of a single standalone component that stores audit data locally] FAU_STG_EXT.1.3 The TSF shall [overwrite previous audit records according to the following rule: [overwrite oldest record first]] when the local storage space for audit data is full. 5.3.2 Cryptographic Support (FCS) FCS_CKM.1 Cryptographic Key Generation FCS_CKM.1.1 The TSF shall generate asymmetric cryptographic keys in accordance with a specified cryptographic key generation algorithm: [ NETSCOUT Security Target Page 23 of 47 • ECC schemes using “NIST curves” [P-256, P-384, P-521] that meet the following: FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Appendix B.4; • FFC Schemes using ‘safe-prime’ groups that meet the following: “NIST Special Publication 800-56A Revision 3, Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography” and [RFC 3526] ]and specified cryptographic key sizes [assignment: cryptographic key sizes] that meet the following: [assignment: list of standards]. FCS_CKM.2 Cryptographic Key Establishment FCS_CKM.2.1 The TSF shall perform cryptographic key establishment in accordance with a specified cryptographic key establishment method: [ • Elliptic curve-based key establishment schemes that meet the following: NIST Special Publication 800-56A Revision 3, “Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography”; • FFC Schemes using “safe-prime” groups that meet the following: ‘NIST Special Publication 800-56A Revision 3, “Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography” and [RFC 3526]; ] that meets the following: [assignment: list of standards]. FCS_CKM.4 Cryptographic Key Destruction FCS_CKM.4.1 The TSF shall destroy cryptographic keys in accordance with a specified cryptographic key destruction method • For plaintext keys in volatile storage, the destruction shall be executed by a [single overwrite consisting of [a pseudo-random pattern using the TSF’s RBG]]; • For plaintext keys in non-volatile storage, the destruction shall be executed by the invocation of an interface provided by a part of the TSF that [ o logically addresses the storage location of the key and performs a [single] overwrite consisting of [a pseudo-random pattern using the TSF’s RBG]; that meets the following: No Standard. FCS_COP.1/DataEncryption Cryptographic Operation (AES Data Encryption/Decryption) FCS_COP.1.1/DataEncryption The TSF shall perform encryption/decryption in accordance with a specified cryptographic algorithm AES used in [CBC, CTR, GCM] mode and cryptographic key sizes [128 bits, 256 bits] that meet the following: AES as specified in ISO 18033-3, [CBC as specified in ISO 10116, CTR as specified in ISO 10116, GCM as specified in ISO 19772]. NETSCOUT Security Target Page 24 of 47 FCS_COP.1/SigGen Cryptographic Operation (Signature Generation and Verification) FCS_COP.1.1/SigGen The TSF shall perform cryptographic signature services (generation and verification) in accordance with a specified cryptographic algorithm [ • RSA Digital Signature Algorithm and cryptographic key sizes (modulus) [2048, 3072, 4096], • Elliptic Curve Digital Signature Algorithm and cryptographic key sizes [256, 384, 521], ] that meet the following: [ • For RSA schemes: FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Section 5.5, using PKCS #1 v2.1 Signature Schemes RSASSA-PSS and/or RSASSA-PKCS1v1_5; ISO/IEC 9796-2, Digital signature scheme 2 or Digital Signature scheme 3, • For ECDSA schemes: FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Section 6 and Appendix D, Implementing “NIST curves” [P- 256, P-384, P-521]; ISO/IEC 14888-3, Section 6.4] FCS_COP.1/Hash Cryptographic Operation (Hash Algorithm) FCS_COP.1.1/Hash The TSF shall perform cryptographic hashing services in accordance with a specified cryptographic algorithm [SHA-1, SHA-256, SHA-384. SHA-512] and cryptographic key sizes [assignment: cryptographic key sizes] and message digest sizes [160, 256, 384, 512] bits that meet the following: ISO/IEC 10118-3:2004. FCS_COP.1/KeyedHash Cryptographic Operation (Keyed Hash Algorithm) FCS_COP.1.1/KeyedHash The TSF shall perform keyed-hash message authentication in accordance with a specified cryptographic algorithm [HMAC-SHA-1, HMAC-SHA-256, HMAC-SHA-512] and cryptographic key sizes [160, 256, 512] and message digest sizes [160, 256, 512] bits that meet the following: ISO/IEC 9797-2:2011, Section 7 “MAC Algorithm 2”. FCS_HTTPS_EXT.1 HTTPS Protocol FCS_HTTPS_EXT.1.1 The TSF shall implement the HTTPS protocol that complies with RFC 2818. FCS_HTTPS_EXT.1.2 The TSF shall implement HTTPS using TLS. FCS_HTTPS_EXT.1.3 If a peer certificate is presented, the TSF shall [not require client authentication] if the peer certificate is deemed invalid. FCS_NTP_EXT.1 NTP Protocol FCS_NTP_EXT.1.1 The TSF shall use only the following NTP version(s) [NTP v4 (RFC 5905)]. FCS_NTP_EXT.1.2 The TSF shall update its system time using [ NETSCOUT Security Target Page 25 of 47 • Authentication using [SHA1] as the message digest algorithm(s)] FCS_NTP_EXT.1.3 The TSF shall not update NTP timestamp from broadcast and/or multicast addresses. FCS_NTP_EXT.1.4 The TSF shall support configuration of at least three (3) NTP time sources. FCS_RBG_EXT.1 Random Bit Generation FCS_RBG_EXT.1.1 The TSF shall perform all deterministic random bit generation services in accordance with ISO/IEC 18031:2011 using [CTR_DRBG (AES)]. FCS_RBG_EXT.1.2 The deterministic RBG shall be seeded by at least one entropy source that accumulates entropy from [[one] platform-based noise source] with a minimum of [256 bits] of entropy at least equal to the greatest security strength, according to ISO/IEC 18031:2011 Table C.1 “Security Strength Table for Hash Functions”, of the keys and hashes that it will generate. FCS_SSHS_EXT.1 SSH Server Protocol FCS_SSHS_EXT.1.1 The TSF shall implement the SSH protocol that complies with: RFC(s) 4251, 4252, 4253, 4254, [4344, 5656, 6668, 8268, 8308 section 3.1, 8332]. FCS_SSHS_EXT.1.2 The TSF shall ensure that the SSH protocol implementation supports the following user authentication methods as described in RFC 4252: public key-based, [password based]. FCS_SSHS_EXT.1.3 The TSF shall ensure that, as described in RFC 4253, packets greater than [256 kilo]bytes in an SSH transport connection are dropped. FCS_SSHS_EXT.1.4 The TSF shall ensure that the SSH transport implementation uses the following encryption algorithms and rejects all other encryption algorithms: [aes128-ctr, aes256-ctr, aes128-gcm@openssh.com, aes256-gcm@openssh.com]. FCS_SSHS_EXT.1.5 The TSF shall ensure that the SSH public-key based authentication implementation uses [ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521] as its public key algorithm(s) and rejects all other public key algorithms. FCS_SSHS_EXT.1.6 The TSF shall ensure that the SSH transport implementation uses [hmac-sha1, hmac-sha2-256, hmac-sha2-512] as its MAC algorithm(s) and rejects all other MAC algorithm(s). FCS_SSHS_EXT.1.7 The TSF shall ensure that [ecdh-sha2-nistp256] and [diffie-hellman- group14-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18- sha512, ecdh-sha2-nistp384, ecdh-sha2-nistp521] are the only allowed key exchange methods used for the SSH protocol. FCS_SSHS_EXT.1.8 The TSF shall ensure that within SSH connections, the same session keys are used for a threshold of no longer than one hour, and each NETSCOUT Security Target Page 26 of 47 encryption key is used to protect no more than one gigabyte of data. After any of the thresholds are reached, a rekey needs to be performed. FCS_TLSC_EXT.1 TLS Client Protocol FCS_TLSC_EXT.1.1 The TSF shall implement [TLS 1.2 (RFC 5246)] and reject all other TLS and SSL versions. The TLS implementation will support the following ciphersuites: [ • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289 • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289 • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 ] and no other ciphersuites. FCS_TLSC_EXT.1.2 The TSF shall verify that the presented identifier matches [the reference identifier per RFC 6125 section 6, IPv4 address in SAN]. FCS_TLSC_EXT.1.3 When establishing a trusted channel, by default the TSF shall not establish a trusted channel if the server certificate is invalid. The TSF shall also [ • Not implement any administrator override mechanism ]. FCS_TLSC_EXT.1.4 The TSF shall [present the Supported Elliptic Curves/Supported Groups Extension with the following curves/groups: [secp256r1, secp384r1, secp521r1] and no other curves/groups] in the Client Hello. FCS_TLSS_EXT.1 TLS Server Protocol FCS_TLSS_EXT.1.1 The TSF shall implement [TLS 1.2 (RFC 5246)] and reject all other TLS and SSL versions. The TLS implementation will support the following ciphersuites: [ • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289 • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 NETSCOUT Security Target Page 27 of 47 ] FCS_TLSS_EXT.1.2 The TSF shall deny connections from clients requesting SSL 2.0, SSL 3.0, TLS 1.0 and [TLS 1.1]. FCS_TLSS_EXT.1.3 The TSF shall perform key establishment for TLS using [ECDHE curves [secp256r1, secp384r1, secp521r1] and no other curves]]. FCS_TLSS_EXT.1.4 The TSF shall support [session resumption based on session IDs according to RFC 5246 (TLS1.2), session resumption based on session tickets according to RFC 5077]. 5.3.3 Identification and Authentication (FIA) FIA_AFL.1 Authentication Failure Management FIA_AFL.1.1 The TSF shall detect when an Administrator configurable positive integer within [1-30] unsuccessful authentication attempts occur related to Administrators attempting to authenticate remotely using a password. FIA_AFL.1.2 When the defined number of unsuccessful authentication attempts has been met, the TSF shall [prevent the offending Administrator from successfully establishing a remote session using any authentication method that involves a password until [account unlocked via local console] is taken by an Administrator;]. FIA_PMG_EXT.1 Password Management FIA_PMG_EXT.1.1 The TSF shall provide the following password management capabilities for administrative passwords: a) Passwords shall be able to be composed of any combination of upper and lower case letters, numbers, and the following special characters: [ “!”, “@”, “#”, “$”, “%”, “^”, “&”, “*”, “(“, “)”]; b) Minimum password length shall be configurable to between [7] and [72] characters. FIA_UIA_EXT.1 User Identification and Authentication FIA_UIA_EXT.1.1 The TSF shall allow the following actions prior to requiring the non-TOE entity to initiate the identification and authentication process: • Display the warning banner in accordance with FTA_TAB.1; • [[no other actions]] FIA_UIA_EXT.1.2 The TSF shall require each administrative user to be successfully identified and authenticated before allowing any other TSF-mediated actions on behalf of that administrative user. FIA_UAU_EXT.2 Password-based Authentication Mechanism NETSCOUT Security Target Page 28 of 47 FIA_UAU_EXT.2.1 The TSF shall provide a local [password-based] authentication mechanism to perform local administrative user authentication. FIA_UAU.7 Protected Authentication Feedback FIA_UAU.7.1 The TSF shall provide only obscured feedback to the administrative user while the authentication is in progress at the local console. FIA_X509_EXT.1/Rev Certificate Validation FIA_X509_EXT.1.1/Rev The TSF shall validate certificates in accordance with the following rules: • RFC 5280 certificate validation and certification path validation supporting a minimum path length of three certificates. • The certification path must terminate with a trusted CA certificate designated as a trust anchor. • The TSF shall validate a certification path by ensuring that all CA certificates in the certification path contain the basicConstraints extension with the CA flag set to TRUE. • The TSF shall validate the revocation status of the certificate using [the Online Certificate Status Protocol (OCSP) as specified in RFC 6960]. • The TSF shall validate the extendedKeyUsage field according to the following rules: o Certificates used for trusted updates and executable code integrity verification shall have the Code Signing purpose (id- kp 3 with OID 1.3.6.1.5.5.7.3.3) in the extendedKeyUsage field. o Server certificates presented for TLS shall have the Server Authentication purpose (id-kp 1 with OID 1.3.6.1.5.5.7.3.1) in the extendedKeyUsage field. o Client certificates presented for TLS shall have the Client Authentication purpose (id-kp 2 with OID 1.3.6.1.5.5.7.3.2) in the extendedKeyUsage field. o OCSP certificates presented for OCSP responses shall have the OCSP Signing purpose (id-kp 9 with OID 1.3.6.1.5.5.7.3.9) in the extendedKeyUsage field. FIA_X509_EXT.1.2/Rev The TSF shall only treat a certificate as a CA certificate if the basicConstraints extension is present and the CA flag is set to TRUE. FIA_X509_EXT.2 Certificate Authentication FIA_X509_EXT.2.1 The TSF shall use X.509v3 certificates as defined by RFC 5280 to support authentication for [TLS] and [no additional uses]. NETSCOUT Security Target Page 29 of 47 FIA_X509_EXT.2.2 When the TSF cannot establish a connection to determine the validity of a certificate, the TSF shall [not accept the certificate]. FIA_X509_EXT.3 Certificate Requests FIA_X509_EXT.3.1 The TSF shall generate a Certificate Request as specified by RFC 2986 and be able to provide the following information in the request: public key and [Common Name, Organization, Organizational Unit, Country]. FIA_X509_EXT.3.2 The TSF shall validate the chain of certificates from the Root CA upon receiving the CA Certificate Response. 5.3.4 Security Management (FMT) FMT_MOF.1/ManualUpdate Management of security functions behaviour FMT_MOF.1.1/ManualUpdate The TSF shall restrict the ability to enable the functions to perform manual updates to Security Administrators. FMT_MOF.1/Services Management of Security Functions Behaviour FMT_MOF.1.1/Services The TSF shall restrict the ability to start and stop the functions services to Security Administrators. FMT_MTD.1/CoreData Management of TSF Data FMT_MTD.1.1/CoreData The TSF shall restrict the ability to manage the TSF data to Security Administrators. FMT_MTD.1/CryptoKeys Management of TSF data FMT_MTD.1.1/CryptoKeys The TSF shall restrict the ability to manage the cryptographic keys to Security Administrators. FMT_SMF.1 Specification of Management Functions FMT_SMF.1.1 The TSF shall be capable of performing the following management functions: • Ability to administer the TOE locally and remotely; • Ability to configure the access banner; • Ability to configure the session inactivity time before session termination or locking; • Ability to update the TOE, and to verify the updates using [digital signature] capability prior to installing those updates; • Ability to configure the authentication failure parameters for FIA_AFL.1; • [ NETSCOUT Security Target Page 30 of 47 o Ability to start and stop services; o Ability to manage the cryptographic keys; o Ability to re-enable an Administrator account; o Ability to set the time which is used for time-stamps; o Ability to configure NTP; o Ability to import X.509v3 certificates to the TOE's trust store; o Ability to manage trusted public keys database;] FMT_SMR.2 Restrictions on Security Roles FMT_SMR.2.1 The TSF shall maintain the roles: • Security Administrator. FMT_SMR.2.2 The TSF shall be able to associate users with roles. FMT_SMR.2.3 The TSF shall ensure that the conditions • The Security Administrator role shall be able to administer the TOE locally; • The Security Administrator role shall be able to administer the TOE remotely are satisfied. 5.3.5 Protection of the TSF (FPT) FPT_SKP_EXT.1 Protection of TSF Data (for reading of all pre-shared, symmetric and private keys) FPT_SKP_EXT.1.1 The TSF shall prevent reading of all pre-shared keys, symmetric keys, and private keys. FPT_APW_EXT.1 Protection of Administrator Passwords FPT_APW_EXT.1.1 The TSF shall store administrative passwords in non-plaintext form. FPT_APW_EXT.1.2 The TSF shall prevent the reading of plaintext administrative passwords. FPT_TST_EXT.1 TSF testing FPT_TST_EXT.1.1 The TSF shall run a suite of the following self-tests [during initial start-up (on power on)] to demonstrate the correct operation of the TSF: [ • BIOS tests • Boot loader image verification • Cryptographic module tests]. NETSCOUT Security Target Page 31 of 47 FPT_TUD_EXT.1 Trusted update FPT_TUD_EXT.1.1 The TSF shall provide Security Administrators the ability to query the currently executing version of the TOE firmware/software and [no other TOE firmware/software version]. FPT_TUD_EXT.1.2 The TSF shall provide Security Administrators the ability to manually initiate updates to TOE firmware/software and [no other update mechanism]. FPT_TUD_EXT.1.3 The TSF shall provide means to authenticate firmware/software updates to the TOE using a [digital signature] prior to installing those updates. FPT_STM_EXT.1 Reliable Time Stamps FPT_STM_EXT.1.1 The TSF shall be able to provide reliable time stamps for its own use. FPT_STM_EXT.1.2 The TSF shall [allow the Security Administrator to set the time, synchronize time with an NTP server]. 5.3.6 TOE Access (FTA) FTA_SSL_EXT.1 TSF-initiated Session Locking FTA_SSL_EXT.1.1 The TSF shall, for local interactive sessions, [ • terminate the session] after a Security Administrator-specified time period of inactivity. FTA_SSL.3 TSF-initiated Termination FTA_SSL.3.1 The TSF shall terminate a remote interactive session after a Security Administrator-configurable time interval of session inactivity. FTA_SSL.4 User-initiated Termination FTA_SSL.4.1 Refinement: The TSF shall allow Administrator-initiated termination of the Administrator’s own interactive session. FTA_TAB.1 Default TOE Access Banners FTA_TAB.1.1 Before establishing an administrative user session the TSF shall display a Security Administrator-specified advisory notice and consent warning message regarding use of the TOE. 5.3.7 Trusted path/channels (FTP) FTP_ITC.1 Inter-TSF trusted channel NETSCOUT Security Target Page 32 of 47 FTP_ITC.1.1 The TSF shall be capable of using [TLS] to provide a trusted communication channel between itself and authorized IT entities supporting the following capabilities: audit server, [no other capabilities] that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from disclosure and detection of modification of the channel data. FTP_ITC.1.2 The TSF shall permit the TSF or the authorized IT entities to initiate communication via the trusted channel. FTP_ITC.1.3 The TSF shall initiate communication via the trusted channel for [audit server]. FTP_TRP.1 /Admin Trusted Path FTP_TRP.1.1/Admin The TSF shall be capable of using [SSH, HTTPS] to provide a communication path between itself and authorized remote Administrators that is logically distinct from other communication paths and provides assured identification of its end points and protection of the communicated data from disclosure and provides detection of modification of the channel data. FTP_TRP.1.2 /Admin The TSF shall permit remote Administrators to initiate communication via the trusted path. FTP_TRP.1.3 /Admin The TSF shall require the use of the trusted path for initial Administrator authentication and all remote administration actions. NETSCOUT Security Target Page 33 of 47 5.4 Assurance Requirements 18 The TOE security assurance requirements are summarized in Table 13. Table 13: Assurance Requirements Assurance Class Components Description Security Target Evaluation ASE_CCL.1 Conformance Claims ASE_ECD.1 Extended Components Definition ASE_INT.1 ST Introduction ASE_OBJ.1 Security Objectives for the operational environment ASE_REQ.1 Stated Security Requirements ASE_SPD.1 Security Problem Definition ASE_TSS.1 TOE Summary Specification Development ADV_FSP.1 Basic Functional Specification Guidance Documents AGD_OPE.1 Operational User Guidance AGD_PRE.1 Preparative User Guidance Life Cycle Support ALC_CMC.1 Labelling of the TOE ALC_CMS.1 TOE CM Coverage Tests ATE_IND.1 Independent Testing - conformance Vulnerability Assessment AVA_VAN.1 Vulnerability Survey 19 In accordance with section 7.1 of the CPP_ND_v2.2E, the following refinement is made to ASE: a) ASE_TSS.1.1C Refinement: The TOE summary specification shall describe how the TOE meets each SFR. In the case of entropy analysis, the TSS is used in conjunction with required supplementary information on Entropy. NETSCOUT Security Target Page 34 of 47 6 TOE Summary Specification 20 The following describes how the TOE fulfils each SFR included in section 5.3. 6.1 Security Audit 6.1.1 FAU_GEN.1 21 The TOE generates the audit records specified at FAU_GEN.1 containing fields that include the timestamp, IP address (if applicable), action, user (if applicable) and a contextual message indicating success or failure of the action. 22 The following information is logged as a result of the Security Administrator generating/importing or deleting cryptographic keys: a) Generate SSH key-pair. Action and key reference. b) Importing SSH keys. Action and key reference. c) Deleting SSH keys. Action and key reference. d) Generate Certificate Requests. Action and key reference. e) Importing Certificates. Action and certificate reference. f) Deleting Certificates. Action and certificate reference. 6.1.2 FAU_GEN.2 23 The TOE includes the user identity in audit events resulting from actions of identified users. 6.1.3 FAU_STG_EXT.1 24 Log files are transferred via TLS (see FCS_TLSC_EXT.1) to the remote audit server in real time. This prevents the audit records from unauthorized viewing and modification during transmission. 25 The TOE logs all events related to startup/shutdown, external communications, user authentication, and user management (user creation/deletion, password changes, role changes) and administrative commands in the audit log. 26 The TOE is a standalone component that stores audit data locally. Local audit data is rotated daily. The local audit record will be rotated if it exceeds at minimum 64M, otherwise it will carry into the next day. The TOE maintains at most 11 previous records and will overwrite audit records starting with the oldest audit record. 27 Only authorized administrators may view audit records and no capability to modify the audit records is provided. 6.2 Cryptographic Support 6.2.1 FCS_CKM.1 28 The TOE supports key generation for the following asymmetric schemes: a) ECC P-256/P-384/P-521. Used in SSH host key authentication and key exchange. Used in TLS key exchange. b) FFC Safe Primes. Used in SSH key exchange. NETSCOUT Security Target Page 35 of 47 6.2.2 FCS_CKM.2 29 The TOE supports the following key establishment schemes: a) ECC schemes. Used in SSH and TLS key exchange. TOE is both sender and receiver. b) FFC schemes using safe primes. Used in SSH key exchange. TOE is both sender and receiver. The following Diffie Hellman groups are supported: SSH: i) Group 14 per RFC 3526 section 3 ii) Group 16 per RFC 3526 section 5 iii) Group 18 per RFC 3526 section 7 30 Table 14 below identifies the scheme being used by each service. Table 14: Key Agreement Mapping Scheme SFR Service ECC FCS_SSHS_EXT.1 Administration FCS_TLSC_EXT.1 Audit Server FCS_TLSS_EXT.1 Administration FFC Safe Primes FCS_SSHS_EXT.1 Administration 6.2.3 FCS_CKM.4 31 Table 16 shows the origin, storage location and destruction details for cryptographic keys. Unless otherwise stated, the keys are generated by the TOE. 6.2.4 FCS_COP.1/DataEncryption 32 The TOE provides symmetric encryption and decryption capabilities using 128 and 256 bit AES in CBC, CTR and GCM mode. AES is implemented in SSH and TLS. 33 The relevant NIST CAVP certificate numbers are listed Table 4. 6.2.5 FCS_COP.1/SigGen 34 The TOE provides cryptographic signature generation and verification services using: a) RSA Signature Algorithm with key sizes of 2048, 3072 and 4096, b) ECDSA with key size of 256, 384 and 521 35 The RSA signature verification services are used in the SSH protocol, TLS Client protocol and TOE firmware integrity checks. 36 The ECDSA signature verification services are used in the SSH and TLS protocols. 37 The relevant NIST CAVP certificate numbers are listed in Table 4. NETSCOUT Security Target Page 36 of 47 6.2.6 FCS_COP.1/Hash 38 The TOE provides cryptographic hashing services using SHA-1, SHA-256, SHA-384 and SHA-512. 39 SHA is implemented in the following parts of the TSF: a) SSH; b) TLS; c) NTP; d) Digital signature verification as part of trusted update validation; and e) Hashing of passwords in non-volatile storage. 40 The relevant NIST CAVP certificate numbers are listed in Table 4. 6.2.7 FCS_COP.1/KeyedHash 41 The TOE provides keyed-hashing message authentication services using HMAC- SHA-1, HMAC-SHA-256, and HMAC-SHA-512. 42 HMAC is implemented in SSH. 43 The characteristics of the HMACs used in the TOE are given in Table 15. Table 15: HMAC Characteristics Algorithm Block Size Key Size Digest Size HMAC-SHA-1 512 bits 160 bits 160 bits HMAC-SHA-256 512 bits 256 bits 256 bits HMAC-SHA-512 1024 bits 512 bits 512 bits 44 The relevant NIST CAVP certificate numbers are listed in Table 4. 6.2.8 FCS_HTTPS_EXT.1 45 The TOE Web GUI is accessed via an HTTPS connection using the TLS implementation described by FCS_TLSS_EXT.1. The TOE does not use HTTPS in a client capacity. The TOE’s HTTPS protocol complies with RFC 2818. 46 RFC 2818 specifies HTTP over TLS. The majority of RFC 2818 is spent on discussing practices for validating endpoint identities and how connections must be setup and torn down. The TOE Web GUI operates on an explicit port designed to natively speak TLS: it does not attempt STARTTLS or similar multi-protocol negotiation which is described in section 2.3 of RFC 2818. 6.2.9 FCS_NTP_EXT.1 47 The TOE supports NTPv4 using SHA-1 authentication. 48 The TOE allows configuration of up to 3 NTP servers. 49 The TOE does not accept timestamp updates from broadcast or multicast addresses and only accepts timestamps from authenticated sources. NETSCOUT Security Target Page 37 of 47 6.2.10 FCS_RBG_EXT.1 50 The TOE contains a CTR_DRBG that is seeded from a CPU provided entropy source. Entropy from the noise is conditioned and used to seed the DRBG with 256 bits of full entropy. 51 Additional detail is provided the proprietary Entropy Description. 6.2.11 FCS_SSHS_EXT.1 52 The TOE implements SSH in compliance with RFCs 4251, 4252, 4253, 4254, 4344, 5656, 6668, 8268, 8308 section 3.1 and 8332. 53 The TOE supports password-based or public key authentication (ecdsa-sha2- nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521). In the case of public keys, the TOE authenticates the identity of the SSH client using a local database associating authorized hosts with its corresponding public key. 54 The TOE supports host key authentication algorithms ecdsa-sha2-nistp256, ecdsa- sha2-nistp384, and ecdsa-sha2-nistp521. 55 The TOE examines the size of each received SSH packet. If the packet is greater than 256 KB, it is automatically dropped. 56 The TOE utilises AES-CTR-128, AES-CTR-256, AES-GCM-128 and AES-GCM-256 for SSH encryption. 57 The TOE provides data integrity for SSH connections via HMAC-SHA1, HMAC- SHA2-256 and HMAC-SHA2-512. 58 The TOE supports ecdh-sha2-nistp256, diffie-hellman-group14-sha256, diffie- hellman-group16-sha512, diffie-hellman-group18-sha512, ecdh-sha2-nistp384 and ecdh-sha2-nistp521 for SSH key exchanges. 59 The TOE will re-key SSH connections after 1 hour of time or after an aggregate of 1 gig of data has been exchanged (whichever occurs first). 6.2.12 FCS_TLSC_EXT.1 60 The TOE implements TLS 1.2 in compliance with RFC 5246. 61 The TLS implementation supports the following ciphersuites: 62 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 63 The TOE verifies the presented identifier against the reference identifier per RFC 6215, and an IPv4 address in the SAN field. The TOE will only support a wildcard in the left-most label (e.g. *.example.com). All other usages of a wildcard will cause a failure in the connection. 64 The TOE does not implement any override mechanisms if a server certificate is invalid. 65 The TOE presents the supported elliptic curves extension with the secp256r1, secp384r1 and secp521r1 curves. This behaviour is configured when FIPS mode is enabled on the TOE during installation activities. 6.2.13 FCS_TLSS_EXT.1 66 The TOE implements TLS 1.2 in compliance with RFC 5246. NETSCOUT Security Target Page 38 of 47 67 The TLS implementation supports the following ciphersuites: 68 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 69 The TOE supports key establishment using ECDHE curves secp256r1, secp384r1, secp521r1. 70 The TLS implementation will deny connections using SSL 2.0, SSL 3.0, TLS 1.0 and TLS 1.1 71 The TOE supports session resumption through the use of session IDs according to RFC 5246 and session tickets according to RFC 5077. 72 Session tickets adhere to the structural format provided in section 4 of RFC 5077. Session tickets are encrypted using 128-bit AES in CBC mode, which is consistent with FCS_COP.1/DataEncryption. 73 An abbreviated handshake occurs only when both client and server successfully validate resumption. If the connection is suspected to be compromised, a full handshake will occur. 6.3 Identification and Authentication 6.3.1 FIA_PMG_EXT.1 74 The TOE supports the local definition of users with corresponding passwords. The passwords can be composed of any combination of upper and lower case letters, numbers, and special characters “!”, “@”, “#”, “$”, “%”, “^”, “&”, “*”, “(“, “)”. 75 The minimum password length is settable by the Administrator and can range from 7 to 72 characters. 6.3.2 FIA_UIA_EXT.1 76 The TOE requires all users to be successfully identified and authenticated before any administrative action can be taken. The TOE warning banner is displayed prior to authentication at all interfaces. 77 Administrative access to the TOE is facilitated through several interfaces: a) CLI. Administrative CLI via direct serial connection or VGA connector with a keyboard. b) SSH CLI. Administrative CLI via SSH. c) Web GUI. Administrative GUI over HTTPS/TLS. 78 The TOE uses username and password authentication at the local CLI, SSH and HTTPS WebGUI. The SSH interface additionally supports public key authentication. 6.3.3 FIA_UAU_EXT.2 79 Regardless of the interface at which the administrator interacts, the TOE prompts the user for a credential. Only after the administrative user presents the correct authentication credentials will they be granted access to the TOE administrative functionality. No TOE administrative access is permitted until an administrator is successfully identified and authenticated. 80 The TOE provides a local password-based authentication mechanism. 81 The process for authentication is the same for administrative access whether administration is occurring via direct connection or remotely. At initial login, the NETSCOUT Security Target Page 39 of 47 administrative user is prompted to provide a username. After the user provides the username, the user is prompted to provide the administrative credential associated with the user account (e.g. password or SSH public/private key response). The TOE then either grants administrative access (if the combination of username and credential is correct) or indicates that the login was unsuccessful. The TOE does not provide a reason for failure in the cases of a login failure. 6.3.4 FIA_UAU.7 82 For authentication at the local CLI the TOE provides no feedback when the administrative password is entered so that the password is obscured. 6.3.5 FIA_AFL.1 83 The TOE is capable of tracking authentication failures of remote administrators. 84 When a user account has sequentially failed authentication the configured number of times the account will be locked until a Security Administrator unlock is performed. 85 The local console does not implement the lockout mechanism. 6.3.6 FIA_X509_EXT.1/Rev 86 The TOE ensures that the X.509 certificates adhere to RFC 5280 Section 6.3 (certificate validation and certificate path validation), which can be summarized as follows: a) TOE TLS client validation of server X.509 certificates; b) When certificates are loaded into the TOE, such as when importing CAs, certificate responses and other device-level certificates c) In all scenarios, certificates are checked for several validation characteristics: d) If the certificate ‘notAfter’ date is in the past, then this is an expired certificate which is considered invalid; e) The certificate chain must terminate with a trusted CA certificate; f) Server certificates consumed by the TOE TLS client must have a Server Authentication purpose; g) OCSP certificates presented for OCSP responses must have the OCSP Signing purpose. h) The TOE validates a certificate path and treats a certificate as a CA certificate when certificates include the basicConstraints extensions and that the CA flag is set to “TRUE” for all CA certificates. 87 Certificate revocation checking for the above scenarios is performed using OCSP . 88 As X.509 certificates are not used for trusted updates, firmware integrity self-tests or client authentication, the code-signing and clientAuthentication purpose is not checked in the extendedKeyUsage for related certificates. 89 If, during the entire trust chain verification activity, any certificate under review fails a verification check, then the entire trust chain is deemed untrusted. 6.3.7 FIA_X509_EXT.2 90 The TOE has a trust store where root CA and intermediate CA certificates can be stored. The trust store is not cached: if a certificate is deleted, it is immediately NETSCOUT Security Target Page 40 of 47 untrusted. If a certificate is added to the trust store, it is immediately trusted for its given scope. 91 Instructions for configuring the trusted IT entities to supply appropriate X.509 certificates are captured in the guidance documents. 92 As part of the verification process, an OCSP responder is used to determine whether the certificate is revoked or not. If the OCSP connection cannot be established, the response is rejected and the certificate will not be accepted. 6.3.8 FIA_X509_EXT.3 93 The TOE generates Certificate Requests that provide public key, Common Name, Organization, Organizational Unit and Country information. 94 The TSF only accepts Certificate Responses with the complete certificate chain up to the Root CA, as valid. 6.4 Security Management 6.4.1 FMT_MOF.1/ManualUpdate 95 The TOE restricts the ability to perform software updates to Security Administrators. 6.4.2 FMT_MOF.1/Services 96 The TOE restricts the ability to start and stop the following services to Security Administrators: a) AED Service b) SSH c) Web GUI 97 Services are managed via the CLI. 6.4.3 FMT_MTD.1/CoreData 98 Users are required to login before being provided with access to any administrative functions. 6.4.4 FMT_SMR.2 99 The following user account is available which is a Security Administrator: a) admin. This account is used to access the CLI, SSH CLI and Web GUI. 100 Management of TSF data is restricted to Security Administrators. 6.4.5 FMT_MTD.1/CryptoKeys 101 The TOE restricts the ability to manage SSH and TLS keys to Security Administrators. 6.4.6 FMT_SMF.1 102 The TOE provides the following management capabilities: a) Ability to administer the TOE locally (serial) and remotely (SSH & HTTPS) b) Ability to configure the access banner via CLI, SSH CLI or Web GUI NETSCOUT Security Target Page 41 of 47 c) Ability to configure the session inactivity time before session termination i) The CLI / SSH CLI and Web GUI timeout value is set via the CLI or SSH CLI d) Ability to update the TOE and to verify the updates via CLI, SSH CLI e) Ability to configure the authentication failure parameters via CLI or SSH CLI f) Ability to start and stop services via CLI or SSH CLI g) Ability to manage the cryptographic keys (SSH and TLS keys) via CLI or SSH CLI h) Ability to re-enable an Administrator account via CLI i) Ability to set the time via CLI or SSH CLI. j) Ability to configure NTP via the CLI or SSH CLI k) Ability to import X.509v3 certificates to the TOE’s trust store via CLI or SSH CLI l) Ability to manage trusted public keys database via CLI or SSH CLI 6.5 Protection of the TSF 6.5.1 FPT_SKP_EXT.1 103 Keys are protected as described in Table 16. In all cases, plaintext keys cannot be viewed through an interface designed specifically for that purpose. Table 16: Keys Key Algorithm Storage Zeroization SSH Private Keys ECDSA Flash - plaintext Keys are destroyed when generating new keys by deleting the previous file with an overwrite of a pseudo-random pattern and creating a new file. Initiated via CLI command by the Security Administrator. SSH Ephemeral Keys AES / DH / ECDH RAM – plaintext OpenSSL ensures that keys (including re- keyed keys) are overwritten with random data when no longer required. TLS Private Keys ECDSA Flash – plaintext Keys are destroyed when generating new keys by deleting the previous file and creating a new file. Initiated via CLI command by the Security Administrator. TLS Ephemeral Keys AES / ECDH RAM – plaintext OpenSSL ensures that keys (including re- keyed keys) are overwritten with random data when no longer required. NTP Key SHA-1 Flash - plaintext As NTP keys are not intended to be used for encryption of sensitive information, the level of protection is different compared to other pre-shared keys NETSCOUT Security Target Page 42 of 47 Key Algorithm Storage Zeroization See TD0639 6.5.2 FPT_APW_EXT.1 104 Passwords are protected as describe in Table 17. In all cases plaintext passwords cannot be viewed through an interface designed specifically for that purpose. Table 17: Passwords Key/Password Generation/ Algorithm Storage Locally stored administrator passwords User generated Flash - SHA-512 hash 6.5.3 FPT_TST_EXT.1 105 At startup, the TOE undergoes the following tests: a) The TOE performs a file system self-test to ensure the underlying hardware does not have any anomalies that would cause the software to be executed in an unpredictable or inconsistent manner. This test calls the standard test method in the ext3 file system to check the file system data structures and confirm that they are in a consistent state. b) The TSF runs a cryptographic module integrity test as well as a cryptographic known-answer test and continuous RNG tests. These tests verify the software integrity and that the cryptographic module is operating correctly and has not been tampered with. If a cryptographic self-test fails, the device will become inoperable. The only remediation to this test failure is to call the technical support team. 106 In the event that a power on self-test fails, the boot process will terminate. The TOE will need to be rebooted to attempt to clear the error. If the TOE has been corrupted or the hardware has failed such that rebooting will not resolve the issue, a Security Administrator will need to contact NETSCOUT support. These tests and their response to failures is sufficient to ensure that the TSF behaves as described in the ST because it would detect any unauthorized modifications to the TOE, failures or tampering of the hardware (which could be an attempt to compromise its storage or take the TOE out of the range of operating conditions specified for its entropy source), and any cryptographic failures that could result in the establishment of insecure trusted channels. 6.5.4 FPT_TUD_EXT.1 107 The current firmware version may be queried using the CLI or SSH CLI. 108 Firmware upgrades are obtained from the Arbor Technical Assistance Center site (https://support.arbornetworks.com). 109 The Security Administrator manually initiates TOE updates from the SSH CLI. TOE update files must first be copied to the TOE. 110 TOE update files are digitally signed (RSA) and the signature is verified using a hardcoded public key prior to installation of the update. If verification fails, the update NETSCOUT Security Target Page 43 of 47 is aborted, an error message is displayed, and a log is generated. If verification succeeds, the installation will continue and a log is generated. 6.5.5 FPT_STM_EXT.1 111 The TOE makes use of manual time setting and NTP to maintain date and time. 112 The TOE makes use of time for the following: a) Audit record timestamps b) Session timeouts (lockout enforcement) c) Validation X.509 certificate expiration dates 6.6 TOE Access 6.6.1 FTA_SSL_EXT.1 113 The Security Administrator may configure the TOE to terminate an inactive local interactive session following a specified period of time. This is applicable to the local CLI. 6.6.2 FTA_SSL.3 114 The Security Administrator may configure the TOE to terminate an inactive remote interactive session following a specified period of time. This is applicable to the SSH CLI, and Web GUI. 6.6.3 FTA_SSL.4 115 Administrative users may terminate their own sessions at any time. Administrators terminate their CLI and SSH CLI session by executing the “exit” command. Administrators terminate their Web GUI session by clicking the “Logout” button in the UI. 6.6.4 FTA_TAB.1 116 The TOE displays an administrator configurable message to users prior to login at the CLI, SSH CLI, and Web GUI. 6.7 Trusted Path/Channels 6.7.1 FTP_ITC.1 117 The TOE supports secure communication with the following IT entities: Audit server per FCS_TLSC_EXT.1 6.7.2 FTP_TRP.1/Admin 118 The TOE provides the following trusted paths for remote administration: a) SSH CLI. Administrative CLI via SSH per FCS_SSHS_EXT.1. b) Web GUI. Administrative HTTPS web portal via TLS per FCS_TLSS_EXT.1. NETSCOUT Security Target Page 44 of 47 7 Rationale 7.1 Conformance Claim Rationale 119 The following rationale is presented with regard to the PP conformance claims: a) TOE type. As identified in section 2.1, the TOE is network device, consistent with the CPP_ND_v2.2E. b) Security problem definition. As shown in section 3, the threats, OSPs and assumptions are reproduced directly from the CPP_ND_v2.2E. c) Security objectives. As shown in section 4, the security objectives are reproduced directly from the CPP_ND_v2.2E. d) Security requirements. As shown in section 5, the security requirements are reproduced directly from the CPP_ND_v2.2E. No additional requirements have been specified. 7.2 Security Objectives Rationale 120 All security objectives are drawn directly from the CPP_ND_v2.2E. 7.3 Security Requirements Rationale All security requirements are drawn directly from the CPP_ND_v2.2E. 121 Table 18 presents a mapping between threats and SFRs as presented in the CPP_ND_v2.2E. Table 18: CPP_ND_v2.2E SFR Rationale Identifier SFR Rationale T.UNAUTHORIZED_ADMINIS TRATOR_ACCESS • The Administrator role is defined in FMT_SMR.2 and the relevant administration capabilities are defined in FMT_SMF.1 and FMT_MTD.1/CoreData, with optional additional capabilities in FMT_MOF.1/Services and FMT_MOF.1/Functions • The actions allowed before authentication of an Administrator are constrained by FIA_UIA_EXT.1, and include the advisory notice and consent warning message displayed according to FTA_TAB.1 • The requirement for the Administrator authentication process is described in FIA_UAU_EXT.2 • Locking of Administrator sessions is ensured by FTA_SSL_EXT.1 (for local sessions), FTA_SSL.3 (for remote sessions), and FTA_SSL.4 (for all interactive sessions) • The secure channel used for remote Administrator connections is specified in FTP_TRP.1/Admin NETSCOUT Security Target Page 45 of 47 Identifier SFR Rationale • (Malicious actions carried out from an Administrator session are separately addressed by T.UNDETECTED_ACTIVITY) • (Protection of the Administrator credentials is separately addressed by T.PASSWORD_CRACKING). T.WEAK_CRYPTOGRAPHY • Requirements for key generation and key distribution are set in FCS_CKM.1 and FCS_CKM.2 respectively • Requirements for use of cryptographic schemes are set in FCS_COP.1/DataEncryption, FCS_COP.1/SigGen, FCS_COP.1/Hash, and FCS_COP.1/KeyedHash • Requirements for random bit generation to support key generation and secure protocols (see SFRs resulting from T.UNTRUSTED_COMMUNICATION_CHANNELS) are set in FCS_RBG_EXT.1 • Management of cryptographic functions is specified in FMT_SMF.1 T.UNTRUSTED_COMMUNI CATION_CHANNELS • The general use of secure protocols for identified communication channels is described at the top level in FTP_ITC.1 and FTP_TRP.1/Admin; for distributed TOEs the requirements for inter-component communications are addressed by the requirements in FPT_ITT.1 • Requirements for the use of secure communication protocols are set for all the allowed protocols in FCS_DTLSC_EXT.1, FCS_DTLSC_EXT.2, FCS_DTLSS_EXT.1, FCS_DTLSS_EXT.2, FCS_HTTPS_EXT.1, FCS_IPSEC_EXT.1, FCS_SSHC_EXT.1, FCS_SSHS_EXT.1, FCS_TLSC_EXT.1, FCS_TLSC_EXT.2, FCS_TLSS_EXT.1, FCS_TLSS_EXT.2 • Optional and selection-based requirements for use of public key certificates to support secure protocols are defined in FIA_X509_EXT.1, FIA_X509_EXT.2, FIA_X509_EXT.3 T.WEAK_AUTHENTICATIO N_ENDPOINTS • The use of appropriate secure protocols to provide authentication of endpoints (as in the SFRs addressing T.UNTRUSTED_COMMUNICATION_CHANNELS) are ensured by the requirements in FTP_ITC.1 and FTP_TRP.1/Admin; for distributed TOEs the authentication requirements for endpoints in inter-component communications are addressed by the requirements in FPT_ITT.1 • Additional possible special cases of secure authentication during registration of distributed TOE components are addressed by FCO_CPC_EXT.1 and FTP_TRP.1/Join. T.UPDATE_COMPROMISE • Requirements for protection of updates are set in FPT_TUD_EXT.1 • Additional optional use of certificate-based protection of signatures can be specified using FPT_TUD_EXT.2, supported by the X.509 certificate processing requirements NETSCOUT Security Target Page 46 of 47 Identifier SFR Rationale in FIA_X509_EXT.1, FIA_X509_EXT.2 and FIA_X509_EXT.3 • Requirements for management of updates are defined in FMT_SMF.1 and (for manual updates) in FMT_MOF.1/ManualUpdate, with optional requirements for automatic updates in FMT_MOF.1/AutoUpdate T.UNDETECTED_ACTIVITY • Requirements for basic auditing capabilities are specified in FAU_GEN.1 and FAU_GEN.2, with timestamps provided according to FPT_STM_EXT.1 and if applicable, protection of NTP channels in FCS_NTP_EXT.1 • Requirements for protecting audit records stored on the TOE are specified in FAU_STG.1 • Requirements for secure transmission of local audit records to an external IT entity via a secure channel are specified in FAU_STG_EXT.1 • Optional additional requirements for dealing with potential loss of locally stored audit records are specified in FAU_STG_EXT.2/LocSpace, and FAU_STG_EXT.3/LocSpace • If (optionally) configuration of the audit functionality is provided by the TOE then this is specified in FMT_SMF.1, and confining this functionality to Security Administrators is required by FMT_MOF.1/Functions. T.SECURITY_FUNCTIONAL ITY_COMPROMISE • Protection of secret/private keys against compromise is specified in FPT_SKP_EXT.1 • Secure destruction of keys is specified in FCS_CKM.4 • If (optionally) management of keys is provided by the TOE then this is specified in FMT_SMF.1, and confining this functionality to Security Administrators is required by FMT_MTD.1/CryptoKeys • (Protection of passwords is separately covered under T.PASSWORD_CRACKING) T.PASSWORD_CRACKING • Requirements for password lengths and available characters are set in FIA_PMG_EXT.1 • Protection of password entry by providing only obscured feedback is specified in FIA_UAU.7 • Actions on reaching a threshold number of consecutive password failures are specified in FIA_AFL.1 • Requirements for secure storage of passwords are set in FPT_APW_EXT.1. T.SECURITY_FUNCTIONAL ITY_FAILURE • Requirements for running self-test(s) are defined in FPT_TST_EXT.1 NETSCOUT Security Target Page 47 of 47 Identifier SFR Rationale P.ACCESS_BANNER • An advisory notice and consent warning message is required to be displayed by FTA_TAB.1