Technical data

Brocade Communications Systems, Inc. Page 41 of 48
8. Rationale
This section provides the rationale for completeness and consistency of the Security Target. The rationale addresses
the following areas:
• Security Objectives;
• Security Functional Requirements;
• Security Assurance Requirements;
• Requirement Dependencies;
• TOE Summary Specification; and,
• PP Claims.
8.1 Security Objectives Rationale
This section shows that all secure usage assumptions, organizational security policies, and threats are completely
covered by security objectives. In addition, each objective counters or addresses at least one assumption,
organizational security policy, or threat.
8.1.1 Security Objectives Rationale for the TOE and Environment
This section provides evidence demonstrating the coverage of organizational policies and usage assumptions by the
security objectives.
O.ACCESS
O.ADMIN_ROLE
O.AUDIT_GNEERATION
O.MANAGE
O.TOE_PROTECTION
O.
USER_AUTHENTICATION
O.
USER_IDENTIFICATION
OE.CONFIG
OE.NETWORK
OE.PHYCAL
T.ACCOUNTABILITY
x
T.ADMIN_ERROR
x
x
T.MASQERADE
x
x
T.TSF_COMPROMISE
x
T.UNAUTH_ACCESS
x
A.LOCATE
x
A.NETWORK
x
A.NO_EVIL
x
Table 4 Environment to Objective Correspondence
8.1.1.1 T.ACCOUNTABILITY
A user may not be held accountable for their actions.