
Cisco Intrusion Prevention System Security Target
Exceptions to
Shall/Shall Not
Statement(s)
6.3.1 dhStatic, C(0, 2,
FFC DH)
6.3.2 Static Unified
Model, C(0, 2, ECC
CDH)
TOE does not use ECC.
TOE would use C(2,0)
6.3.3 Rationale in
Choosing a C(0, 2)
Scheme
7. DLC-Based Key
Transport
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.1 Assurance of
Possession
Considerations when
using Key Confirmation
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.2 Unilateral Key
Confirmation for Key
Agreement Schemes
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.3 Bilateral Key
Confirmation for Key
Agreement Schemes
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4 Incorporating Key
Confirmation into a Key
Agreement Scheme
Key confirmation for the
C(2, 0) key agreement
schemes is not specified,
since neither party has a
static key pair
8.4.1 C(2, 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.2 C(2, 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.3 C(2, 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
Comentarios a estos manuales