Page 37 of 81
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.
Functional requirements Actions which should be auditable Auditable events of TOE
Authentication information.
6. Changing time and date of system
clock.
7. Deleting entire audit logs.
FMT_SMF.1
a) Minimal: Use of the Management
Functions.
<Individually defined auditable
events>
1. Adding and deleting administrator
roles.
2. Lockout release by the unlocking
administrator.
3. Changing time and date of system
clock.
FMT_SMR.1
a) Minimal: modifications to the group
of users that are part of a role;
b) Detailed: every use of the rights of a
role.
a) Minimal
1. Adding and deleting administrator
roles.
FPT_STM.1 a) Minimal: changes to the time;
b) Detailed: providing a timestamp.
a) Minimal
1. Changing time and date of system
clock.
FPT_TST.1
a) Basic: Execution of the TSF self
tests and the results of the tests.
-
FTP_ITC.1
a) Minimal: Failure of the trusted
channel functions.
b) Minimal: Identification of the
initiator and target of failed trusted
channel functions.
c) Basic: All attempted uses of the
trusted channel functions.
d) Basic: Identification of the initiator
and target of all trusted channel
functions.
<Individually-defined auditable
events>
1. Communication with trusted IT
products (Outcome: Success/Failure,
Communication IP address)
FTP_TRP.1
a) Minimal: Failures of the trusted path
functions.
b) Minimal: Identification of the user
associated with all trusted path
failures, if available.
c) Basic: All attempted uses of the
trusted path functions.
d) Basic: Identification of the user
associated with all trusted path
invocations, if available.
<Individually-defined auditable
events>
1. Communication with remote users
(Outcome: Success/Failure)
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