Page 36 of 82
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.
Functional requirements Actions which should be auditable Auditable events of TOE
FCS_CKM.1
a) Minimal: Success and failure of the
activity.
b) Basic: The object attribute(s), and
object value(s) excluding any
sensitive information (e.g. secret or
private keys).
<Individually-defined auditable
events>
1. HDD cryptographic key
generation (Outcome:
Success/Failure)
FCS_COP.1
a) Minimal: Success/failure, and type
of cryptographic operation.
b) Basic: Any applicable
cryptographic mode(s) of operation,
subject and object attributes.
<Individually-defined auditable
events>
1. Storage of document data
successful
2. Reading of document data
successful
FDP_ACC.1 None -
FDP_ACF.1
a) Minimal: Successful requests to
perform an operation on an object
covered by the SFP.
b) Basic: All requests to perform an
operation on an object covered by the
SFP.
c) Detailed: The specific security
attributes used in making an access
check.
<Individually-defined auditable
events>
1. Storage of document data
successful
2. Reading of document data
successful
3. Deletion of document data
successful
FDP_IFC.1 None -
FDP_IFF.1
a) Minimal: Decisions to permit
requested information flows.
b) Basic: All decisions on requests for
information flow.
c) Detailed: The specific security
attributes used in making an
information flow enforcement
decision.
d) Detailed: Some specific subsets of
the information that has flowed based
upon policy goals (e.g. auditing of
downgraded material).
a) Minimal
1. Fax Function: Reception
FIA_AFL.1
a) Minimal: the reaching of the
threshold for the unsuccessful
authentication attempts and the
actions (e.g. disabling of a terminal)
taken and the subsequent, if
appropriate, restoration to the normal
state (e.g. re-enabling of a terminal).
a) Minimal
1. Lockout start
2. Lockout release
FIA_ATD.1 None -
To Next Page
Loading...
Need help?
General
