The NIKSUN NetDetector/NetVCR 10440 (also known as the NetDetector) sends information about detected events to NetOmni for data aggregation and to provide real-time network-wide analysis. NetDetector accomplishes this by providing security monitoring of network traffic using IDS methods and statistical anomaly detection in order to safeguard networks against cyber-attacks.
","evaluation_configuration":"\r\n\r\nThe TOE is the NIKSUN NetDetector/NetVCR 10440 appliance, running the NIKSUN NetDetector/NetVCR Everest software version 5.1.2.0.
\r\nThe following lists components and applications in the environment that the TOE relies upon in order to function properly:
\r\nThe evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) processes and procedures. NetDetector was evaluated against the criteria contained in the Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 4. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 Revision 4. The product, when installed and configured per the instructions provided in the preparative guidance, satisfies all of the security functional requirements stated in the NIKSUN NetDetector/NetVCR 10440 Security Target Version 1.0. The evaluation underwent CCEVS Validator review. The evaluation was completed in August 2018. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, CCEVS-VR-VID10869-2018 prepared by CCEVS.
","environmental_strengths":"\r\n\r\nSecurity Audit
\r\nAudit records are generated for various types of management activities and events. These records include the date and time stamp of the event, the event type, and the subject identity. Audit records are stored as syslog records on the TOE, and can be configured to also be sent to a Syslog Server via a TLS connection. When the storage space allocated to specific audit record types is exhausted, the TOE will overwrite the oldest relevant log file.
\r\nCryptographic Support
\r\nThe TOE relies on its NIKOS FIPS Object Module 2.0.16 (derived from OpenSSL FIPS Object Module 2.0.7) cryptographic module to implement cryptographic methods and trusted channels. Cryptographic keys are generated using the CTR_DRBG provided through this module. The TOE destroys all plaintext secrets and private keys.
\r\nSSH is used to secure the remote CLI interface for remote management of the TOE. SSH is also used to secure the communication with the SCP Server when the TOE receives software image updates. The TOE uses TLS to secure the automatic transfer of audit records to the Syslog Server, and for connection to the LDAP/AD Server for remote authentication. When a user utilizes the “Forgot Username/Password” feature on the NetDetector/NetVCR login screen, NetDetector/NetVCR will send an email to the SMTP Server over a protected TLS channel. TLS/HTTPS is used to secure the connection for remote management of the TOE via the web GUI as well as connections to NetOmni devices. The TOE will deny any connections for disallowed protocols and invalid X.509v3 certificates.
\r\nIdentification and Authentication
\r\nThe TOE verifies the identity of users connecting to the TOE. All users must be identified and authenticated before being allowed to perform actions on the TOE. This is true of users accessing the TOE via the local console, or through protected paths using the remote CLI via SSH or the web GUI via TLS 1.2. Users can authenticate to the TOE using a username and password. In addition, when authenticating by the remote CLI, users can instead use SSH public-key authentication. LDAP can be configured to provide external authentication for the GUI.
\r\nThe TOE uses X.509v3 certificates to perform server side authentication of Syslog Server, SMTP Server and LDAP/AD Server and present its certificate to NetOmni for authentication. The TSF determines the validity of the certificates by confirming the validity of the certificate chain, and verifying that the certificate chain ends in a trusted Certificate Authority (CA). The TSF connects with a CRL distribution point through HTTP to confirm certificate validity and to access certificate revocation lists (CRL).
\r\nSecurity Management
\r\nThe TOE has a role based authentication system where roles (permissions) are assigned to groups for the web GUI. Authorized actions for a particular user are dependent on which group they are assigned to. There are 4 initial groups: Administrator, Account Administrator, Advanced Users, and Users. Only users assigned to the Administrator group are capable of performing SFR related management functions via the web GUI and thus, are Security Administrators in the context of the evaluation. The VCR user is the Security Administrator user for the remote and local CLI, and is able to update the TOE’s software and verify it via published hash.
\r\nProtection of the TSF
\r\nThe TOE stores passwords in a variety of locations depending on their use and encryption. They cannot be viewed by any user regardless of the user’s role. Pre-shared keys, symmetric keys, and private keys cannot be accessed in plaintext form by any user. There is an underlying hardware clock that is used for accurate timekeeping and is set by the Security Administrator. Power-on self-tests are executed automatically when the cryptographic module is loaded into memory. It verifies its own integrity using an HMAC-SHA-256 digest computed at build time and also tests all algorithms for integrity. The TOE also performs self-tests on the CPU, RAM, and disk components. The TOE’s DRBG also performs its own health tests.
\r\nThe version of the TOE is verified via the CLI or web GUI. The TOE is updated by the VCR user via the CLI. Updated software images are downloaded to the SCP Server and are transferred to the TOE via the SCP using SSH. The administrator is also capable of copying the image to a CD and manually loading it to the TOE. The TOE conducts a hash verification on the system image using SHA-256 against the known hash to ensure the integrity of the update.
\r\nTOE Access
\r\nBefore any user authenticates to the TOE, the TOE displays a configurable Security Administrator banner for the web GUI. The local and remote CLI interfaces display the default Linux security banner prior to authentication that is also configurable. The TOE can terminate local CLI, remote CLI, and web GUI sessions after a specified time period of inactivity. Administrator users have the capability to terminate their own sessions.
\r\nTrusted Path/Channels
\r\nThe TOE connects and sends data to IT entities that reside in the Operational Environment via trusted channels. In the evaluated configuration, the TOE connects to Syslog Server via TLS to send audit data for remote storage. TLS is used for the TOE’s connection with the SMTP Server to send secure email. TLS is also used for the TOE’s connection with the LDAP/AD Server for its remote authentication store. TLS/HTTPS is used for the transfer of data to the NetOmni appliance. TLS/HTTPS and SSH are used for remote administration of the TOE via the web GUI and remote CLI respectively.
","features":[]}