
Page 36 of 83
6 Security Requirements
This chapter describes the Security Functional Requirements, Security Assurance Requirements, and
Security Requirements Rationale.
6.1 Security Functional Requirements
This chapter describes the TOE security functional requirements to accomplish the security objectives
defined in "4.1 Security Objectives for TOE". The security functional requirements are quoted from the ones
defined in the CC Part 2.
The part with Assignment and Selection defined in the CC Part 2 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 in
Table 5].
Table 5 shows the actions (rules in the CC) that are recommended by the CC to be auditable for each
functional requirement, and the corresponding auditable events of the TOE.
Table 5: 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 are not recorded.
FAU_SAR.2 a) Basic: Unsuccessful attempts
to read information from the
audit records.㩷
Auditable events are not recorded.
FAU_STG.1 None㩷 -
FAU_STG.4 a) Basic: Actions taken due to
the audit storage failure.㩷
Auditable events are not recorded.
FCS_CKM.1 a) Minimal: Success and failure <Individually defined auditable events>
Copyright (c) 2009,2010 RICOH COMPANY, LTD. All Rights Reserved.
Comentarios a estos manuales