Ricoh Mp 3351 User Guide

  Page 51 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved. Functional requirements Management requirements Management items FMT_MTD.1 a) Managing the group of roles that can 
interact with the TSF data. None: No groups of roles can interact with 
TSF data. FMT_SMF.1 None - FMT_SMR.1 a) Managing the group of users that are 
part of a role. Management of administrator  
roles by administrators. FPT_STM.1 a) Management of the time. Security Management Function 
(management of machine...

  Page 52 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  Dependencies: No dependencies. 
FPT_TST.1.1 The TSF shall run a suite of self tests [selection: during initial start-up] to demonstrate the 
correct operation of [selection: [assignment: encryption function of the Ic Hdd]]. 
FPT_TST.1.2 The TSF shall provide authorised users with the capability to verify the integrity of the 
[selection: [assignment: HDD cryptographic key]]. 
FPT_TST.1.3 The TSF shall provide authorised users...

  Page 53 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  Table 20: Services requiring trusted paths Related persons for communication Services that require a trusted path TSF E-mail service to client computer from  TOE (S/MIME) Remote users Initial user authentication (SSL) 
TOE web service from client PC (SSL) 
Printing service from client PC (SSL) 
Fax service from client PC (SSL)  

  Page 54 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  6.2 Security Assurance Requirements 
The evaluation assurance level of this TOE is EAL3. Table 21 lists the assurance components of the TOE. 
These components meet evaluation assurance level 3 (EAL3). Other requirements are not included. 
Table 21: TOE Security assurance requirements (EAL3) Assurance classes Assurance components ADV_ARC.1 Security architecture description ADV_FSP.3 Functional specification with complete...

  Page 55 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  6.3 Security Requirements Rationale 
This section describes the rationale behind the security requirements. If all security functional requirements 
are satisfied as below, the security objectives defined in 4.1Security Objectives for TOE are fulfilled. 
6.3.1 Tracing 
Table 22 shows the relationship between the TOE security functional requirements and TOE security 
objectives. The v in the table indicates that the TOE security...

  Page 56 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  O.AUDIT
 
O.I&A
 
O.DOC_ACC
 
O.MANAGE
 
O.MEM.PROTECT
 
O.NET.PROTECT
 
O.GENUINE
 
O.LINE_PROTECT
 FIA_USB.1  v       FMT_MSA.1    v     FMT_MSA.3    v     FMT_MTD.1    v     FMT_SMF.1    v     FMT_SMR.1    v     FPT_STM.1 v        FPT_TST.1     v  v  FTP_ITC.1      v   FTP_TRP.1      v    
6.3.2 Justification of Traceability 
This section describes how the TOE security objectives are fulfilled by the TOE security functional...

  Page 57 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  d) Reliable record of time of event 
To fulfill O.AUDIT, a reliable record of the times when events occurred should be available, as this will 
help identify security breaches. 
For this, FPT_STM.1 provides a trusted time stamp. 
O.I&A User identification and authentication 
Following are the rationale behind the functional requirements corresponding to O.I&A in Table 22, and 
these requirements are included to fulfill the...

  Page 58 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  FDP_ACC.1 and FDP_ADF.1 allow the general user to perform operations on document data. The 
operations that are permitted follow the operation permissions specified in the document data for each 
general user ID in the document data ACL. 
O. MANAGE Security management 
Following are the rationale behind the functional requirements corresponding to O.MANAGE in Table 22, 
and these requirements are included to fulfill the...

  Page 59 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  performed. 
For this, FMT_SMF.1 specifies the required Security Management Functions for the Security Function 
requirements. 
d) Authorised use of Security Management Functions. 
To fulfill O.MANAGE, authorised users shall be associated with the security management roles, and 
operation permissions for the Security Management Functions shall be maintained, since the use of the 
Security Management Functions depends on the...

  Page 60 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.  O.GENUINE Protection of integrity of MFP Control Software integrity 
Following are the rationale behind the functional requirements corresponding to O.GENUINE in Table 22, 
and these requirements are included to fulfill the O.GENUINE specification. 
a) Check the integrity of the MFP Control Software. 
To fulfill O.GENUINE, the integrity of the MFP Control Software, which is installed in FlashROM, 
shall be verified. For this,...