IEEE 2600.1-2009 pdf free

IEEE 2600.1-2009 pdf free.IEEE Standard for a Protection Profile in Operational Environment A.
IEEE 2600.1 is for a Protection Profile for Hardcopy Devices in a restrictive commercial information processing environment in which a relatively high level of document security, operational accountability, and information assurance are required. The typical information processed in this environment is trade secret, mission critical, or subject to legal and regulatory considerations, such as for privacy or governance. This environment is not intended to support life-critical or national security applications. This environment will he known as ‘Operational Environment A.”
1.2 Purpose
The purpose of this standard is to create a security Protection Profile (PP) for Hardcopy Devices in Operational Environment A as defined in IEEE Std 26OOIM2OO8.
1.3 Application notes
Application notes are provided where they may contribute to the reader’s understanding. These notes. while not part of the fiirmal 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.
1.4 Notational conventions
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 are set in all caps (for example, ‘DSR”).
c) In tables that describe Security Objectives rationale, a checkrnark (“) 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 bold 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.
1) In specifications of Security Functional Requirements (SFRs):
I) 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) Bold 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.1 pdf free download.