Konica Minolta Bizhub 450i/360i/300i With FK514
Konica Minolta Bizhub 450i/360i/300i With FK514
Security Target
Version: 2.00
Issued on:December 21, 2020
Created by:KONICA MINOLTA, INC
―【Table of Contents】--
1. ST Introduction ........................................................................................................................................ 6
ST Reference ........................................................................................................................................................... 6
TOE Reference ........................................................................................................................................................ 6
TOE Overview......................................................................................................................................................... 6
1.3.1. Type of TOE .........................................................................................................................................................................6
1.3.2. Usage and Main Security Functions ...................................................................................................................................6
1.3.3. Operating environment ........................................................................................................................................................7
1.3.4. Necessary Hardware/Software for the TOE ........................................................................................................................8
TOE Description ...................................................................................................................................................... 9
1.4.1. Physical Scope of the TOE ..................................................................................................................................................9
1.4.2. Logical scope of the TOE ..................................................................................................................................................10
1.4.3. Glossary ............................................................................................................................................................................12
2. Conformance Claims ............................................................................................................................. 16
CC Conformance Claims ...................................................................................................................................... 16
PP Claim ................................................................................................................................................................ 16
PP Conformance Rationale ................................................................................................................................... 16
3. Security Problem Definition ................................................................................................................. 17
Users ...................................................................................................................................................................... 17
Assets ..................................................................................................................................................................... 17
3.2.1. User Data ..........................................................................................................................................................................17
3.2.2. TSF Data ...........................................................................................................................................................................17
Threat Definitions.................................................................................................................................................. 18
Organizational Security Policy Definitions .......................................................................................................... 18
Assumption Definitions ......................................................................................................................................... 19
4. Security Objectives ................................................................................................................................ 20
Definitions of Security Objectives for the Operational Environment................................................................... 20
5. Extended components definition .......................................................................................................... 21
FAU_STG_EXT Extended: External Audit Trail Storage .................................................................................... 21
FAU_CKM_EXT Extended: Cryptographic Key Management ........................................................................... 21
FCS_IPSEC_EXT Extended: IPsec selected ........................................................................................................ 22
FCS_RBG_EXT Extended: Cryptographic Operation (Random Bit Generation)................................................ 24
FDP_FXS_EXT Extended: Fax Separation .......................................................................................................... 25
FIA_PMG_EXT Extended: Password Management ............................................................................................. 26
FIA_PSK_EXT Extended: Pre-Shared Key Composition .................................................................................... 26
FPT_SKP_EXT Extended: Protection of TSF Data.............................................................................................. 27
FPT_TST_EXT Extended: TSF testing ................................................................................................................ 28
FPT_TUD_EXT Extended: Trusted Update ....................................................................................................... 29
6. Security Requirements .......................................................................................................................... 31
Security Functional Requirements ........................................................................................................................ 31
6.1.1. Mandatory Requirements ..................................................................................................................................................31
6.1.2. Conditionally Mandatory Requirements ...........................................................................................................................45
6.1.3. Selection-based Requirements ...........................................................................................................................................45
Security Assurance Requirements ......................................................................................................................... 47
Security Requirements Rationale .......................................................................................................................... 47
6.3.1. The dependencies of security requirements .......................................................................................................................47
―【Table of figures】---
Figure 1-1 TOE's operating environment ................................................................................................................... 7
Figure 1-2 The logical scope of TOE ....................................................................................................................... 10
―【Table of Contents】--
1. ST Introduction
ST Reference
・ ST name : KONICA MINOLTA bizhub 450i/bizhub 360i/bizhub 300i with FK-514,
DEVELOP ineo 450i/ineo 360i/ineo 300i with FK-514 Security Target
・ ST version : 2.00
・Created on : December 21, 2020
・Created by : KONICA MINOLTA, INC.
TOE Reference
・ TOE name : KONICA MINOLTA bizhub 450i/bizhub 360i/bizhub 300i with FK-514,
DEVELOP ineo 450i/ineo 360i/ineo 300i with FK-514
・ Version : G00-31
The physical components of the TOE are the MFP body and the FAX kit. “KONICA MINOLTA bizhub
450i/bizhub 360i/bizhub 300i with FK-514” is equipped with FAX kit (product name FK-514, corresponding
identification information A883) on the MFP body (KONICA MINOLTA bizhub 450i, KONICA MINOLTA
bizhub 360i, KONICA MINOLTA bizhub 300i, and its version (AC770Y0-F000-G00-31)). “DEVELOP ineo
450i/ineo 360i/ineo 300i with FK-514” is equipped with FAX kit (product name FK-514, corresponding
identification information A883) on the MFP body (DEVELOP ineo 450i, DEVELOP ineo 360i, DEVELOP ineo
300i, and its version (AC770Y0-F000-G00-31)).
TOE Overview
(3) LAN
Network used for the TOE setup environment
(5) Firewall
Device for protecting against the network attacks to intra-office LAN from the internet
(6) Client PC
By connecting to the LAN, this works as the client of the TOE. The user can access TOE from the client
PC and operate the following by installing the printer driver in the client PC.
・Accumulation, Print of electronic documents
Also, the user can access TOE from the client PC and operate the following by installing the Web
browser in the client PC.
・WC
TOE Description
This paragraph explains the overview of the physical scope and logical scope of the TOE.
ineo 300i
bizhub 650i/550i/450i User’s Guide 1.00 Japanese exe file Customer engineer
bizhub 360i/300i User’s Guide 1.00 Japanese (*2) (CE) bring. (*1)
(with
bizhub 650i/550i/450i User's Guide 1.00 English
FULL digital
bizhub 360i/300i User’s Guide 1.00 English
signature)
ineo 650i/550i/450i User's Guide 1.00 English
ineo 360i/300i User’s Guide 1.00 English
Security bizhub 650i/550i/450i/360i/300i User's exe file Customer engineer
1.02 Japanese
Functions Guide Security Functions (*3) (CE) bring. (*1)
(*1) Customer engineer delivers the guidance corresponding to the MFP (FULL and Security Functions).
Japanese/English is at the purchaser’s request.
(*2) Obtain html file by executing the exe file.
(*3) Obtain pdf file by executing the exe file.
from the printer driver or WC of the client PC. In addition, electronic documents can be
temporarily saved from the WC to the password encrypted PDF user box. When a user
prints an electronic document that has been temporarily saved from the operation
panel, the relevant electronic document is deleted from the TOE.
2 Scan function This function scans paper documents, creates electronic documents, and sends them
(e-mail, WebDAV, SMB) through the user's operation from the operation panel.
3 Copy function This function scans paper documents and copies scanned images through the user's
operation from the operation panel.
4 Fax function This function sends and receives documents through Public switched telephone
network (PSTN) by using standard facsimile protocol.
・ Fax TX function
This function specifies a destination from the operation panel, scans paper documents,
creates electronic documents, and sends them to the specified external fax machine.
Electronic documents stored in the personal user box can also be sent by fax from the
operation panel.
・ Fax RX function
Function to receive electronic documents through the telephone line from the external
fax.
5 Document Storage and This function stores electronic documents in Personal user box, Memory RX user box
retrieval function and Password Encrypted PDF used box or retrieve the stored electronic documents
To personal user box, this function can store the electronic documents by scanning and
converting a paper document, can store the electronic document from the printer driver
or WC of a client PC and can store the Fax document with F code by Fax RX function.
This function can store the fax documents received by the fax function in Memory RX
user box. For Password encrypted PDF user box, electronic documents can be stored
from the WC of the client PC.
Electronic documents stored in personal user box can be printed, sent files to SMTP
server/WebDAV server/SMB server, and Fax TX from the operation panel. Also, it can
be sent files to SMTP server/WebDAV server/SMB server, and downloaded from the
WC. Electronic documents stored in Memory RX user box can be printed from the
operation panel and downloaded from the WC. Electronic documents stored in
Password encrypted PDF user box can be stored to personal user box from the
operation panel.
identification and authentication of the user, when accessing the Memory RX user box
(except Fax RX). There are two types of Authentication Method: MFP authentication
method that TOE itself identifies and authenticates, and External server authentication
method using external authentication server. This function includes the following
functions.
- Function to stop the authentication when the number of continuous
authentication failures reaches to the setting value.
- Function to display the input password in dummy characters at login.
- Function to register only password that satisfy the condition of minimum
character of password, set by administrator for protecting the password
quality.
- Function to terminate that session when no operation is performed for a
certain period of time (the time set by the administrator) by the user who is
identified and authenticated.
2 Access control function This function restricts the access to the assets in the TOE only to the permitted users.
3 Encryption function Encryption function that prevents access to data assets during the communication
through LAN. The effectiveness of data encryption is assured by the use of
internationally accepted encryption algorithms.
4 Trusted communications The function to prevent information leakage due to wiretapping on a network when
function using a LAN. Encrypt the communication data between the client PC, SMTP server,
external authentication server, DNS server, log server, WebDAV server, SMB server
and TOE. Protects the protected assets flowing over the network by the encryption
function (No.3). This function ensures that the communication takes place between
known terminations.
5 Security management The function that ensures that only users who have administrator role (U.ADMIN)
function authenticated by the identification and authentication function can set and refer to the
TOE security function.
6 Audit function The function that records logs of events related to TOE use and security (hereinafter
referred to as "audit events") together with date and time information as audit log data.
The log file is sent to the log server using the trusted communication function and can
be viewed by the log server.
7 Trusted operation function The function (update function) that verifies the authenticity of the firmware to be
updated and verifies that the firmware is legitimate before the TOE starts firmware
update. The function (self-test function) to ensure that TOE operation is not interrupted
due to detectable failures, etc.
8 FAX separation function The function that ensures that the TOE Fax I/F cannot be used to generate a data bridge
between the PSTN and the LAN.
1.4.3. Glossary
The meanings of terms used in this ST are defined.
Designation Definition
Electronic document An electronic document is a document data that digitized information such as characters
and figures.
Paper document A paper document is a paper document that contains information such as characters and
figures.
Accumulated document An electronic document (Subject to storage and retrieval operations) that is to be stored
and retrieved.
Fax document Documents sent and received to external fax via public line by fax function.
Job Document processing task sent to hard copy device. Single processing task can process
more than one document.
WC Web Connection.
Function/Interface to operate TOE through the Web browser of the client PC.
Operation panel The control device for operating TOE. Consists of touch panel liquid crystal displays.
Scanner unit A device to read graphics and photographs from paper document and convert them into
electronic data by TOE.
Printer unit A device to print out image data converted for printing by TOE.
Controller unit A device to control TOE.
Firmware Software to control TOE.
CPU Central Processing Unit
RAM A volatile memory used as a working area.
SPI Flash Field-nonreplaceable nonvolatile memory that stores TSF data that decides TOE
operation.
SSD Field-nonreplaceable storage medium of 250GB. Stores the firmware, the language data
of each countries to display the response to access through the operation panel and
network, TOE setting data, electronical documents as a file.
Ethernet I/F The interface for connecting the TOE and LAN. 10BASE-T, 100BASE-TX, and Gigabit
Ethernet are supported.
USB I/F The interface for connection the TOE and USB device.
RS-232C I/F An interface that can be serially connected to the TOE via the D-sub9 pin. Customer
engineer shall use this for the maintenance function when TOE fails.
SMB TX A function that converts scanned data, electronic documents stored in TOE, etc. into
computer-handled files and sends them to public folders on computers and servers.
WebDAV TX A function that converts scanned data, electronic documents stored in TOE, etc. into
computer-handled files and uploads them to a WebDAV server. It is also used for when
sending the log to the log server.
User Box A function to store user document data and user job data in TOE for Print function, Fax
function, and Document Storage and retrieval function. During operation, ID & Print user
box, Password encrypted PDF user box, Memory RX user box, and Personal user box are
available.
ID & Print user box Electronic documents are temporarily saved when a normal user performs the print
function from the printer driver or WC of the client PC. The normal user can print
electronic documents temporarily saved from the operation panel.
Password encrypted PDF user Electronic documents are temporarily saved when a normal user prints or saves a
box password-encrypted PDF from the WC of the client PC. The normal user can print or store
electronic documents temporarily saved from the operation panel.
Designation Definition
Memory RX user box Stores the fax document with no F-code received by Fax function. This function can be
used when the administrator has enabled Memory RX in the memory RX setting (enabled
during operation). Also, it is protected by the Memory RX user box password set by the
administrator in the memory RX setting. Normal user who knows the memory RX user box
password can retrieve fax documents from the operation panel and the WC of the client
PC.
Personal user box Normal users can store electronic documents from the operation panel, the printer driver or
the WC of the client PC into their own personal user box. If F-code is specified for the job
received by the fax function, the fax document is saved in the specified user box. The
normal users can retrieve electronic documents from the operation panel or the WC of the
client PC form their own personal user box.
Confidential RX This function saves the fax document with the specified F-code received by the fax
function in the personal user box. Normal users and administrators who own the personal
user box can set passwords for confidential RX and set valid/invalid for each personal user
box.
F-code Consists of SUB address and sender ID. When sending a fax to the personal user box
that confidential RX is set to be valid, enter the registered No. of the relevant personal
user box and the password for confidential RX as the SUB address and sender ID of
the F-code.
Role Role of security relevant that is associated with a user when logs in. TOE has the role of
normal user (U.NORMAL) and built-in administrator (U.BUILTIN_ADMIN).
Normal User User authorized to use TOE as normal user (U.NORMAL). When a user successfully logs
(U.NORMAL) in with a user name, user password, and without administrator rights, it is identified as a
normal user (U.NORMAL). Functions provided on the user screen are available.
Administrator User authorized to use TOE as administrator (U.ADMIN). The TOE administrators are the
(U.ADMIN) user administrator (U.USER_ADMIN) and built-in administrator (U.BUILTIN_ADMIN)
depending on the login method. The security management function provided on the
administrator screen can be used.
User administrator When a user successfully logs in with a user name, user password, and administrator
(U.USER_ADMIN) rights, it is identified as a user administrator (U.USER ADMIN).
Built-in administrator User who knows the administrator password. When a user successfully logs in with an
(U.BUILTIN_ADMIN) administrator password, it is identified as a built-in administrator (U.BUILTIN_ADMIN).
Customer Engineer User who knows the service password. When a user successfully logs in with a service
password, the function provided on the service screen can be used. Supports the TOE
installation and trouble.
User ID Identification to which the TOE identifies the user. If the user successfully logs in, it is
associated with the user attribute. For normal users and user administrators, the registered
No. of the user management function is assigned. Built-in administrator is assigned a
special fixed number.
Login Obtain credentials from users to perform identification and authentication, and if
identification and authentication is successful, make TOE available. This can be performed
from the operation panel, WC, and printer driver.
User name Identification entered as credential by the normal user and user administrator when logs in.
When MFP Device Authentication, the TOE identifies whether the user is a registered user
by user name. This is set when registering a normal user in the user management function
Designation Definition
and cannot be changed thereafter.
Login password The password that the user enters as credential at login. When MFP Device
Authentication, the TOE authenticates the user by a login password. There are user
passwords, administrator passwords, and service passwords.
User password Login password for normal user. When MFP Device Authentication, the administrator can
set the user password for each normal user in the user management function. The normal
user can change his or her own user password.
Administrator password Login password for the built-in administrator. At the time of TOE shipment, the
predetermined administrator password is set, and the built-in administrator changes the
default value at the time of TOE installation. Thereafter, the administrator can change.
CE password Login password of the customer engineer.
Suspend temporarily Function that an administrator suspends the use of TOE by normal user. The administrator
can set and release the temporary suspension of use for each User ID registered in the user
management function. When a user who has a User ID with a Temporary Suspension is
logged in, the TOE discards the relevant user attribute and so user fails to log in and cannot
use the TOE.
Administrator Rights Function that an administrator allows the use of TOE by normal user in the role of
administrator. Administrator can set and release the administrator rights for each User ID
registered in the user management function. When a user who has a User ID set
administrator rights logs in successfully with the administrator authority, TOE can be
used in the role of administrator. When a user who has a User ID not set administrator
rights performs log in with the administrator authority, TOE discards the relevant user
attribute and so user fails to log in and cannot use the TOE.
Function Restriction A function that restricts the functions available to the normal user by the administrator. The
administrator can set or release the function restriction for each User ID registered in the
user management function. When a normal user with a User ID set a restricted function
performs a login, the TOE will hide the UI of the restricted function or display them with
the deactivate status and will not be able to use the restricted function.
2. Conformance Claims
CC Conformance Claims
This ST conforms to the following Common Criteria (hereinafter referred to as “CC”).
PP Claim
This ST conforms to the following PP and Errata.
PP Conformance Rationale
This satisfies the following conditions required by PP and is "Exact Conformance" as required by PP. Therefore, the
TOE type is consistent with PP
・Required Uses
Printing, Scanning, Copying, Network communications, Administration
・Conditionally Mandatory Uses
PSTN faxing, Storage and retrieval
・Optional Uses
None
Users
TOE users are classified as follows.
Table 3-1 User Categories
Name Classification name Definitions
Normal user Normal User User who is identified and authenticated by a user name and
(U.NORMAL) (U.NORMAL) user password. It has the role of normal user (U.NORMAL).
Administrator User who is identified and authenticated by a user name and
User administrator
(U.ADMIN) user password with administrator rights by assigned an
(U.USER_ADMIN)
administrator authority by administrator.
Built-in administrator Administrator User who is identified and authenticated by an administrator
(U.BUILTIN_ADMIN) (U.ADMIN) password. It has the role of administrator (U.ADMIN).
Assets
The assets in the TOE are as follows.
Table 3-2 Asset categories
Designation Asset category Definition
D.USER User Data Data created by and for Users that do not affect the operation of the TSF
D.TSF TSF Data Data created by and for the TOE that might affect the operation of the TSF
Threat Definitions
Threats are defined by a threat agent that performs an action resulting in an outcome that has the potential to violate
TOE security policies.
Assumption Definitions
Assumptions are conditions that must be satisfied in order for the Security Objectives and functional requirements to be
effective.
Table 3-7 Assumptions
Designation Definition
Physical security, commensurate with the value of the TOE and the data it
A.PHYSICAL
stores or processes, is assumed to be provided by the environment.
The Operational Environment is assumed to protect the TOE from direct,
A.NETWORK
public access to its LAN interface.
TOE Administrators are trusted to administer the TOE according to site
A.TRUSTED_ADMIN
security policies.
Authorized Users are trained to use the TOE according to site security
A.TRAINED_USERS
policies.
4. Security Objectives
Component leveling:
FAU_STG_EXT.1 External Audit Trail Storage requires the TSF to use a trusted channel implementing a secure
protocol.
Management:
The following actions could be considered for the management functions in FMT:
The TSF shall have the ability to configure the cryptographic functionality.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
The TSF is required that the transmission of generated audit data to an External IT Entity which relies on a non-TOE
audit server for storage and review of audit records. The storage of these audit records and the ability to allow the
administrator to review these audit records is provided by the Operational Environment in that case. The Common
Criteria does not provide a suitable SFR for the transmission of audit data to an External IT Entity.
This extended component protects the audit records, and it is therefore placed in the FAU class with a single component.
This family addresses the management aspects of cryptographic keys. Especially, this extended component is intended
for cryptographic key destruction.
Component leveling:
FCS_CKM_EXT.4 Cryptographic Key Material Destruction ensures not only keys but also key materials that are no
longer needed are destroyed by using an approved method.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
Cryptographic Key Material Destruction is to ensure the keys and key materials that are no longer needed are destroyed
by using an approved method, and the Common Criteria does not provide a suitable SFR for the Cryptographic Key
Material Destruction.
This extended component protects the cryptographic key and key materials against exposure, and it is therefore placed in
the FCS class with a single component.
Component leveling:
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
Failure to establish an IPsec SA
Rationale:
IPsec is one of the secure communication protocols, and the Common Criteria does not provide a suitable SFR for the
communication protocols using cryptographic algorithms.
This extended component protects the communication data using cryptographic algorithms, and it is therefore placed in
the FCS class with a single component.
Component leveling:
FCS_RBG_EXT.1 Random Bit Generation requires random bit generation to be performed in accordance with
selected standards and seeded by an entropy source.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
number of hardware-based sources] hardware-based noise source(s)] with a minimum of [selection: 128
bits, 256 bits] of entropy at least equal to the greatest security strength, according to ISO/IEC 18031:2011
Table C.1 “Security Strength Table for Hash Functions”, of the keys and hashes that it will generate.
Rationale:
Random bits/number will be used by the SFRs for key generation and destruction, and the Common Criteria does not
provide a suitable SFR for the random bit generation.
This extended component ensures the strength of encryption keys, and it is therefore placed in the FCS class with a
single component.
Component leveling:
FDP_FXS_EXT.1 Fax Separation, requires the fax interface cannot be used to create a network bridge between a PSTN
and a LAN to which TOE is connected.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
Fax Separation is to protect a LAN against attack from PSTN line, and the Common Criteria does not provide a
suitable SFR for the Protection of TSF or User Data.
This extended component protects the TSF Data or User Data, and it is therefore placed in the FDP class with a single
component.
Component leveling:
FIA_PMG_EXT.1 Password management requires the TSF to support passwords with varying composition
requirements, minimum lengths, maximum lifetime, and similarity constraints.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
Password Management is to ensure the strong authentication between the endpoints of communication, and the
Common Criteria does not provide a suitable SFR for the Password Management.
This extended component protects the TOE by means of password management, and it is therefore placed in the FIA
class with a single component.
Component leveling:
FIA_PSK_EXT.1 Pre-Shared Key Composition, ensures authenticity and access control for updates.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
Pre-shared Key Composition is to ensure the strong authentication between the endpoints of communications, and the
Common Criteria does not provide a suitable SFR for the Pre-shared Key Composition.
This extended component protects the TOE by means of strong authentication, and it is therefore placed in the FIA
class with a single component.
Component leveling:
FPT_SKP_EXT.1 Protection of TSF Data (for reading all symmetric keys), requires preventing symmetric keys from
being read by any user or subject. It is the only component of this family.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
Protection of TSF Data is to ensure the pre-shared keys, symmetric keys and private keys are protected securely, and
the Common Criteria does not provide a suitable SFR for the protection of such TSF data.
This extended component protects the TOE by means of strong authentication using Preshared Key, and it is therefore
placed in the FPT class with a single component.
Component leveling:
FPT_TST_EXT.1 TSF testing requires a suite of self-testing to be run during initial start-up in order to demonstrate
correct operation of the TSF.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
TSF testing is to ensure the TSF can be operated correctly, and the Common Criteria does not provide a suitable SFR
for the TSF testing. In particular, there is no SFR defined for TSF testing.
This extended component protects the TOE, and it is therefore placed in the FPT class with a single component.
Component leveling:
FPT_TUD_EXT.1 Trusted Update, ensures authenticity and access control for updates.
Management:
The following actions could be considered for the management functions in FMT:
There are no management actions foreseen.
Audit:
The following actions should be auditable if FAU_GEN Security Audit Data Generation is included in the PP/ST:
There are no auditable events foreseen.
Rationale:
Firmware/software is a form of TSF Data, and the Common Criteria does not provide a suitable SFR for the
management of firmware/software. In particular, there is no SFR defined for importing TSF Data.
This extended component protects the TOE, and it is therefore placed in the FPT class with a single component.
6. Security Requirements
<Notation>
“Bold” indicates completed or refined in [PP].
“Italic” indicates parts that is necessary to select and/or assign in ST.
“Bold” and “Italic” indicate selected and/or completed in the ST to the parts of an SFR completed or refined in
[PP].
The brackets([]) indicate the values selected or assigned by ST.
SFR component with a character in the parentheses such as (a), (b) etc. means that it is used repeatedly.
Extended components are identified by adding “_EXT” to the SFR identification.
(for O.AUDIT)
FCS_COP.1.1(a) Refinement: The TSF shall perform encryption and decryption in accordance with a specified
cryptographic algorithm AES operating in [CBC mode] and cryptographic key sizes 128-bits
and 256-bits that meets the following:
• FIPS PUB 197, "Advanced Encryption Standard (AES)"
• [NIST SP 800-38A]
View copy
Operation: Create copy job Modify copy job Cancel copy job
status / log
Job owner (note 2) denied
Copy
U.ADMIN denied denied
U.NORMAL denied denied
Unauthenticated denied denied denied
Create fax send View fax job Modify fax Cancel fax send
Operation:
job queue / log send job job
Job owner (note 2) denied
Fax send
U.ADMIN denied denied
U.NORMAL denied denied
Unauthenticated denied denied denied
Create fax View fax receive Modify fax Cancel fax
Operation:
receive job status / log receive job receive job
Fax Fax owner (note 3) denied
receive U.ADMIN (note 4) denied
U.NORMAL (note 4) denied denied
Unauthenticated (note 4) denied denied
Create storage / View storage / Modify storage Cancel storage /
Operation:
retrieval job retrieval log / retrieval job retrieval job
Storage / Job owner (note 6) denied
retrieval U.ADMIN denied denied
U.NORMAL denied denied
Unauthenticated denied denied denied
・Note 1: Job Owner is identified by a credential or assigned to an authorized User as part of the process of submitting
a print or storage Job.
・Note 2: Job Owner is assigned to an authorized User as part of the process of initiating a scan, copy, fax send, or
retrieval Job.
・Note 3: Job Owner of received faxes is assigned by default or configuration. Minimally, ownership of received
faxes is assigned to a specific user or U.ADMIN role.
・Note 4: PSTN faxes are received from outside of the TOE, they are not initiated by Users of the TOE.
・Note 5: Job Owner of the document created by Fax receive shall be Note3, Job Owner of the document sent from
the client PC shall be Note 1, Job Owner of the document generated by the scanner shall be Note 2, and Job
Owner of the document created by the store from Password encrypted PDF user box shall be Note 1.
・Note 6: Job Owner of the job created by Fax receive on "Create storage job" shall be Note3, Job Owner of the job
sent from the client PC shall be Note 1, Job Owner of the job generated by the scanner shall be Note 2, and Job
Owner of the job created by the store from Password encrypted PDF user box shall be Note 1. Job Owner of
"Create retrieval job" is Note 2.
FIA_UAU.7.1 The TSF shall provide only [display "*" or "●" every character data input] to the user while the
authentication is in progress.
Dependencies : No dependencies
FTA_SSL.3.1 The TSF shall terminate an interactive session after a [time determined by system auto reset time
for operation panels, time determined by automatic logout time for WCs, and no interactive
session for printer drivers].
(for O.COMMS_PROTECTION)
Hierarchical to : No other components.
Dependencies : [FCS_IPSEC_EXT.1 Extended: IPsec selected, or
FCS_TLS_EXT.1 Extended: TLS selected, or
FCS_SSH_EXT.1 Extended: SSH selected, or
FCS_HTTPS_EXT.1 Extended: HTTPS selected].
FTP_TRP.1.1(b) Refinement : The TSF shall use [IPsec] to provide a trusted communication path between itself
and remote users that is logically distinct from other communication paths and provides assured
identification of its end points and protection of the communicated data from disclosure and
detection of modification of the communicated data.
FTP_TRP.1.2(b) Refinement: The TSF shall permit [remote users] to initiate communication via the trusted path
FTP_TRP.1.3(b) Refinement: The TSF shall require the use of the trusted path for initial user authentication
and all remote user actions.
composed of any combination of upper and lower case letters, numbers, and special characters
(that include: "!", "@", "#", "$", "%", "^", "&", "*", "(", and ")").
FIA_PSK_EXT.1.3 The TSF shall condition the text-based pre-shared keys by using [SHA-1, SHA-256, SHA-512,
[SHA-384]] and be able to [use no other pre-shared keys].
FIA_UAU.1, FIA_UID.1
TOE supports the three authentication methods shown in Table 7-2 and an administrator can set in the user
authentication setting function.
When using TOE from the operation panel or WC, enter the user name, user password, and administrator rights. When
using TOE from the operation panel or WC as the built-in administrator, enter the administrator password from the login
screen for the built-in administrator. When using TOE from the printer driver, enter the user name and user password.
TOE performs the identification and the authentication based on the input credentials, and permits the use of TOE only
if successful. If the external server authentication method is set, the user enters an external authentication server ID in
addition to the user name and user password. TOE sends the user name to the specified external authentication server and
decrypts the returned credential by user key generated from the user password. It determines that the authentication is
successful when the decryption is successful, and that the authentication is not successful when the decryption is failed.
Identification and authentication of Built-in Administrator is always performed by the MFP authentication method,
regardless of the authentication method setting.
TOE provides a function for the administrator to set the password to the Memory RX user box in the Memory RX
setting function, and Memory RX user box password has been set during operation. When a normal user who succeeds in
identification and authentication from the operation panel or WC accesses the Memory RX user box, authentication
using the Memory RX user box password is requested, and access is permitted only when authentication is successful.
Therefore, a normal user who does not know the Memory RX user box password cannot operate fax documents stored in
the Memory RX user box. The authentication of Memory RX user box password is always performed by the MFP
authentication method, regardless of the setting of the authentication method.
Since identification and authentication is performed for each of the above interfaces, the normal user can perform
identification and authentication from the panel while the administrator is performing the remote management function
from the WC, and if successful, the TOE can be operated. However, because identification and authentication of other
administrators is prohibited while an administrator logs in, two or more administrators cannot use TOE simultaneously
When TOE is used by the printer driver, there is no interactive session. When TOE receives electronic document,
identification and authentication is performed using the credential (user name, user password) included in the electronic
document. If successful, the normal user (U.NORMAL) is assigned as the user’s role and stored in TOE as an electronic
document owned by relevant normal user. If it fails, the received electronic document is destroyed without storing it. The
Printer Driver does not provide a way for administrators to use TOE.
Possible operations before performing identification and authentication are as follows.
・FAX RX
・The following settings can be used to check and display the TOE status.
Device information display from the operation panel (firmware version etc.)
Job display from the operation panel
Enlarge display setting from the operation panel
Change of display language of the WC
FIA_ATD.1
For each normal user registered with the user management function, TOE defines the User ID, administrator rights
and the access authority of function restriction as the user attribute. Also, the access authority to Memory RX user box is
defined as the user attribute, too. This is provided the interface of Memory RX user box password authentication to
access memory RX user box only to normal user registered with the user management function, and associates the
normal user who is succeded this authentication. Also, User ID is defined as user attributes of the built-in administrator.
FIA_USB.1
TOE associates the user attribute (User ID, administrator rights, function restriction, access authority to Memory RX
user box), if a normal user or a user administrator succeeds in identification and authentication. TOE associates the user
attribute (User ID), if the built-in administrator succeeds in identification and authentication.
At this time, TOE discards the user attribute associated with the user, if the temporary suspension is set to the User ID.
Also, if the administrator rights are not set to the user who performed the login as the user administrator, the user
attribute associated with the relevant user is discarded.
When accessing the memory RX user box after a normal user succeeds in identification and authentication, the
authentication by memory RX user box password is required. If the authentication is successful, TOE enables access to
the memory RX user box that is the user attribute of the relevant user. If the authentication fails, the TOE disables access
to the memory RX user box that is the user attribute of the relevant user.
FIA_AFL.1
The TOE provides an authentication operation prohibition function to stop the user's authentication when the
administrator detects a continuous authentication failure more than the number of checks (1 to 3 times) set in advance by
the administrator in the user's identification and authentication. If an administrator rights is assigned to a normal user, the
number of authentication failures as a normal user and the number of authentication failures as a user administrator are
totaled.
When the authentication of the built-in administrator was suspended, turn OFF and ON the TOE power first. Then, the
authentication suspension is released when the time set for the operation prohibition release time setting, has passed after
the TOE is started. If the authentication of the normal user or the user administrator is suspended, the administrator who
is not in the suspended status can release their suspension by performing the deletion function of the number of the
authentication failure.
The TOE also performs the above-mentioned authentication failure operation for identification and authentication by
an external server authentication method.
The authentication of the memory RX user box password is suspended when the administrator detects a continuous
authentication failure more than the number of checks (1 to 3 times) set in advance by the administrator in the
identification and authentication of memory RX user box password. If the authentication of memory RX user box
password is suspended, the administrator who is not in the suspended status can release the authentication suspension by
performing the deletion function of the number of authentication failures.
FIA_UAU.7
When entering the login password or the memory RX user box password in the authentication processing of the
interactive session (login from the operation panel or WC), TOE displays "*" or "●" for each character entered.
FIA_PMG_EXT.1
Characters that TOE can use as a user password are uppercase and lowercase letters in the alphabet , numbers,
symbols (“!”, “@”, “#”, “$”, “%”, “^”, “&”, “*”, “(“, “)”, “-”, “¥”, “[”, “]”, “:”, “;”, “,”, “.”, “/“, “'”, “=”, “~”, “|”, “`”, “{”,
“}”, “+”, “<”, “>“, “?” ,“_” and space), special characters (97 characters). In addition to the above characters, “””
(double quotation) can be used for the memory RX user box password. The administrator can set the minimum password
length from 8 to 64 characters. Therefore, the minimum password length of 15 characters or longer can be set.
FTA_SSL.3
The TOE terminates the session when a user who has been identified and authenticated by the operation panel or WC
satisfies the following conditions. In the case of the printer driver, there is no interactive session, but it logs in when the
requested processing is received from the printer driver and logs out immediately after the processing is completed.
・In the case of the operation panel, the user is logged out when the system auto reset time (settable between 1 and 9
minutes) has passed since the process of the final operation was completed.
・In the case of the WC, the user is logged out when the automatic logout time (settable between 1 and 60 minutes)
has passed since the process of the final operation was completed.
When a normal user (U.NORAML) allowed by the identification and authentication performs Create operations in
Tables 7-3 through 7-14, the user becomes a Job Owner and TOE records the User ID as the owner information of a
document or Job. TOE does not provide an interface for an administrator (U.ADMIN) to perform a Create operation.
Since the Fax RX function (Fax receive) performs the Create operation by receiving a fax from an external fax without
the TOE operation, the job owner of the document or job until the Fax RX completion is assigned to the administrator
(*1). In the case of Fax RX with no F-code specified, the fax document is saved in the Memory RX user box, so the job
owner after the Fax RX is the normal user who knows the Memory RX user box password (*2). In the case of Fax RX
with the F-code specified, the fax document is saved in the specified personal user box, so the job owner after Fax RX is
the normal user who owns the personal user box (*3). Saving from the password encrypted PDF user box (Storage /
retrieval) is performed the create operation by retrieving the document, set to be saved, from the password encrypted
PDF user box and saving it in the operator's personal user box, when performing the direct print. The job owner of the
document or job after saving is the normal user who is the owner of the personal user box.
TOE has a function restriction setting that restricts the functions available to each normal user by the administrator in
the user management functions. The TOE displays the interface of the restricted function either hidden or inoperable
based on the user attribute function limitations. Therefore, a normal user with a function restriction cannot use the
operation using the restricted function from Table 7-3 to Table 7-14.
TOE has Memory RX setting function in which the administrator restricts the access of the normal user to the memory
RX user box in the Memory RX setting function. During operation, access is restricted by the memory RX user box
password. Based on the access authority to the memory RX user box of user attribute, the TOE allows access to the user's
memory RX user box if it is valid, and denies access to the user's memory RX user box if it is invalid. Therefore, normal
users who do not know the memory RX user box password cannot use the operations required to access the memory RX
user box in Tables 7-3 to 7-14.
In the user box management function, the TOE has a function to set the owner of the personal user box (User ID) by
the administrator or normal user. It has a function to change the owner of the personal user box (User ID) by the
administrator or the normal user who owns the personal user box. The TOE restricts access to the personal user box and
documents stored in the personal user box. If the normal user has the same User ID based on the Personal user Box
Owner (User ID), the TOE provides an interface to the Personal User Box and permits access to the Personal User Box.
On the other hand, if the normal user has a different User ID, the TOE will hide the interface of the relevant Personal
User Box, so the operation that requires the access to the relevant personal user box with Tables 7-3 to 7-14 cannot used.
Job owner 〇 〇 - Deletion of fax documents due to deletion of print job of fax
U.ADMIN documents.
〇 〇 - Deletion of fax documents due to deletion of personal user
boxes.
from the user box menu screen, and save in the user box.
- 〇 - To the password encrypted PDF, specify the Save in User Box
and perform direct print.
〇 Select the document from the password encrypted PDF user box
and save. (Selected document is moved to the operator’s
personal user box.)
Job owner(*2) - - - No operation of TOE. After receiving a Fax with no F-code from
an external Fax, save the fax document in the Memory RX user
box.
Job owner(*3) - - - No operation of TOE. After receiving a Fax with F-code from the
external Fax, save the fax document is the specified personal
user box.
Read Job owner 〇 〇 - Select the document from the personal user box and display the
document preview.
(Except fax documents. Document previews of fax documents
are controlled by the Read operation in Table 7-7.)
〇 - - Select the document from the personal user box and print, send,
fax TX, move, or copy it.
(Except the printing of fax documents. The printing of fax
documents is controlled by the Read operation in Table 7-7.)
- 〇 - Select a document from the personal user box and send,
download, move, or copy it.
- 〇 - Select a document from the Memory RX user box and download
it.
〇 - - Select the document from the Password Encrypted PDF user box
and save it.
(Password must be entered for storage. Documents will be
deleted upon completion of storage.)
Modify Job owner 〇 〇 - Select a document from the personal user box and edit it.
(Except fax documents. Editing of fax documents is controlled
by the Modify operation in Table 7-7.)
〇 〇 - Perform application setting in Read operation (send, print).
(Except printing of fax documents. The application setting in the
printing of fax documents is controlled by the Modify operation
in Table 7-7.)
〇 - - Select the fax document from the Memory RX user box and edit
it (change name).
Delete Job owner 〇 〇 - Delete the document from the personal user box.
(Except the deletion of fax documents. Delete of fax documents
is controlled by Delete operation in Table 7-7.)
〇 - - Delete document from password encrypted PDF user box.
Job owner 〇 〇 - Deletion of documents due to deletion of personal user boxes.
U.ADMIN (Except deletion of fax documents. Delete of fax documents is
controlled by Delete operation in Table 7-7.)
printing.
(The fax document will be deleted upon completion of printing.)
Read Job owner 〇 〇 -
U.ADMIN
Displays the job.
U.NORMAL
Unauthenticated 〇 - -
Modify - - - - None.
Job owner 〇 〇 - Delete a job from the job display.
U.ADMIN (In the case of a print job, the fax document is also deleted by
deleting the job.)
Encryption function
FCS_CKM.1(a)
The TOE generates an RSA asymmetric key with a key length of 2048 bits in the method described in the rsakpg1-crt
method described in Section 6.3.1.3 of NIST SP800-56B, Revision 1 in the generation of IPsec certificates used in the
key establishment for IPsec communication. Also, in the key establishment for IPsec communication, an asymmetric key
is generated by Diffie-Hellman Group 14 as described in the Using the Approved Safe-Prime Groups described in
Section 5.6.1.1.1 of NIST SP800-56A, Revision 3.
FCS_CKM.1(b)
The TOE generates a random number using the RBG described in FCS_RBG_EXT.1 and generates a 128-bit or
256-bit symmetric encryption key at the start of IPsec communication or at the key establishment after the SA lifetime.
TOE starts the above RBG by calling the DRBG function (CTR DRBG (AES-256)) and generates a random number.
FCS_RBG_EXT.1
TOE implements a CTR DRBG (AES-256) conforming to NIST SP 800-90A and an RBG consisting of a single
software entropy source. The above CTR DRBG uses the Derivation Function and Reseed, but the Prediction Resistance
function does not work. The software entropy source implements a condition branch code etc., that affects the internal
state of the CPU, and a clock counter value acquisition process in the loop process. The variation of the loop processing
performance time is acquired via the clock counter and obtain the raw data. Conditioning is performed to agitate and
compress the entropy included in the raw data into the entire bit using shift operations and XOR, and after increasing the
entropy rate of the entire bit, it is output as an entropy value.
The TOE uses this RBG to generate random numbers and uses them to generate encryption keys (key length 256 bit
and 128 bit) with a trusted communication function. When the TOE generates a random number, if the CTR DRBG
requires a seed material (Entropy Input and Nonce), start the software to be used as the entropy source and obtain and use
the required size entropy value. This entropy value satisfies the minimum amount of entropy required for Instantiate and
Reseed (in the case of TOE, 256 bits equal to the security strength) shown in 10.2.1 of NIST SP800-90A and contains
sufficient entropy.
FIA_PSK_EXT.1
The TOE uses the following text-based pre-shared key as the pre-shared key for IPsec. The text-based pre-shared key
is also converted into a bit string using the hash algorithm described below.
・Text-based pre-shared key
Length: 22 characters
Available Characters: ASCII String or HEX Values
Conditioning methods: SHA-1, SHA-256, SHA-384, and SHA-512
FCS_COP.1(a)
TOE uses an AES-CBC with a key length of 128 bits and 256 bits conforming to FIPS PUB 197 and NIST SP 800-38A
as an ESP encryption algorithm for IPsec communication.
FCS_COP.1(b)
TOE uses the RSA digital signature algorithm with a key length of 2048 bits conforming to FIPS PUB 186-4 in FW
verification of the update function. The RSA digital signature algorithm (signature generation) with a key length of 2048
bits conforming to FIPS PUB 186-4 is used for peer authentication of IPsec communications, and the RSA digital
signature algorithm (signature verification), with a key length of 2048 bits and 3048 bits, conforming to FIPS PUB 186-4
is used for digital signature verification.
FCS_COP.1(c)
In the update function described in Section 7.7.1, TOE verifies firmware data using digital signature verification as
follows. Among them, the calculation of the hash value by SHA-256 conforming to ISO/IEC 10118-3:2004 is
performed.
Decodes the digital signature data with the RSA public key (key length 2048 bit) owned by TOE.
Calculate the hash value of the firmware data with SHA-256.
Compare the values of (1) and (2). The firmware data is judged to be correct if the data are matched.
As an IKEv1 authentication algorithm for IPsec communication, TOE calculates hash values using SHA-1, SHA-256,
SHA-348, and SHA-512 conforming to ISO/IEC 10118-3:2004.
FCS_COP.1(g)
In IPsec communication, TOE implements the following ESP by keyed hash message authentication in compliance
with The Keyed-Hash Message Authentication Code defined in FIPS PUB 198-1 and Secure Hash Standard defined in
FIPS PUB 180-3.
・Message digest length: 160, 256, 384, 512
・Key Length: 160, 256, 384, 512
・Encryption algorithms: HMAC-SHA-1, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512
FCS_CKM.4, FCS_CKM_EXT.4
Table 7-15 shows the storage destination of keys and key materials used for IPsec communication and the method of
destruction. The pre-shared key set by the administrator and the private key of the IPsec certificate are stored in the
field-nonreplaceable SSD. When the administrator performs the deletion of these keys, it is overwritten with 0x00.
Session keys (temporary encryption keys) used in IPsec are stored in RAM. These items are deleted when the TOE
power is turned off since they will be no longer needed.
FTP_TRP.1(a)
TOE provides a WC that runs on the browser of the client PC as a way for the administrator to remotely manage TOE.
Communication between TOE and client PC uses the IPsec protocol, which is the trusted communication path. When the
TOE is accessed from the client PC for remote management, the TOE starts communication only with the IPsec protocol
and guarantees end point identification, protection from communication data leakage, and detection of communication
data modification.
FTP_TRP.1(b)
TOE provides WC and printer drivers that run on the browser of the client PC as a way for non-administrator users to
access TOE remotely. Communication between TOE and client PC uses the IPsec protocol, which is the trusted
communication path. When the TOE is accessed from the client PC for remote access, the TOE starts communication
only with the IPsec protocol and guarantees end point identification, protection from communication data leakage, and
detection of communication data modification.
FCS_IPSEC_EXT.1
TOE implements an IPsec architecture conforming to RFC 4301. Only the administrator can set and change the
following settings as the IPsec protocol, but cannot use the settings other than followings.
Also, the TOE implements the IPsec Security Policy Database (SPD) and the followings can be set by the administrator.
・IPsec Policy: Specify the IP packet conditions and select which of the protected, allow, and deny operations to
perform for IP packets that meet each of these conditions. Inbound packet and outbound packet are processed
with same rule from the view of the IPsec policy. For IP packet conditions, protocols of Any and destination IP
addresses (Individual, or Subnet settings) can be set.
IPsec policy can be set to 10 groups of IP policy groups 1 to 10. When multiple IPsec policies are set, the
operation is applied in the following order of precedence, regardless of the order in which IPsec policy groups 1
to 10 are registered.
Priority: High Protected > Deny > Allow Priority: Low
・Default Action: If the IPsec policy is not matched, select the action from the following. (Guidance instructs
administrators to choose to discard in this setting.)
Deny: Discard IP packets that do not match the IPsec policy setting
Allow: Bypassing IP packets that do not match the IPsec policy setting
Copyright ©2020 KONICA MINOLTA, INC., All Rights Reserved
64 / 71
KONICA MINOLTA bizhub 450i/bizhub 360i/bizhub 300i with FK-514, DEVELOP ineo 450i/ineo 360i/ineo 300i with FK-514
Security Target
FPT_SKP_EXT.1
TOE stores the pre-shared key set by the administrator and the private key of the IPsec certificate, among the
encryption keys used for IPsec communication in the SSD that is a Field- nonreplaceable non-volatile storage. Other
encryption keys are stored in RAM (see Table 7-15). The TOE does not provide the ability to view stored pre-shared
keys, private keys, and encryption keys, so users cannot retrieve them by operating the TOE. The TOE implements
RS-232C IF on the MFP itself, but since it is disabled during operation, the user cannot use this interface to retrieve SSD
internal data. Other than the RS-232C IF, the interface for retrieving SSD internal data from outside the TOE is not
implemented. Because SSD is the field-nonreplaceable storage, user cannot remove SSD and retrieve internal data.
Therefore, users cannot read the stored pre-shared key, private key, or encryption key.
Audit function
TOE generates and records an audit log for the event being audited and sends it to the log server.
FAU_GEN.1, FAU_GEN.2
The TOE defines the following events as the event to be audited and records the event occurrence time (year, month,
day, hour, minute, second), event type, subject identification information, and event results.
ID (Subject Identification
Event to be audited Results
Information *1)
Modification of Administrator password Admin ID OK
Modification of User Authentication Settings Admin ID OK
Registration and modification of External Authentication
Admin ID OK
Server settings
Modification of the No. of Authentication Failures threshold Admin ID OK
Modification of the Prohibited operation Release time of
Admin ID OK
Administrator authentication
Clearing the No. of Authentication Failures (other than
Admin ID OK
U.BUILTIN_ADMIN)
Password rule modification function Admin ID OK/NG
Modification of Enhanced Security mode settings Admin ID OK
Modification of Date and time information Admin ID OK
Modification of System Auto reset time Admin ID OK
Modification of Automatic Logout time Admin ID OK
Registration, modification and deletion of Trusted
Admin ID OK/NG
Communication Management settings
Registration and modification of Network settings Admin ID OK/NG
Start of the Audit Log acquisition function Admin ID OK
End of the Audit Log acquisition function Admin ID OK
Registration and modification of Audit Log management
Admin ID OK
function
Registration, modification, and deletion of personal user box
Admin ID/User ID OK/NG
by User box management functions
Registration, modification of Memory RX setting function Admin ID
Storing a print job User ID OK/NG
Printing a print job User ID OK/NG
Sending a scan job User ID OK/NG
Printing a copy job User ID OK/NG
Sending a Fax TX job User ID OK/NG
Receiving a Fax RX job System ID OK/NG
Printing a Fax RX job User ID OK/NG
Storing a saved job User ID OK/NG
Storing a Fax RX job System ID OK/NG
Printing a saved job User ID OK/NG
Sending a saved job User ID OK/NG
Fax sending a saved job User ID OK/NG
Downloading a saved job User ID OK/NG
Moving a saved job User ID OK/NG
Duplicating a saved job User ID OK/NG
Deleting a saved job User ID OK/NG
Failure of IPsec session establishment System ID ErrNo(*2)
(*1) The ID of the event to be audited (subject identification information) that occurred before identification and
authentication records a fixed value such as an unregistered ID.
The system ID (fixed value: system (MFP)) is recorded because no identification and authentication is performed
for Fax RX.
The system ID (fixed value: system (MFP)) is recoded in the failure of IPsec session establishment.
(*2) A predetermined error such as "1414" (failure of secure communication (IPSec)) is recorded.
FAU_STG_EXT.1
TOE provides the Audit Log management function performed by the administrator for enabling/disabling the audit
function, how to obtain the audit log, log server, setting of automatic log distribution conditions, and sending and
deleting the audit log. Use WebDAV server for the log server. IPsec communication between TOE and the log server is
set by the trusted communication management function.
The TOE temporarily saves log information as a log file in the local storage area of the TOE. It converts it to XML
data and sends it to the log server when the date and time set in the automatic log distribution condition or the log storage
amount set in the automatic log distribution condition is reached or when the administrator performs the audit log
transmission.
Log files temporarily saved in TOE are deleted after conversion to XML data or when an administrator performs the
audit log deletion. XML data is deleted at the timing of XML data conversion of the next file, after transmission to the
log server is completed. The only interfaces that access the log files and XML data stored temporarily in the TOE are the
sending and deletion of audit logs by the administrator, and so unauthorized access by normal users or attackers is not
possible.
When log information cannot be sent to the log server due to network failure, etc., and the local storage area in the
TOE becomes full, the functions that can be performed are limited to the following functions.
・End of the audit log acquisition function by turning OFF the power supply
・Start of the audit log acquisition function by turning ON the power
・User Authentication (only administrator login from the operation panel is allowed)
・Sending or deleting audit log by administrator
The restriction is released, by an administrator sends an audit log or performs an audit log deletion and clears the full of
the local storage area.
FPT_STM.1
TOE has a clock function and provides only the administrator with the function to change the time of TOE. Time
information to be recorded in the audit log is provided by the clock function.
---End---