The TOE Cisco Web Security Appliance (WSA) is an appliance that monitors HTTP/HTTPS network traffic, analyzes the monitored network traffic using various techniques, and reacts to identified threats associated with web traffic (such as blacklisted urls and inappropriate or malicious content).
\r\nThe TOE can optionally connect to an NTP server on its internal network for time services. Also, if the WSA is to be remotely administered, then the management station must be connected to an internal network, SSHv2 must be used to remotely connect to the appliance. A syslog server is also used to store audit records. If these servers are used, they must be attached to the internal (trusted) network. The internal (trusted) network is meant to be separated effectively from unauthorized individuals and user traffic; one that is in a controlled environment where implementation of security policies can be enforced.
","evaluation_configuration":"\r\n\r\nThe TOE consists of one or more appliances and includes the Cisco AsyncOS software version 10.5. The hardware is comprised of the following S690, S690X, S680, S670, S390, S380, S370, S190, S170, S100v, S300v running on Cisco UCS servers (blade or rack-mounted). The TOE includes both software and hardware.
","security_evaluation_summary":"\r\n\r\nThe evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Cisco Email Security Appliance was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 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 rev 4. Acumen Security determined that the evaluation assurance level (EAL) for the product is EAL 1. The product, when delivered configured as identified in the Cisco Email Security Appliance CC Configuration Guide, satisfies all of the security functional requirements stated in the Cisco Email Security Appliance Security Target. The project underwent CCEVS Validator review. The evaluation was completed in June 2017. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe TOE is comprised of several security features. Each of the security features identified above consists of several security functionalities, as identified below.
\r\nThese features are described in more detail in the subsections below. In addition, the TOE implements all RFCs of the NDcPP v1.0 as necessary to satisfy testing/assurance measures prescribed therein.
\r\nSecurity Audit
\r\nThe Cisco Web Security Appliance provides extensive auditing capabilities. The TOE can audit events related to cryptographic functionality, identification and authentication, and administrative actions. The Cisco Web Security Appliance generates an audit record for each auditable event. Each security relevant audit event has the date, timestamp, event description, and subject identity. The administrator configures auditable events, performs back-up operations, and manages audit data storage. The TOE provides the administrator with a circular audit trail or a configurable audit trail threshold to track the storage capacity of the audit trail. Audit logs are backed up over an encrypted channel to an external audit server.
\r\n\r\nThe TOE provides cryptography in support of other Cisco WSA security functionality. This cryptography has been validated for conformance to the requirements of FIPS 140-2 Level 1. The entropy source provides 256 bits of entropy used to seed the RNG. After cryptographic keys are used, they are zeroized.
\r\n| \r\n Algorithm \r\n | \r\n\r\n Cert. # \r\n | \r\n
| \r\n AES \r\n | \r\n\r\n 4561, 4680 \r\n | \r\n
| \r\n HMAC \r\n | \r\n\r\n 3013, 3096 \r\n | \r\n
| \r\n DRBG \r\n | \r\n\r\n 1509, 1583 \r\n | \r\n
| \r\n ECDSA \r\n | \r\n\r\n 1113, 1155 \r\n | \r\n
| \r\n RSA \r\n | \r\n\r\n 2488, 2553 \r\n | \r\n
| \r\n SHA \r\n | \r\n\r\n 3739, 3831 \r\n | \r\n
| \r\n CVL \r\n | \r\n\r\n 1244, 1325 \r\n | \r\n
The TOE provides cryptography in support of remote administrative management via SSHv2. The cryptographic services provided by the TOE are described in Table 7 below.
\r\n| \r\n Cryptographic Method \r\n | \r\n\r\n Use within the TOE \r\n | \r\n
| \r\n Secure Shell Establishment (SSH) \r\n | \r\n\r\n Used to establish initial SSH session. \r\n | \r\n
| \r\n Transport Layer Security (TLS) \r\n | \r\n\r\n Used in TLS session establishment. \r\n | \r\n
| \r\n AES \r\n | \r\n\r\n Used to encrypt TLS session traffic. \r\nUsed to encrypt SSH session traffic. \r\n | \r\n
| \r\n ECDH \r\n | \r\n\r\n Used to provide key exchange in SSH \r\n | \r\n
| \r\n RSA Signature Services \r\n | \r\n\r\n Used in TLS session establishment. \r\nUsed in SSH session establishment. \r\nX.509 certificate signing \r\n | \r\n
| \r\n HMAC \r\n | \r\n\r\n Used for keyed hash, integrity services in TLS an SSH session establishment. \r\n | \r\n
| \r\n DRBG \r\n | \r\n\r\n Used for random number generation \r\nUsed in TLS session establishment. \r\nUsed in SSH session establishment. \r\n | \r\n
| \r\n SHA \r\n | \r\n\r\n Used to provide TLS traffic integrity verification \r\n | \r\n
\r\n
Identification and Authentication
\r\nThe TOE performs user authentication for the Authorized Administrator of the TOE. The TOE provides authentication services for administrative users wishing to connect to the TOE’s secure CLI and GUI administrative interfaces. Prior to an administrator logging in, a login banner is presented at both the CLI and GUI. The TOE requires Authorized Administrators to authenticate prior to being granted access to any of the management functionality.
\r\nThe TOE can be configured to require a minimum password length of 15 characters as well as mandatory password complexity rules that includes special characters. The TOE provides administrator authentication against a local user database. Password-based authentication can be performed on the serial console or remote interfaces. The SSHv2 interface also supports authentication using SSH keys. The remote GUI is protected using TLS.
\r\nSecurity Management
\r\nThe TOE provides secure administrative services for management of general TOE configuration and the security functionality provided by the TOE. All TOE administration occurs either through a secure SSHv2 session or via a local console connection. The TOE provides the ability to securely manage:
\r\n· All TOE administrative users;
\r\n· All identification and authentication;
\r\n· All audit functionality of the TOE;
\r\n· All TOE cryptographic functionality;
\r\n· The timestamps maintained by the TOE;
\r\n· Updates to the TOE; and
\r\n· TOE configuration file storage and retrieval.
\r\nThe TOE provides capabilities to manage its security functions, and controls access to those capabilities through the use of administrative roles with varying security management authorizations.
\r\nAdministrators can create configurable login banners to be displayed at time of login, and can also define an inactivity timeout for each admin interface to terminate sessions after a set period of inactivity.
\r\nProtection of the TSF
\r\nThe TOE protects against interference and tampering by untrusted subjects by implementing identification, authentication, and access controls to limit configuration to Authorized Administrators. The TOE prevents reading of cryptographic keys and passwords.
\r\nThe TOE internally maintains the date and time. This date and time is used as the timestamp that is applied to audit records generated by the TOE. Administrators can update the TOE’s clock manually, or can optionally configure the TOE to use NTP to synchronize the TOE’s clock with an external time source. Finally, the TOE performs testing to verify correct operation of the appliance itself and that of the cryptographic module.
\r\nThe TOE is able to verify any software updates prior to the software updates being installed on the TOE to avoid the installation of unauthorized software.
\r\nTOE Access
\r\nThe TOE is able to download software updates from the Update Server. The TOE can terminate inactive sessions after an Authorized Administrator configurable time-period. Once a session has been terminated the TOE requires the user to re-authenticate to establish a new session.
\r\nThe TOE can also display an Authorized Administrator specified banner on the CLI and GUI management interfaces prior to allowing any administrative access to the TOE. Administrators are able to exit their own administrator sessions.
\r\nTOE Access
\r\nThe TOE allows trusted paths to be established to itself from remote administrators over SSHv2 for remote CLI access and HTTPS for remote GUI access. The TOE can push log files to an external syslog server using SCP over SSH.
","features":[]}