IEEE 2600-2008 - IEEE Standard for Information Technology: Hardcopy Device and System Security

Standard Details

This standard defines security requirements (all aspects of security including but not limited to authentication, authorization, privacy, integrity, device management, physical security, and information security) for manufacturers, users, and others on the selection, installation, configuration, and usage of hardcopy devices (HCDs) and systems, including printers, copiers, and multifunction devices (MFDs), and the computer systems that support these devices. This standard identifies security exposures for these HCDs and systems, and instructs manufacturers and software developers on appropriate security capabilities to include in their devices and systems, and instructs users on appropriate ways to use these security capabilities.

Sponsor Committee	C/CPSC - Cybersecurity and Privacy Standards Committee
Status	Active
Board Approval	2008-03-27
History	Published Date:2008-06-30

Additional Resources Details

Pars	Approved PAR

Working Group Details

Working Group	2600_WG - Hardcopy Device and System Security Working Group
Working Group Chair	Don Wright
Sponsor Committee	C/CPSC - Cybersecurity and Privacy Standards Committee
Society	C - IEEE Computer Society
IEEE Program Manager	Tom Thompson
Existing Standards	Active 2600.1-2009 - IEEE Standard for a Protection Profile in Operational Environment A Standard 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. 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 be known as ?Operational Environment A.?. The PDF of this standards is available at no cost compliments of the IEEE GET program http://ieeexplore.ieee.org/servlet/opac?punumber=5075669)
	Active 2600.2-2009 - IEEE Standard Protection Profile for Hardcopy Devices in IEEE Std 2600-2008 Operational Environment B Standard 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 non-proprietary information needed to operate an enterprise will be handled by this environment. This environment will be known as Operational Environment B. <br><br> The "IEEE Get Program" grants public access to view and download individual PDFs of select standards at no charge. Visit <a href="http://standards.ieee.org/about/get/index.html" target="_blank">http://standards.ieee.org/about/get/index.html</a> for details.
	Active 2600.3-2009 - IEEE Standard Protection Profile for Hardcopy Devices in IEEE Std 2600-2008 Operational Environment C Standard for a Protection Profile for Hardcopy Devices in a public-facing environment in which document security is not guaranteed, but access control and usage accounting are important to the operator of the environment. A retail copy center, public library, Internet caf?, and hotel business center are typical applications of this environment. This environment will be known as ?Operational Environment C.? An errata is available for this standard at http://standards.ieee.org/findstds/errata/2600.3.pdf
	Active 2600.4-2010 - IEEE Standard Protection Profile for Hardcopy Devices in IEEE Std 2600(TM)-2008 Operational Environment D Standard for a Protection Profile for Hardcopy Devices in a small, private information processing environment in which most elements of security are provided by the physical environment, but basic network security is needed to protect the device and its network from misuse from outside of the environment. Small offices and home offices are typical applications of this environment. This environment will be known as ?Operational Environment D.