Archived U.S. Government Approved Protection Profile - US Government Protection Profile Wireless Local Area Network (WLAN) Client for Basic Robustness Environments, Version 1.1
Short Name: pp_wlan_cli_br_v1.1
Technology Type: Wireless LAN
CC Version: 3.1
Date: 25 July 2007
Preceded By: pp_wlan_cli_br_v1.0
Sunset Date: 01 September 2011
Conformance Claim: EAL2 Augmented
Please note: This serves as an addendum to the VR for the Original Evaluated PP
This PP specifies the DoD‘s information security needs for a Basic Robustness WLAN Client. It is expected that the wireless client will be a component in a larger system (for example, a wireless card installed in a laptop computer). This PP requires privacy and integrity of communications over the WLAN using commercially available cryptographic algorithms. Security administration is the responsibility of the user of each component (i.e., client). The assurance requirements defined in section 5.3 provide a minimal level of assurance for basic robustness environments; these include EAL2 Security Assurance Requirements (SARs) augmented with FLC_FLR.2 (Flaw Reporting Procedures).
This PP defines:
- assumptions about the security aspects of the environment in which the TOE will be used;
- threats that are to be addressed by the TOE;
- security objectives of the TOE and its environment;
- functional and assurance requirements to meet those security objectives; and
- rationale demonstrating how the requirements meet the security objectives, and how the security objectives address the threats.
The evaluation of the U. S. Government Wireless LAN Client Protection Profile for Basic Robustness Environments, Version 1.0 provides specification for environments in which TOEs with various levels of robustness are appropriate to meet Basic Robustness level of independently assured security requirements. The assurance requirements were chosen to be consistent with this goal.
July 25, 2007
Assurance maintenance has been performed on this protection profile to update it to the common criteria version 3.1. This update caused a change in version number (from 1.0 to 1.1) that indicates an update has occurred. The updates included revisions based on the assurance requirements of the CC 3.1, removal of FPT_SEP and FPT_RVM since it is now covered by ADV_ARC and replacement of Explicitly stated requirements with Extended requirements (only the nomenclature changed and not the requirements.) Cryptographic functional requirements were also revised to reflect the latest updated standards.
This U.S. Government Approved Protection Profile is not assigned to any Validated Products
Please forward any questions or comments to firstname.lastname@example.org