IEEE 2600.2-2009 pdf free.IEEE Standard Protection Profile for Hardcopy Devices in IEEE Std 2600TM -2008 Operational Environment B.
This standard is for a Protection Profile for Hardcopy Devices in a commercial information processing environment in which a moderate level of document security, network security, and security assurance are required. Typically, the day-to-day proprietary and nonproprietary information needed to operate an enterprise will be handled by this environment. This environment will be known as “Operational Environment B.”
1.2 Purpose
The purpose of this standard is to create a security Protection Profile (PP) for Hardcopy Devices in Operational Environment B as defined in IEEE Std
1.3 Application notes
Application notes are provided where they may contribute to the rcadcr’s understanding. These notes. while not part of the formal statement of this Protection Profile, are included as an acknowledgment of the diverse uses of this document and are intended to provide guidance to its users.
The following notational conventions are used throughout this standard:
a) Defined terms in full form are set in title case (for example, ‘Document Storage and Retrieval”).
b) Defined terms in abbreviated form arc set in all caps (for example. ‘4DSR”).
c) In tables that describe Security Objectives rationale, a checkmark (v”) placed at the intersection of a row and column indicates that the threat identified in that row is wholly or partially mitigated by the objective in that column.
d) In tables that describe completeness of security requirements. a bold typeface letter “P” placed at the intersection of a row and column indicates that the requirement identified in that row performs a principal fulfillment of the objective indicated in that column. A letter ‘S” in such an intersection indicates that it performs a supporting fulfillment.
e) In tables that describe the sufficiency of security requirements, a hold typeface requirement name and purpose indicates that the requirement performs a principal fulfillment of the objective in the same row. Requirement names and purposes set in normal typeface indicate that those requirements perform supporting fulfillments.
f) In specifications of Security Functional Requirements (SFRs):
1) Bold typeface indicates the portion of an SFR that has been completed or refined in this Protection Profile, relative to the original SFR definition in Common Criteria Part 2 or an Extended Component Definition.
2) Italic typeface indicates the portion of an SFR that must be completed by the ST Author in a conforming Security Target.
3) RaId italic typeface indicates the portion of an SFR that has been partially completed or refined in this Protection Profile, relative to the original SFR definition in Common Criteria Part 2 or an Extended Component Definition, but which also must be completed by the ST Author in a conforming Security Target.IEEE 2600.2 pdf download.