
Cisco Intrusion Prevention System Security Target
5 SECURITY REQUIREMENTS
This section identifies the Security Functional Requirements for the TOE. The Security
Functional Requirements included in this section are derived from Part 2 of the Common Criteria
for Information Technology Security Evaluation, Version 3.1, Revision 4, dated: September 2012
and all international interpretations.
5.1 Conventions
The CC defines operations on Security Functional Requirements: assignments, selections,
assignments within selections and refinements. This document uses the following font
conventions to identify the operations defined by the CC:
Where operations were completed in the NDPP itself, the formatting used in the NDPP
has been retained;
Assignment: Indicated with italicized text, which may or may not be bracketed;
Refinement made by PP author: Indicated with bold text; may have Refinement: at the
beginning of the element for further clarification.
Selection: Indicated with underlined text, which may or may not be bracketed;
Iteration: Indicated by appending the iteration number in parenthesis, e.g., (1), (2), (3).
Explicitly stated SFRs are identified by having a label ‘EXT’ after the requirement name for
TOE SFRs.
5.2 TOE Security Functional Requirements
This section identifies the Security Functional Requirements for the TOE. The TOE Security
Functional Requirements that appear in the following table are described in more detail in the
following subsections.
Table 16: Security Functional Requirements
Reproduced from the U.S. Government Protection Profile for Security Requirements for Network Devices
User Identity Association
External Audit Trail Storage
FCS: Cryptographic support
Cryptographic Key Generation (for asymmetric keys)
Cryptographic Key Zeroization
Cryptographic Operation (for data
encryption/decryption)
Cryptographic Operation (for cryptographic
signature)
Cryptographic Operation (for cryptographic hashing)
Cryptographic Operation (for keyed-hash message
authentication)
Kommentare zu diesen Handbüchern