Tenable Nessus Network Monitor (NNM) is a software product that is designed to passively collect traffic data from environmental networks for analysis.
\r\nNNM also connects to an environmental instance of Tenable.sc (SecurityCenter) which serves as a single point to aggregate and analyze data collected from various Tenable applications, including NNM.
\r\nThe evaluated version of Tenable Nessus Network Monitor is supported on Red Hat Enterprise Linux 7 and Windows Server 2016.
","evaluation_configuration":"","security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme for the Protection Profile for Application Software, Version 1.3 and Functional Package for Transport Layer Security (TLS), Version 1.1. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 release 5. The product, when delivered configured as identified in the guidance document, satisfies all of the security functional requirements stated in the Tenable Nessus Network Monitor Security Target. The evaluation was completed in December 2020. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"Timely Security Updates
\r\nThe TOE developer has internal mechanisms for receiving reports of security flaws, tracking product vulnerabilities, and distributing software updates to customers in a timely manner.
\r\nCryptographic Support
\r\nThe TOE implements cryptography to protect data at rest and in transit.
\r\nThe TOE stores credential data and passphrase data encrypted using AES or a password-based key derivation function (PBKDF), depending on the data that is being stored.
\r\nFor data in transit, the TOE implements TLS/HTTPS as a server. The TOE implements a TLS server for its administrative interface and to receive communications from other Tenable components in its operational environment. The TOE supports mutual authentication as a TLS server for all uses.
\r\nThe TOE implements all cryptography used for these functions with NIST-approved algorithms. The TOE’s DRBG is seeded using entropy from the underlying OS platform.
\r\nUser Data Protection
\r\nThe TOE uses cryptographic mechanisms to protect sensitive data at rest. The key used by the TOE to encrypt and decrypt sensitive data is cryptographically protected by the TOE platform.
\r\nThe TOE relies on the network connectivity and system log capabilities of its host OS platform. The TOE supports user-initiated, externally initiated, and application-initiated uses of the network.
\r\nIdentification and Authentication
\r\nThe TOE supports X.509 certificate validation as part of establishing TLS and HTTPS connections. The TOE supports various certificate validity checking methods and can also check certificate revocation status using OCSP. If the validity status of a certificate cannot be determined, the certificate will be accepted. All other cases where a certificate is found to be invalid will result in rejection without an administrative override.
\r\nSecurity Management
\r\nThe TOE itself and the configuration settings it uses are stored in locations recommended by the platform vendor.
\r\nThe TOE includes a web GUI that enforces username/password authentication using locally-stored credentials that are created using the TOE. The TOE does not provide a default user account to access its management interface.
\r\nThe security-relevant management functions supported by the TOE relate to configuration of transmission of system data (through collection of network traffic).
\r\nPrivacy
\r\nThe TOE does not handle Personally Identifiable Information (PII) of any individuals.
\r\nProtection of the TSF
\r\nThe TOE enforces various mechanisms to prevent itself from being used as an attack vector to its host OS platform. The TOE: implements address space layout randomization (ASLR); does not allocate any memory with both write and execute permissions; does not write user-modifiable files to directories that contain executable files; is compiled using stack overflow protection; and is compatible with the security features of its host OS platform.
\r\nThe TOE contains libraries and invokes system APIs that are well-known and explicitly identified.
\r\nThe TOE has a mechanism to determine its current software version. Software updates to the TOE can be acquired by leveraging its OS platform. All updates are digitally signed to guarantee their authenticity and integrity.
\r\nTrusted Path/Channels
\r\nThe TOE encrypts sensitive data in transit between itself and its operational environment using TLS and HTTPS. It facilitates the transmission of sensitive data from remote users over TLS and HTTPS.
","features":[]}