
Cisco Intrusion Prevention System Security Target
Exceptions to
Shall/Shall Not
Statement(s)
with Unilateral Key
Confirmation Provided
by U to V
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.5 C(1, 2) Scheme
with Unilateral Key
Confirmation Provided
by V to U
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.6 C(1, 2) Scheme
with Bilateral Key
Confirmation
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.7 C(1, 1) Scheme
with Unilateral Key
Confirmation Provided
by V to U
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.8 C(0, 2) Scheme
with Unilateral Key
Confirmation Provided
by U to V
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.9 C(0, 2) Scheme
with Unilateral Key
Confirmation Provided
by V to U
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.10 C(0, 2) Scheme
with Bilateral Key
Confirmation
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
7.3 NIST Special Publication 800-56B
The TOE is compliant with NIST SP 800-56B as described in Table 26 below.
Table 26 800-56B Compliance
Shall/Shall Not
Statement(s)
This column does not included “should/should not” statements that relate to the “owner”, “recipient”,
“application”, or “party” as they are outside of the scope of the TOE.
Kommentare zu diesen Handbüchern