Cisco Cat4K NDPP ST
11 March 2014
EDCS-1228241
25
1.7.1 Security Audit
The TOE generates a comprehensive set of audit logs that identify specific TOE
operations. For each event, the TOE records the date and time of each event, the type of
event, the subject identity, and the outcome of the event. Auditable events include: failure
on invoking cryptographic functionality; establishment, termination and failure of an
IPsec SA; establishment, termination and failure of an SSH session; modifications to the
group of users that are part of the authorized administrator roles; all use of the user
identification mechanism; any use of the authentication mechanism; any change in the
configuration of the TOE; detection of replay attacks, changes to time, initiation of TOE
update, indication of completion of TSF self-test, maximum sessions being exceeded,
termination of a remote session and attempts to unlock a termination session; and
initiation and termination of a trusted channel.
The TOE is configured to transmit its audit messages to an external syslog server.
Communication with the syslog server is protected using IPsec and the TOE can
determine when communication with the syslog server fails. If that should occur, the
TOE can be configured to block new permit actions.
The logs can be viewed on the TOE using the appropriate IOS commands. The records
include the date/time the event occurred, the event/type of event, the user associated with
the event, and additional information of the event and its success and/or failure. The
TOE does not have an interface to modify audit records, though there is an interface
available for the authorized administrator to clear audit data stored locally on the TOE.
1.7.2 Cryptographic Support
The TOE provides cryptography support for secure communications and protection of
information when configured in FIPS mode of operation. The crypto module is FIPS
140-2 SL2 validated. The cryptographic services provided by the TOE include:
symmetric encryption and decryption using AES; digital signature using RSA;
cryptographic hashing using SHA1; keyed-hash message authentication using HMAC-
SHA1, and IPsec for authentication and encryption services to prevent unauthorized
viewing or modification of data as it travels over the external network. The TOE also
implements SSHv2 secure protocol for secure remote administration. In the evaluated
configuration, the TOE must be operated in FIPS mode of operation per the FIPS
Security Policy (certificate 1940).
1.7.3 User Data Protection
The TOE supports routing protocols including BGPv4, EIGRP, EIGRPv6 for IPv6,
RIPv2, and OSPFv2 to maintain routing tables, or routing tables can configured and
maintained manually (‘static routes’). Since routing tables are used to determine
which egress ACL is applied to the outbound traffic, the authority to modify the
routing tables is restricted to authenticated administrators, and authenticated neighbor
routers. The only aspect of routing protocols that is security relevant in this TOE is
the TOE’s ability to authenticate neighbor routers using shared passwords. Other
