Specifications

OE.TOE_NO_BYPASS

Wireless clients are configured so that information cannot flow

between a wireless client and any other wireless client or host

networked to the TOE without passing through the TOE.

OE.TIME_STAMPS

The TOE IT environment shall provide reliable time stamps

and the capability for the administrator to set the time used for

these time stamps.

OE.CLIENT_PROTECT

Wireless clients and/or their hosts will be configured to not

allow unauthorized access to networking services of the

wireless client or to stored TOE authentication credentials.

6 Security Requirements

This section identifies the Security Functional Requirements for the TOE and for the IT

Environment. The Security Functional Requirements included in this section are derived

verbatim from Part 2 of the Common Criteria for Information Technology Security

Evaluation, version 3.1 revision 3.

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.

 Assignments: indicated by showing the value in square brackets [Assignment_value].

 Selections: indicated by italicized text.

 Assignments within selections: indicated in italics within the [greater brackets].

 Refinements: indicated in bold text with the addition of details and bold text with

strikethrough (refinement) when details are deleted.

Multiple Security Functional Requirement instances (iterations) are identified by the Security

Functional Requirement component identification followed by the instance number in

parenthesis (e.g.,FCS_CKM.1(1)) and the Security Functional Requirement element name

followed by the instance number in parenthesis (e.g., FCS_CKM.1.1(1)).

Operations already completed within the Protection Profile (US Government Wir eless Local

Area Network (WLAN) Access System Protection Profile for Basic Robustness

Environments, July 25 2007, version 1.1) will not be repeated here in the Security Target.

Please see the PP for these details. Therefore, the SFR operations from CC Part 2 that have

already been completed in the PP will not show the font conventions in the bullet list above.

Extended SFRs are identified by having a label 'Extended component SFR for the TOE' after

the requirement name for TOE SFRs.

The TOE security requirements described below are consistent with those of the WLAN PP

except as noted in the listing of TOE Security Functional Requirement Additions in section 3

above.