19.06.2014 Views

Xerox WorkCentre 5632/5638/5645/5655 - Common Criteria

Xerox WorkCentre 5632/5638/5645/5655 - Common Criteria

Xerox WorkCentre 5632/5638/5645/5655 - Common Criteria

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Xerox</strong> <strong>WorkCentre</strong> <strong>5632</strong>/<strong>5638</strong>/<strong>5645</strong>/<strong>5655</strong>/5665/5675/5687<br />

Multifunction Systems Security Target<br />

5. SECURITY<br />

REQUIREMENTS<br />

This section defines the IT security requirements that shall be satisfied by the TOE or its<br />

environment:<br />

The CC divides TOE security requirements into two categories:<br />

<br />

<br />

Security functional requirements (SFRs) (such as, identification and<br />

authentication, security management, and user data protection) that the TOE and<br />

the supporting evidence need to satisfy to meet the security objectives of the<br />

TOE.<br />

Security assurance requirements (SARs) that provide grounds for confidence<br />

that the TOE and its supporting IT environment meet its security objectives (e.g.,<br />

configuration management, testing, and vulnerability assessment).<br />

These requirements are discussed separately within the following subsections.<br />

5.1. Conventions<br />

All operations performed on the Security Functional Requirements or the Security<br />

Assurance Requirements need to be identified. For this purpose the following<br />

conventions shall be used.<br />

<br />

<br />

<br />

<br />

<br />

Assignments will be written in normal text with brackets: [normal]<br />

Selections will be written in underlined and italic text<br />

Refinements will be written bold<br />

Iterations will be performed on components and functional elements. The<br />

component ID defined by the <strong>Common</strong> <strong>Criteria</strong> (e.g. FDP_IFC.1) will be<br />

extended by an ID for the iteration (e.g. “(SSL)”). The resulting component ID<br />

would be “FDP_IFC.1 (SSL)”.<br />

Where an iteration is identified in rationale discussion as “all”, the statement<br />

applies to all iterations of the requirement (e.g. “FCS_COP.1 (all)”)<br />

5.2. Security Policies<br />

35<br />

Copyright 2009 <strong>Xerox</strong> Corporation, All rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!