c0341 Est
c0341 Est
Fuji Xerox
DocuCentre-IV C2263
Series Controller Software
Security Target
Version 1.0.3
-i-
- Table of Contents -
1. ST INTRODUCTION ........................................................... 1
1.1. ST Reference .............................................................................1
1.2. TOE Reference ...........................................................................1
1.3. TOE Overview ............................................................................1
1.3.1. TOE Type and Major Security Features............................................... 1
1.3.2. Environment Assumptions ...............................................................4
1.3.3. Required Non-TOE Hardware and Software ......................................... 5
1.4. TOE Description ..........................................................................6
1.4.1. User Assumptions .......................................................................... 6
1.4.2. Logical Scope and Boundary ............................................................6
1.4.3. Physical Scope and Boundary ......................................................... 14
1.4.4. Guidance .................................................................................... 15
- ii -
6. SECURITY REQUIREMENTS ...............................................27
6.1. Security Functional Requirements ............................................... 32
6.1.1. Class FAU: Security audit............................................................. 32
6.1.2. Class FCS: Cryptographic support ................................................... 37
6.1.3. Class FDP: User data protection .................................................... 38
6.1.4. Class FIA: Identification and authentication ..................................... 43
6.1.5. Class FMT: Security management ................................................... 47
6.1.6. Class FPT: Protection of the TSF ................................................... 53
6.1.7. Class FTP: Trusted path/channels ................................................. 54
6.2. Security Assurance Requirements ............................................... 55
6.3. Security Requirement Rationale .................................................. 56
6.3.1. Security Functional Requirements Rationale ..................................... 56
6.3.2. Dependencies of Security Functional Requirements ........................... 60
6.3.3. Security Assurance Requirements Rationale ..................................... 63
9. REFERENCES ..................................................................82
- iii -
- List of Figures and Tables -
Figure 1: Intended Operational Environment ........................................................4
Figure 2: MFD Units and TOE Logical Scope .......................................................... 7
Figure 3: Authentication Flow for Private Print and Mailbox ................................... 10
Figure 4: MFD Units and TOE Physical Scope ...................................................... 14
Figure 5: Assets under and not under Protection ................................................. 18
- iv -
Fuji Xerox C2263 Series Security Target
1. ST INTRODUCTION
This chapter describes Security Target (ST) Reference, TOE Reference, TOE Overview, and TOE
Description.
1.1. ST Reference
This section provides information needed to identify this ST.
TOE
Fuji Xerox DocuCentre-IV C2263 Series Controller Software.
Identification:
Version: Controller ROM Ver. 1.0.12
Manufacturer: Fuji Xerox Co., Ltd.
This TOE, categorized as an IT product, is the controller software for MFD and has copy, print, and
scan functions.
The TOE is provided as the firmware product which controls the whole MFD and protects the
following against threats: the document data stored on the internal HDD, the used document data, the
security audit log data, the document data exists on the internal network between the TOE and the
remote, and the TOE setting data. The TOE is stored on the controller ROM which is on the controller
board.
Table 1 shows the function types and functions provided by the TOE.
・ The Data Security Kit, an option, must be used to obtain the security features of the TOE.
・ Optional Fax board (out of the TOE boundary) is required to use Fax, Direct Fax, and Fax Flow
Security functions.
・ To use print, scan, and Direct Fax functions, the following items shall be installed to the external
client for general user and that for system administrator: printer driver, Network Scan Utility,
and fax driver.
・ Scan function and Control Panel function are to read the original data from IIT and store them
into Mailbox within the MFD internal HDD, according to the general user’s instruction from the
control panel.
The stored document data can be retrieved via standard Web browser by using CWIS or
Network Scan Utility.
・ Network Scan function and Control Panel function are to read the original data from IIT and
transmit the document data to FTP server, or SMB server according to the information set in the
MFD. This function is operated according to the general user’s instruction from the control
panel.
・ Fax function and Control Panel function are to send and receive fax data. According to the
general user’s instruction from the control panel to send a fax, the original data are read from IIT
and then sent to the destination via public telephone line. The document data are received from
the sender’s machine via public telephone line and then printed out from the recipient’s IOT or
stored in Mailbox.
・ The Direct Fax function is to send data from a user client to the destination via public telephone
line. The data are first sent to MFD as a print job and then to the destination without being
printed out.
security audit log data, and TOE setting data. (The following general encryption communication-
protocols are supported: SSL/TLS, IPSec, and SNMP v3.)
・ Fax Flow Security
This function prevents unauthorized access to the TOE or the internal network via Fax board
from public telephone line.
Note: The TOE does not provide the S/MIME function for E-mail and Internet Fax functions.
External
Network
MFD
System Administrator
Client Internal
Network
System - Web Browser
- ApeosWare Device TOE
Administrator
Setup
USB
Fax Board
FTP Server
SMB Server
Public
Telephone
Line
General User CE System
Administrator
(1) MFD:
The MFD has a user interface to provide MFD functions and the hardware for scan/print/copy
functions. It includes the control panel, ADF, IIT, IOT, controller board, and Fax board (option).
The OS of (2) general user client and (3) system administrator client are assumed to be Windows XP,
Windows Vista, and Windows 7.
Logical Scope
As shown in Table 3, the TOE provides the functions of control panel, copy, print, scan, network scan,
fax, Direct Fax, and CWIS to general user.
Function Description
Control Panel Control panel function is a user interface function for general user, CE, and
Function system administrator to operate MFD functions.
Copy Function Copy function is to read the original data from IIT and print them out from
IOT according to the general user’s instruction from the control panel.
When more than one copy of an original is ordered, the data read from IIT
are first stored into the MFD internal HDD. Then, the stored data are read out
from the internal HDD for the required number of times so that the required
number of copies can be made.
Print Function Print function is to print out the data according to the instruction from a
general user client. The print data created via printer driver are sent to the
MFD to be analyzed, decomposed, and printed out from IOT.
The print function is of two types: the normal print in which the data are
printed out from IOT directly after decomposed and the Store Print in which
the bitmap data are temporarily stored in the internal HDD and then printed
out from IOT according to the general user’s instruction from the control
panel.
Scan Function, Scan function is to read the original data from IIT and then store them into
Network Scan the internal HDD according to the general user’s instruction from the control
Function panel.
A general user can retrieve the stored document data from a general user
client via CWIS or Network Scan Utility.
Network scan function is to read the original data from IIT and automatically
transmit them to a general user client, FTP server, or SMB server according
to the information set in the MFD. A general user can request this function
from the control panel.
Fax Function Fax function is to send and receive fax data. According to the general user’s
instruction from the control panel to send a fax, the original data them read
from IIT and sent to the destination via public telephone line. The document
data are received from the sender’s machine via public telephone line.
Direct Fax Function Direct Fax function is to directly fax document data to the destination.
According to the instruction from a general user client to send a fax, the print
data created via fax driver are sent to the MFD, analyzed, and decomposed.
Then, the data are converted to the format for fax sending and sent to the
destination via public telephone line.
CWIS Function CWIS is to retrieve the scanned document data and the received fax data that
are stored in the internal HDD according to the instruction from Web browser
of a general user client.
CWIS also enables System Administrator’s Security Management by which a
system administrator can access and rewrite TOE setting data. For this, a
system administrator must be authenticated by his/her ID and password
entered from Web browser of a system administrator client.
Among the above functions which require user authentication, some particularly act as security
functions. The following are the security functions which prevent the unauthorized reading of
document data in the internal HDD by an attacker who is impersonating an authorized user:
・ The Store Print function (Private Print function) and the Mailbox function, which require user
authentication from the control panel,
・ The function to retrieve document data from Mailbox (Mailbox function) which requires user
authentication by using CWIS or Network Scan Utility, and the Store Print function (Private
Print function) by file designation using CWIS.
User Client
Network Scan
Printer driver Web Browser Utility
(User ID Setting) (CWIS)
TOE
Classification Authentication Authentication
Private Mailbox
Scanned Data,
Print Job Print
Received Fax Data
Mailbox Function
The scanned data and received fax data can be stored into Mailbox from IIT and Fax board which
are not shown in Figure 3.
To store the scanned data into Mailbox, a user needs to enter his/her ID and password from the
control panel. When the user is authenticated, the document data can be scanned from IIT and
stored into the internal HDD according to the user’s instruction from the control panel.
To store the received fax data into Mailbox, user authentication is not required. Among the
received fax data transmitted over public telephone line, the following data are automatically
classified and stored into each corresponding Mailbox: the received fax data whose corresponding
Mailbox is specified by the sender, the received fax data from a particular sender (the data are
classified according to the sender’s telephone number), and the received fax data from an
unknown sender.
To retrieve, print, or delete the stored data in the Personal Mailbox corresponding to the each
registered user’s ID, user authentication is required; the MFD compares the user ID and password
preset in the device against those entered by a user from the control panel, CWIS, or Network
Scan Utility.
Additionally, this TOE allows only the system administrator, who is authenticated from the
system administrator client via Web browser using CWIS, to refer to and set the following
security functions via CWIS:
・ Set the ID the password of key operator (only a key operator is privileged);
・ Refer to and set the ID of SA / general user, and set the password;
・ Refer to and set the access denial when system administrator’s authentication fails;
・ Refer to and set the limit of user password length (for general user and SA);
・ Refer to and set Audit Log;
・ Refer to and set the SSL/TLS communication;
・ Refer to and set the IPSec communication;
・ Refer to and set the SNMPv3 communication;
・ Refer to and set the SNMPv3 authentication password.
Moreover, this TOE allows only the key operator (excluding SA), who is authenticated from the
system administrator client via ApeosWare Device Setup, to refer to and set the following security
functions:
・ Set the ID and password of key operator;
・ Refer to and set the ID of SA / general user, and set the password;
・ Refer to and set the functions that use the password entered from MFD control panel in user
authentication;
・ Refer to and set User Authentication;
・ Refer to and set date and time;
System administrator shall set the following to enable security functions in 1.4.2.2.
System Administrator
Control Panel buttons, lamps, touch screen panel
General User
CE
Ethernet
ADF
Copy Hard Disk General User Client
Board Control
Data FTP Server
Panel
Scan / Overwrite SMB Server
Network Customer
Scan SEEPROM
Hard Disk Engineer
IIT Data Operation
USB (device)
Print Encryption Restriction
IIT Board General User Client
(decompos
Security (USB)
e) DRAM
Fax Flow Audit Log
Security
Fax /
Direct Fax User
IOT Authenticat
CWIS System ion
IOT Board Administrat
or’s Security Network
Data
USB (host)
Management
Protection Fax Board
(Public Telephone Line)
CPU
: TOE
Internal HDD
The MFD consists of the PWB units of controller board and control panel, IIT, and IOT,ADF.
The controller board is connected to the control panel via the internal interfaces which transmit
control data, and the controller board is connected to the Fax board, the IIT board, and IOT board via
the internal interfaces which transmit document data and control data.
The controller board is a PWB which controls MFD functions of copy, print, scan, and fax. The board
has a network interface (Ethernet) and local interfaces (USB) and is connected to the IIT board and
IOT board.
The control panel is a panel on which buttons, lamps, and a touch screen panel are mounted to use and
configure MFD functions of copy, print, scan, and fax.
The IIT (Image Input Terminal) is a device to scan an original and send its data to the controller board
for copy, scan, and fax functions.
The IOT (Image Output Terminal) is a device to output image data which was sent from the controller
board.
The ADF(Auto Document Feeder) is a device to automatically transfer original documents to IIT.
1.4.4. Guidance
The following are the guidance documents for this TOE.
・ DocuCentre-IV C2263 Administrator Guide
・ DocuCentre-IV C2263 User Guide
・ DocuCentre-IV C2263 Security Function Supplementary Guide
2. CONFORMANCE CLAIMS
2.2.1. PP Claims
There is no applicable Protection Profile.
3.1. Threats
Internal
Network Other Setting Data
Note) The data stored in a general client and server within the internal network and the general data on
the internal network are not assumed as assets to be protected. This is because TOE functions prevent
the access to the internal network from public telephone line and it cannot be a threat.
Table 4 categorizes the TOE setting data recorded on NVRAM and SEEPROM of the controller
board.
Note: The setting data other than TOE setting data are also stored on NVRAM and SEEPROM. Those
setting data, however, are not assumed as assets to be protected because they do not engage in TOE
security functions.
3.1.2. Threats
Table 5 identifies the threats addressed by the TOE. An attacker is considered to have the disclosed
information on TOE operations and low-level attack capability.
Organizational Policy
Description
(Identifier)
At the behest of the US military in Japan, it must be ensured that the
P.FAX_OPT
internal network cannot be accessed via public telephone line.
3.3. Assumptions
Table 7 shows the assumptions for the operation and use of this TOE.
Table 7: Assumptions
Assumption
Description
(Identifier)
Personnel Confidence
A system administrator shall have the necessary knowledge of TOE
A.ADMIN security functions to perform the given role of managing the TOE and
shall not operate the TOE with malicious intent.
Protection Mode
A system administrator shall configure and set the TOE properly
A.SECMODE according to the security policy of organization and the product
guidance document to manage the TOE and its external environment.
4. SECURITY OBJECTIVES
This chapter describes the security objectives for the TOE and for the environment and the rationale.
Security
Description
Objectives(Identifier)
The TOE must provide the Security Audit Log function and its log data
O.AUDITS
which are necessary to monitor unauthorized access.
The TOE must encrypt the document data, used document data, and
O.CIPHER security audit log data to be stored into the HDD so that they cannot be
analyzed even if retrieved.
The TOE must provide encryption communication function to protect the
document data, security audit log data, and TOE setting data on the
O.COMM_SEC
internal network between TOE and the remote from interception and
alteration.
The TOE must prevent the unauthorized access to the internal network via
O.FAX_SEC
Fax modem from public telephone line.
The TOE must inhibit a general user from accessing the TOE setting data.
The TOE allows only the authenticated system administrator to access the
O.MANAGE
system administrator mode which enables him/her to configure the
security functions.
The TOE must provide overwrite function to prevent the used document
O.RESIDUAL
data in the internal HDD from being reproduced or recovered.
The TOE must provide the function to identify TOE user and allow only
O.USER the authorized user to retrieve, and delete the document data and to change
the password.
O.RESTRICT The TOE must inhibit an unauthorized user from using the TOE functions.
Security
Description
Objectives(Identifier)
A system administrator who is assigned by an organization administrator
OE.ADMIN as an appropriate and reliable person for this TOE management and who
receives necessary training to manage the TOE.
A system administrator shall configure and set the TOE properly according
to the security policy of organization and the product guidance document
to manage the TOE.
OE.SEC
In addition, a system administrator shall manage the external IT
environment according to the security policy of organization and the
product guidance document.
Table 10: Assumptions / Threats / Organizational Security Policies and the Corresponding Security
Objectives
Security Problems
T.COMM_TAP
T.CONFDATA
A.SECMODE
T.DATA_SEC
T.CONSUME
T.RECOVER
P.FAX_OPT
A.ADMIN
Security Objectives
O.AUDITS
O.CIPHER
O.COMM_SEC
O.FAX_SEC
O.MANAGE
O.RESIDUAL
O.USER
O.RESTRICT
Security Problems
T.COMM_TAP
T.CONFDATA
A.SECMODE
T.DATA_SEC
T.CONSUME
T.RECOVER
P.FAX_OPT
A.ADMIN
Security Objectives
OE.ADMIN
OE.SEC
6. SECURITY REQUIREMENTS
This chapter describes the security functional requirements, security assurance requirements, and
security requirement rationale.
The terms and phrases used in this chapter are defined below.
- Subject
Term/phrase Definition
Key Operator Process Operation upon using Mailbox and Store Print when
the user authentication of key operator succeeded.
SA Process Operation upon using Mailbox and Store Print when
the user authentication of SA succeeded.
General User Process Operation upon using Mailbox and Store Print when
the user authentication of general user succeeded.
Receiving information from To receive the document data from the sender’s
public telephone line machine via public telephone line, as receiving fax
data.
Sending information to public To send the document data to the destination via public
telephone line telephone line according to the general user’s
instruction from the control panel or client PC, as
sending fax data.
Sending information to the To send the Network Scan data to the destination, a
internal network client PC, within the internal network.
Receiving information from the To receive the print data or the Direct Fax from the
internal network. sender, a client PC, within the internal network.
- Object
Term/phrase Definition
Mailbox A logical box created in the MFD internal HDD.
Mailbox can store the scanned document data or the
document data received via fax, categorizing by users
and senders.
Personal Mailbox The Mailbox privately used by a general user. Each
user can create his/her own Personal Mailbox.
Shared Mailbox The Mailbox shared by any general user. Key operator
can create the Shared Mailbox.
Store Print A print function in which bitmap data (decomposed
print data) are temporarily stored in the MFD internal
HDD and then printed out according to the
authenticated general user’s instruction from the
control panel.
Used document data stored in the The remaining data in the MFD internal HDD even
internal HDD after deletion. The document data are first stored into
the internal HDD, used, and then only their files are
deleted.
Document data Document data means all the data including image data
transmitted across the MFD when any of copy, print,
scan or fax functions is operated by a general user.
Security Audit Log The chronologically recorded data of important events
of the TOE. The events such as device failure,
configuration change, and user operation are recorded
based on when and who caused what event and its
result.
- Operation
Term/phrase Definition
Delivery MFD receives the data from public telephone line for
fax function.
Modify of behavior To change the settings of the following information:
User Authentication (Local)
Store Print (Save or Deletion of login failure job)
Internal Network Data Protection (Certificate and
encryption type)
Hard Disk Data Overwrite (number of overwrite, data
of overwrite)
Modify Changes of TSF data and security attributes (user
identifier).
- Data
Term/phrase Definition
Data on public telephone line The data which flow on public telephone line for fax
Fax data communication.
- Security attributes
Term/phrase Definition
General User role Indicates the authority required for general user to use
the TOE.
SA role Indicates the authority required for SA to use the TOE.
Key Operator role Indicates the authority required for key operator to use
the TOE.
General User identifier User ID and password used to authenticate and identify
general user.
- Other terminology
Term/phrase Definition
The Fuji Xerox’s standard The Fuji Xerox’s standard algorithm to generate a
method, FXOSENC cryptographic key. This is used when MFD is booted.
AES The FIPS-standard encryption algorithm used for
encryption/decryption of Hard Disk data.
Access denial due to When the number of unsuccessful authentication
authentication failure of system attempts of system administrator ID has exceeded the
administrator ID specified number of times, the control panel does not
accept any operation except power-on and power-off,
and ApeosWare Device Setup and the web browser do
not accept authentication operation until the MFD main
unit is powered off/on.
Data on use of password entered The data on whether to enable/disable the use of
from MFD control panel in user password to be entered from MFD control panel in user
authentication authentication. Included in the TOE setting data.
Data on ID of key operator ID data for key operator authentication. Included in the
TOE setting data.
Data on password of key operator Password data for key operator authentication.
Included in the TOE setting data.
Data on Hard Disk Data The data on whether to enable/disable the functions
Overwrite related to Hard Disk Data Overwrite. They also
incorporate the data on the number of pass (overwrite
procedure). Included in the TOE setting data.
Data on date and time The horologe information to manage log. Included in
the TOE setting data.
Public telephone line The line/network on which the data flow for fax
communication.
System Administrator mode An operation mode that enables a system administrator
to refer to and rewrite TOE setting for device operation
and that for security functions according to the
operational environment. This mode is distinguished
from the operation mode that enables a general user to
use the MFD functions.
Certificate Defined in the X.509 which is recommended by ITU-T.
The data for user authentication (name, identification
name, organization where he/she belongs to, etc.),
public key, expiry date, serial number, signature, etc.
Printer driver Software to convert the data on a general user client
into print data written in page description language
(PDL), a readable format for MFD. Used on the user
client.
Fax Driver Software for Direct Fax function, which enables a
general user to fax data to the destination directly from
a general user client through MFD. The user can send
the fax data just as printing. Used on the user client.
Network Scan Utility Software for a general user client to retrieve the
document data stored in Mailbox of MFD.
FAU_GEN.1.1 The TSF shall be able to generate an audit record of the following
auditable events:
a) Start-up and shutdown of the audit functions;
b) All auditable events for the [selection, choose one of: minimum,
basic, detailed, not specified] level of audit; and
c) [assignment: other specifically defined auditable events].
Table 12: Auditable Events of TOE and Individually Defined Auditable Events
private keys).
administrator mode
FMT_SMR.1 a) Minimal: modifications to the group of users that <Minimal>
are part of a role; Registration of system
b) Detailed: every use of the rights of a role. administrator, changes
in user registration data
(role), and deletion of
system administrator
FPT_STM.1 a) Minimal: changes to the time; <Minimal>
b) Detailed: providing a timestamp. Changes in time setting.
FTP_TRP.1 a) Minimal: Failures of the trusted path functions. <Minimal>
b) Minimal: Identification of the user associated Failure of the trusted
with all trusted path failures, if available. Communication within a
c) Basic: All attempted uses of the trusted path specified period of time,
functions. and client host data
d) Basic: Identification of the user associated with (host name or IP
all trusted path invocations, if available. address)
FAU_GEN.1.2 The TSF shall record within each audit record at least the following
information:
a) Date and time of the event, type of event, subject identity (if
applicable), and the outcome (success or failure) of the event; and
b) For each audit event type, based on the auditable event definitions of
the functional components included in the PP/ST, [assignment: other
audit relevant information].
FAU_SAR.1.1 The TSF shall provide [assignment: authorized users] with the capability
to read [assignment: list of audit information] from the audit records.
FAU_SAR.1.2 The TSF shall provide the audit records in a manner suitable for the user
to interpret the information.
FAU_SAR.1.2 The TSF shall provide the audit records in a manner suitable for the user
to interpret the information.
FAU_SAR.2.1 The TSF shall prohibit all users read access to the audit records, except
those users that have been granted explicit read-access.
FAU_STG.1.1 The TSF shall protect the stored audit records in the audit trail from
unauthorized deletion.
FAU_STG.1.2 The TSF shall be able to [selection, choose one of: prevent, detect]
unauthorized modifications to the stored audit records in the audit trail.
FAU_STG.4.1 The TSF shall [selection, choose one of: “ignore audited events”,
“prevent audited events, except those taken by the authorized user with
special rights”, “overwrite the oldest stored audit records”] and
[assignment: other actions to be taken in case of audit storage failure] if
the audit trail is full.
stored in the internal HDD and decryption of the document data and
security audit log data retrieved from the internal HDD.
FDP_ACC.1.1 The TSF shall enforce the [assignment: access control SFP] on
[assignment: list of subjects, objects, and operations among subjects and
objects covered by the SFP].
Table 13: Operations between Subjects and Objects Covered by MFD Access Control SFP
FDP_ACF.1.1 The TSF shall enforce the [assignment: access control SFP] to objects
based on the following: [assignment: list of subjects and objects
controlled under the indicated SFP, and for each, the SFP-relevant
security attributes, or named groups of SFP-relevant security attributes].
FDP_ACF.1.2 The TSF shall enforce the following rules to determine if an operation
among controlled subjects and controlled objects is allowed:
[assignment: rules governing access among controlled subjects and
controlled objects using controlled operations on controlled objects].
Rules for Mailbox Operation in the General User Process and SA Process
- Creation of Personal Mailbox
In the general user process and SA process to create Personal Mailbox, the Personal
Mailbox in which general user identifier and SA identifier are set as its owner is
created.
- Deletion of Personal Mailbox
When the general user identifier and SA identifier of the general user process and SA
process match the owner identifier of Personal Mailbox, deletion of the
FDP_ACF.1.3 The TSF shall explicitly authorize access of subjects to objects based on
the following additional rules: [assignment: rules, based on security
attributes, that explicitly authorize access of subjects to objects].
FDP_ACF.1.4 The TSF shall explicitly deny access of subjects to objects based on the
following additional rules [assignment: rules, based on security
attributes, that explicitly deny access of subjects to objects].
FDP_IFC.1.1 The TSF shall enforce the [assignment: information flow control SFP] on
[assignment: list of subjects, information, and operations that cause
controlled information to flow to and from controlled subjects covered
by the SFP].
Table 16: Subjects, Information, and Operations that cause the information to flow
FDP_IFF.1.1 The TSF shall enforce the [assignment: information flow control SFP]
based on the following types of subject and information security
attributes: [assignment: list of subjects and information controlled under
the indicated SFP, and for each, the security attributes].
FDP_IFF.1.2 The TSF shall permit an information flow between a controlled subject
and controlled information via a controlled operation if the following
rules hold: [assignment: for each operation, the security attribute-based
relationship that must hold between subject and information security
attributes].
FDP_IFF.1.3 The TSF shall enforce the [assignment: additional information flow
control SFP rules].
FDP_IFF.1.4 The TSF shall explicitly authorize an information flow based on the
following rules: [assignment: rules, based on security attributes, that
explicitly authorize information flows].
FDP_IFF.1.5 The TSF shall explicitly deny an information flow based on the
following rules: [assignment: rules, based on security attributes, that
explicitly deny information flows].
FDP_RIP.1.1 The TSF shall ensure that any previous information content of a resource
FIA_AFL.1.1(1) The TSF shall detect when [selection: [assignment: positive integer
number], an administrator configurable positive integer within
[assignment: range of acceptable values]] unsuccessful authentication
attempts occur related to [assignment: list of authentication events].
FIA_AFL.1.2 (1) When the defined number of unsuccessful authentication attempts has
been [selection: met, surpassed], the TSF shall [assignment: list of
actions].
FIA_AFL.1.1 (2) The TSF shall detect when [selection: [assignment: positive integer
number], an administrator configurable positive integer within
[assignment: range of acceptable values]] unsuccessful authentication
attempts occur related to [assignment: list of authentication events].
FIA_AFL.1.2 (2) When the defined number of unsuccessful authentication attempts has
been [selection: met, surpassed], the TSF shall [assignment: list of
actions].
FIA_AFL.1.1 (3) The TSF shall detect when [selection: [assignment: positive integer
number], an administrator configurable positive integer within
[assignment: range of acceptable values]] unsuccessful authentication
attempts occur related to [assignment: list of authentication events].
FIA_AFL.1.2 (3) When the defined number of unsuccessful authentication attempts has
been [selection: met, surpassed], the TSF shall [assignment: list of
actions].
FIA_ATD.1.1 The TSF shall maintain the following list of security attributes belonging
to individual users: [assignment: list of security attributes].
FIA_SOS.1.1 The TSF shall provide a mechanism to verify that secrets (SA password
and U.NORMAL password) meet [assignment: a defined quality metric].
FIA_UAU.1.1 The TSF shall allow [assignment: list of TSF mediated actions] on behalf
of the user to be performed before the user is authenticated.
FIA_UAU.1.2 The TSF shall require each user to be successfully authenticated before
allowing any other TSF-mediated actions on behalf of that user.
FIA_UAU.7.1 The TSF shall provide only [assignment: list of feedback] to the user
while the authentication is in progress.
FIA_UID.1.2 The TSF shall require each user to be successfully identified before
allowing any other TSF-mediated actions on behalf of that user.
FIA_USB.1.1 The TSF shall associate the following user security attributes with
subjects acting on the behalf of that user: [assignment: list of user
security attributes].
FIA_USB.1.2 The TSF shall enforce the following rules on the initial association of
user security attributes with subjects acting on the behalf of users:
FIA_USB.1.3 The TSF shall enforce the following rules governing changes to the user
security attributes associated with subjects acting on the behalf of users:
[assignment: rules for the changing of attributes].
FMT_MOF.1.1 The TSF shall restrict the ability to [selection: determine the behavior of,
disable, enable, modify the behavior of] the functions [assignment: list of
functions] to [assignment: the authorized identified roles].
enable, disable,
Store Print Key operator, SA
modify
Internal Network Data Protection enable, disable, Key operator, SA
modify
Customer Engineer Operation Restriction enable, disable Key operator, SA
Hard Disk Data Encryption enable, disable Key operator, SA
Hard Disk Data Overwrite enable, disable, Key operator, SA
modify
FMT_MSA.1.1 The TSF shall enforce the [assignment: access control SFP(s),
information flow control SFP(s)] to restrict the ability to [selection:
change default, query, modify, delete, [assignment: other operations]] the
security attributes [assignment: list of security attributes] to [assignment:
the authorized identified roles].
FMT_MSA.3.1 The TSF shall enforce the [assignment: access control SFP, information
flow control SFP] to provide [selection, choose one of: restrictive,
permissive, [assignment: other property]] default values for security
attributes that are used to enforce the SFP.
FMT_MSA.3.2 The TSF shall allow the [assignment: the authorized identified roles] to
specify alternative initial values to override the default values when an
object or information is created.
- none
FMT_MTD.1.1 The TSF shall restrict the ability to [selection: change default, query,
modify, delete, clear, [assignment: other operations]] the [assignment:
list of TSF data] to [assignment: the authorized identified roles].
FMT_SMR.1.1 The TSF shall maintain the roles [assignment: the authorized identified
roles].
FTP_TRP.1.1 The TSF shall provide a communication path between itself and
[selection: remote, local] users that is logically distinct from other
communication paths and provides assured identification of its end
points and protection of the communicated data from [selection:
modification, disclosure, [assignment: other types of integrity or
confidentiality violation]].
FTP_TRP.1.2 The TSF shall permit [selection: the TSF, local users, remote users] to
initiate communication via the trusted path.
FTP_TRP.1.3 The TSF shall require the use of the trusted path for [selection: initial
user authentication, [assignment: other services for which trusted path is
required]].
Assurance
Assurance Component Name
Requirements
Class ADV: Development
ADV_ARC.1 Security architecture description
ADV_FSP.3 Functional specification with complete summary
ADV_TDS.2 Architectural design
Class AGD: Guidance documents
AGD_OPE.1 Operational user guidance
AGD_PRE.1 Preparative procedures
Class ALC: Life-cycle support
ALC_CMC.3 Authorization controls
ALC_CMS.3 Implementation representation CM coverage
ALC_DEL.1 Delivery procedures
ALC_DVS.1 Identification of security measures
ALC_LCD.1 Developer defined life-cycle model
Class ASE: Security Target evaluation
ASE_CCL.1 Conformance claims
ASE_ECD.1 Extended components definition
ASE_INT.1 ST introduction
ASE_OBJ.2 Security objectives
ASE_REQ.2 Derived security requirements
ASE_SPD.1 Security problem definition
ASE_TSS.1 TOE summary specification
Class ATE: Tests
ATE_COV.2 Analysis of coverage
ATE_DPT.1 Testing: basic design
ATE_FUN.1 Functional testing
ATE_IND.2 Independent testing - sample
Class AVA: Vulnerability assessment
AVA_VAN.2 Vulnerability analysis
Table 23: Security Functional Requirements and the Corresponding Security Objectives
Security Objectives
O.COMM_SEC
O.RESIDUAL
O.RESTRICT
O.MANAGE
O.FAX_SEC
O.AUDITS
O.CIPHER
O.USER
Security Functional
Requirements
FAU_GEN.1
FAU_SAR.1
FAU_SAR.2
FAU_STG.1
FAU_STG.4
FCS_CKM.1
FCS_COP.1
FDP_ACC.1
FDP_ACF.1
FDP_IFC.1
FDP_IFF.1
FDP_RIP.1
FIA_AFL.1 (1)
FIA_AFL.1 (2)
FIA_AFL.1 (3)
FIA_ATD.1
FIA_SOS.1
FIA_UAU.1
FIA_UAU.7
FIA_UID.1
FIA_USB.1
FMT_MOF.1
FMT_MSA.1
Security Objectives
O.COMM_SEC
O.RESIDUAL
O.RESTRICT
O.MANAGE
O.FAX_SEC
O.AUDITS
O.CIPHER
O.USER
Security Functional
Requirements
FMT_MSA.3
FMT_MTD.1
FMT_SMF.1
FMT_SMR.1
FPT_STM.1
FTP_TRP.1
The evaluation assurance level of the TOE is EAL3 which includes the following analyses:
- Analysis of the security measures of the TOE at development phase
(Performing/analyzing systematic tests and evaluating the management of the development
environment and the developed products.)
Analysis of whether the sufficient guidance information is included so that the security functions can
be used safely. Therefore, EAL 3 is the reasonable evaluation level for this TOE.
Table 26: Security Functional Requirements and the Corresponding TOE Security Functions
Security Functions
TSF_USER_AUTH
TSF_FAX_FLOW
TSF_NET_PROT
TSF_CE_LIMIT
TSF_CIPHER
TSF_FMT
TSF_IOW
TSF_FAU
Security Functional
Requirements
FAU_GEN.1
FAU_SAR.1
FAU_SAR.2
FAU_STG.1
FAU_STG.4
FCS_CKM.1
FCS_COP.1
FDP_ACC.1
FDP_ACF.1
FDP_IFC.1
FDP_IFF.1
FDP_RIP.1
FIA_AFL.1 (1)
FIA_AFL.1 (2)
FIA_AFL.1 (3)
FIA_ATD.1
FIA_SOS.1
FIA_UAU.1
FIA_UAU.7
FIA_UID.1
FIA_USB.1
FMT_MOF.1
FMT_MSA.1
Security Functions
TSF_USER_AUTH
TSF_FAX_FLOW
TSF_NET_PROT
TSF_CE_LIMIT
TSF_CIPHER
TSF_FMT
TSF_IOW
TSF_FAU
Security Functional
Requirements
FMT_MSA.3
FMT_MTD.1
FMT_SMF.1
FMT_SMR.1
FPT_STM.1
FTP_TRP.1
The summary of each TOE security function and the corresponding security functional requirements
are described below.
stored into the internal HDD when operating any function of copy, print, scan, Network Scan, fax,
Direct Fax, or configuring various security function settings.
In addition, access to and setting change of the TOE security functions are restricted to the authorized
system administrator. A system administrator needs to enter his/her ID and password from MFD
The setting of password for key operator is limited to key operator, that for SA is limited to key
operator and SA, and that for general user is limited to system administrator and the general user
(when it is his/her own).
panel. When the user is authenticated, the data on the waiting list corresponding to the user ID are
displayed. The user can request printing or deletion of the data on the list.
b) Mailbox Function
The scanned data and received fax data can be stored into Mailbox from IIT and Fax board which
are not shown in Figure 3.
To store the scanned data into Mailbox, a user needs to enter his/her ID and password from the
MFD control panel. When the user is authenticated, the document data can be scanned from IIT
and stored into the internal HDD according to the user’s instruction from the control panel.
To store the received fax data into Mailbox, user authentication is not required. Among the
received fax data transmitted over public telephone line, the following data are automatically
classified and stored into each corresponding Mailbox: the received fax data whose corresponding
Mailbox is specified by the sender, the received fax data from a particular sender (the data are
classified according to the sender’s telephone number), and the received fax data from an
unknown sender.
To retrieve, print, or delete the stored data in the Personal Mailbox corresponding to each
registered user ID, user authentication is required; the MFD compares the user ID and password
preset in the MFD against those entered by a general user from the control panel, CWIS, or
Network Scan Utility.
key operator operates via ApeosWare Device Setup.For all Mailboxes, the key operator's
operations to delete Mailbox, and to retrieve, and delete the document data inside are allowed.
The settings of the following TOE security functions can be referred to and changed from the
control panel.
・ Refer to the setting of Hard Disk Data Overwrite, enable/disable it, and set the number of pass
(overwrite procedure);
・ Refer to the setting of Hard Disk Data Encryption and enable/disable it;
・ Set the cryptographic seed key for Hard Disk Data Encryption;
・ Refer to the setting on the use of password entered from MFD control panel in user
authentication, and enable/disable it;
・ Refer to the setting of access denial due to authentication failure of system administrator
identification, enable/disable it, and set the allowable number of the failures before access
denial;
・ Change the key operator ID and password (only a key operator is privileged);
・ Refer to the setting of access denial due to authentication failure of system administrator,
enable/disable it, and set the allowable number of failures;
・ Refer to and set the minimum password length (for general user and SA);
・ Refer to the setting of SSL/TLS communication of Internal Network Data Protection,
enable/disable it, and configure the details;
・ Refer to the setting of IPSec communication of Internal Network Data Protection, enable/disable
it, and configure the details;
・ Refer to the setting of User Authentication and select disable/Local Authentication, and
configure the details;
With CWIS function, the settings of the following TOE security functions can be referred to and
changed from a system administrator client via Web browser.
・ Change the key operator ID and password (only a key operator is privileged);
・ Refer to the setting of ID of SA and general user and change the ID and password;
・ Refer to the setting of access denial due to authentication failures of system administrator,
enable/disable it, and set the allowable number of the failures before access denial;
・ Refer to and set the minimum password length (for general user and SA);
・ Refer to the setting of Security Audit Log and enable/disable it,
(When Security Audit Log is enabled, security audit log data can be downloaded in the form of
tab-delimited text to a system administrator client.);
・ Refer to the setting of SSL/TLS communication of Internal Network Data Protection,
enable/disable it, and configure the details;
・ Refer to the setting of IPSec communication of Internal Network Data Protection, enable/disable
it, and configure the details;
・ Refer to the setting of SNMP v3 communication of Internal Network Data Protection,
enable/disable it, and configure the details;
・ Set the authentication password for SNMPv3 communication;
・ Download/upload and create an X.509 certificate;
・ Refer to the setting of User Authentication and select disable/Local Authentication, and
configure the details;
This TOE allows only the key operator (exc. SA) who is authenticated from system administrator
client via ApeosWare Device Setup to refer to and set the following security functions.
・ Change the key operator ID and password;
・ Refer to the setting of ID of SA and general user and change the ID and password;
・ Refer to and set the setting on the use of password entered from MFD control panel in user
authentication;
・ Refer to the setting of User Authentication and select disable/Local Authentication, and
configure the details;
・ Refer to and set date and time;
The auditable events are recorded with the following fixed size entries:
- Log ID: consecutive numbers as an audit log identifier (1 - 60000)
- Date: date data (yyyy/mm/dd, mm/dd/yyyy, or dd/mm/yyyy)
- Time: time data (hh:mm:ss)
- Logged Events: event name (arbitrary characters of up to 32 digits)
- User Name: user name (arbitrary characters of up to 32 digits)
- Description: description on events
(arbitrary characters of up to 32 digits, see below for details)
- Status: status or result of event processing
(arbitrary characters of up to 32 digits, see below for details)
- Optionally Logged Items: additional information recorded to audit log
(except common record items)
- 73 – Copyright 2012 by Fuji Xerox Co., Ltd.
Fuji Xerox C2263 Series Security Target
The document data, security audit log data, and TOE setting data are protected by the encryption
communication protocol that ensures secure data communication between the TOE and IT
products (communication service via Web, communication service for printer driver,
communication service for fax driver, communication service for network utility, communication
service for ApeosWare Device Setup, and other services which require trusted path). This trusted
path is logically distinct from other communication paths and provides assured identification of
its endpoints and protection of the communication data from modification or disclosure.
a) SSL/TLS
According to the SSL/TLS communication which is configured by a system administrator using
the system administrator mode, SSL/TLS ensuring secure data transmission is supported. This
protects the security of document data, security audit log data, and TOE setting data on the
internal network.
By supporting SSL/TLS, the TOE can act as SSL/TLS server or SSL/TLS client. Moreover,
SSL/TLS can protect data transmission between the TOE and the remote from interception and
alteration. Protection from interception is realized by encrypting transmission data with the
following cryptographic keys. A cryptographic key is generated at the time of starting a session
and lost at the time of ending the session or powering off the MFD main unit.
Cryptographic key generated as SSLv3/TLSv1/TLSv1.2 upon every session.
Specifically, one of the cryptographic suites below is adopted:
Protection from the alteration is realized by HMAC (Hashed Message Authentication Code -
IETF RFC 2104) of SSL/TLS.
When SSL/TLS communication is enabled on the Web client, requests from the client must be
received via HTTPS. The SSL/TLS communication needs to be enabled before IPSec, or
SNMPv3 is enabled or before security audit log data are downloaded by a system administrator.
b) IPSec
According to the IPSec communication which is configured by a system administrator using the
system administrator mode, IPSec ensuring secure data transmission is supported. This protects
the security of document data, security audit log data, and TOE setting data on the internal
network.
IPSec establishes the security association to determine the parameters (e.g. private key and
cryptographic algorithm) to be used in the IPSec communication between the TOE and the
remote. After the association is established, all transmission data among the specified IP
addresses are encrypted by the transport mode of IPSec until the TOE is powered off or reset. A
cryptographic key is generated at the time of starting a session and lost at the time of ending the
session or powering off the MFD main unit.
Cryptographic key generated as IPSec (ESP: Encapsulating Security Payload) at every session
Specifically, one of the following combinations between secret-key cryptographic method and
hash method is adopted:
c) SNMPv3
According to the SNMP v3 communication which is configured by a system administrator using
the system administrator mode, SNMP v3 is supported. This is one of the security solutions for
the network management protocol, SNMP. As defined in IETF RFC3414, SNMP v3 is used for
not only data encryption but also authentication of each SNMP message.
To enable this function, both authentication password and privacy password need to be set up in
both the TOE and the remote server. Length of both passwords must be 8 characters or more.
Authentication of SNMP v3 uses SHA-1 hash function; encryption of the protocol uses
CBC-DES. A cryptographic key is generated at the time of starting a session and lost at the time
of ending the session or powering off the MFD main unit.
8.1. Acronyms
The following acronyms are used in this ST:
Acronym Definition
ADF Auto Document Feeder
CC Common Criteria
CE Customer Engineer / Customer Service Engineer
CWIS CentreWare Internet Service
DRAM Dynamic Random Access Memory
EAL Evaluation Assurance Level
FIPS PUB Federal Information Processing Standard publication
IIT Image Input Terminal
IOT Image Output Terminal
IT Information Technology
IP Internet Protocol
MFD Multi Function Device
NVRAM Non Volatile Random Access Memory
PDL Page Description Language
PP Protection Profile
SAR Security Assurance Requirement
SEEPROM Serial Electronically Erasable and Programmable Read Only Memory
SFP Security Function Policy
SFR Security Functional Requirement
SMTP Simple Mail Transfer Protocol
SOF Strength of Function
ST Security Target
TOE Target of Evaluation
TSF TOE Security Function
8.2. Terminology
The following terms are used in this ST:
Term Definition
Any entity outside the TOE who interacts with the TOE: i.e. general user,
User
system administrator, and CE.
System Administrator A user authorized by key operator to manage MFD maintenance and
Privilege (SA) configure TOE security functions.
An authorized user who manages MFD maintenance and configures TOE
System Administrator
security functions. This term covers both key operator and SA.
Customer Engineer
Customer service engineer, an engineer who maintains and repairs MFD.
(CE)
Attacker A malicious user of TOE
A panel of MFD on which buttons, lamps, and a touch screen panel are
Control Panel
mounted to operate the MFD
General User Client A client for general user.
System Administrator A client for system administrator. An administrator can refer to and rewrite
Client TOE setting data of MFD via Web browser and ApeosWare Device Setup.
CWIS is a service on a Web server in the TOE to confirm the status of the
CentreWare Internet
TOE, change settings of the TOE, and request retrieval and printing of
Service
documents toward the TOE via the Web browser of the user client.
(CWIS)
CWIS can be used via the Windows standard Web browser.
Software for a key operator to conduct settings and management of
multiple MFDs from the system administrator client. It enables reference
ApeosWare Device
and editing of registration information such as user information, access
Setup
restriction, mailbox, address book, and job flow, and also the basic device
information in a list.
An operation mode that enables a system administrator to refer to and
System Administrator rewrite TOE setting for device operation and that for security functions
Mode according to the operational environment. This mode is distinguished from
the operation mode that enables a general user to use the MFD functions.
Software for Direct Fax function, which enables a general user to fax data
Fax Driver to the destination directly from a general user client through MFD. The
user can send the fax data just as printing. Used on the user client.
Software for a general user client to retrieve the document data stored in
Network Scan Utility
Mailbox of MFD.
Software to convert the data on a general user client into print data written
Printer driver in page description language (PDL), a readable format for MFD. Used on
the user client.
Print Data The data written in PDL, a readable format for MFD, which are to be
Term Definition
converted into bitmap data by the TOE decompose function.
The data that are transmitted by command and response interactions. This
Control Data
is one the type of the data transmitted between MFD hardware units.
The decomposed data of the data read by the copy function and the print
data transmitted from a user client to MFD by the print function. Bitmap
Bitmap Data
data are stored into the internal HDD after being compressed in the unique
process.
A function to analyze and convert the print data written in PDL into
Decompose Function
bitmap data.
To analyze and convert the data written in PDL into bitmap data by the
Decompose
decompose function.
Original Texts, images and photos to be read from IIT in the copy function.
Document data means all the data, including images, transmitted across
the MFD when any of copy, print, scan or fax functions is used by a
general user. The document data includes:
- Bitmap data read from IIT and printed out from IOT (copy function),
- Print data sent by general user client and its decomposed bitmap data
Document Data (print function),
- Bitmap data read from IIT and then stored into the internal HDD (scan
function),
- Bitmap data read from IIT and sent to the fax destination and the bitmap
data faxed from the sender’s machine and printed out from the recipient’s
IOT (fax function).
The remaining data in the MFD internal HDD even after deletion. The
Used Document Data document data are first stored into the internal HDD, used, and then only
their files are deleted.
The chronologically recorded data of important events of the TOE. The
Security Audit Log
events such as device failure, configuration change, and user operation are
Data
recorded based on when and who caused what event and its result.
The data which are stored in a general user client or in the general client
Internally Stored Data
and server, but do not include data regarding TOE functions.
The data on the internal network. The general data do not include data
General Data
regarding TOE functions.
The data which are created by the TOE or for the TOE and may affect the
TOE operations. Specifically, they includes the information regarding the
functions of Hard Disk Data Overwrite, Hard Disk Data Encryption,
TOE Setting Data System Administrator’s Security Management, Customer Engineer
Operation Restriction, Use of password entered from MFD control panel
in user authentication, ID and password of system administrator, access
denial due to authentication failure of system administrator, Internal
Term Definition
Network Data Protection, Security Audit Log, Mailbox, and User
Authentication.
General Client and
Client and server which do not directly engage in TOE operations
Server
Deletion from the internal HDD means deletion of the management
information. When deletion of document data from the internal HDD is
Deletion from the requested, only the management information corresponding to the data is
Internal Hard Disk deleted. Therefore, user cannot access the document data which were
Drive (HDD) logically deleted. However, the document data themselves are not deleted
but remain as the used document data until new data is written in the same
storage area.
To write over the area of the document data stored in the internal HDD
Overwrite
when deleting the data.
The 12 alphanumeric characters to be entered by a user. When data in the
Cryptographic Seed
internal HDD are encrypted, a cryptographic key is generated based on the
Key
cryptographic seed key.
The 256-bit data which is automatically generated based on the
Cryptographic Key cryptographic seed key. Before the data are stored into the internal HDD,
they are encrypted with the cryptographic key.
Network A general term to indicate both external and internal networks.
The network which cannot be managed by the organization that manages
External Network
the TOE. This does not include the internal network.
Channels between MFD and highly reliable remote server / client PC. The
channels are located in the network of the organization, the owner of the
Internal Network
TOE, and are protected from the security risks coming from the external
network.
A function to limit the accessible TOE functions by identifying the user
User Authentication
before he/she uses each TOE function.
A mode to manage user authentication of the TOE using the user
Local Authentication
information registered in the MFD.
9. REFERENCES
The following documentation was used to prepare this ST.