Page 34 of 81 
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved. 
6  Security Requirements 
This section describes the security functional requirements, security assurance requirements, and security 
requirements rationale. 
6.1  Security Functional Requirements 
This section describes the TOE security functional requirements for fulfilling the security objectives 
defined in "4.1  Security Objectives for TOE".  The security functional requirements are quoted from the 
requirement defined in the CC Part2. 
The part with assignment and selection defined in the CC Part2 are identified with [bold face and 
brackets]. 
6.1.1  Class FAU: Security audit 
FAU_GEN.1  Audit data generation 
Hierarchical to:  No other components. 
Dependencies:  FPT_STM.1 Reliable time stamps. 
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: not specified] level of audit; and 
c) [assignment: auditable events of the TOE shown inTable4]. 
 
Table 4 shows the actions (CC rules) recommended by the CC as auditable for each functional requirement 
the corresponding auditable events of the TOE. 
Table 4: List of auditable events 
Functional requirements  Actions which should be auditable  Auditable events of TOE 
FAU_GEN.1  None - 
FAU_SAR.1 
a) Basic: Reading of information from 
the audit records.
Auditable events not recorded. 
FAU_SAR.2 
a) Basic: Unsuccessful attempts to 
read information from the audit 
records. 
Auditable events not recorded. 
FAU_STG.1  None - 
FAU_STG.4 
a) Basic: Actions taken due to the 
audit storage failure. 
Auditable events not recorded. 
FCS_CKM.1 
a) Minimal: Success and failure of the 
activity. 
b) Basic: The object attribute(s), and 
<Individually-defined auditable 
events> 
1. HDD cryptographic key