Ricoh Aficio MP 2851 Security Target - Page 37

FAU_GEN.1.2 The TSF shall - ip address

Page 37 highlights

Functional requirements FMT_SM F.1 FMT_SMR.1 FPT_STM.1 FPT_TST.1 FTP_ITC.1 FTP_TRP.1 Page 37 of 81 Actions which should be auditable a) Minimal: Use of the Management Functions. 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: changes to the time; b) Detailed: providing a timestamp. a) Basic: Execution of the TSF self tests and the results of the tests. 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. 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. Auditable events of TOE 6. Changing time and date of system clock. 7. Deleting entire audit logs. 1. Adding and deleting administrator roles. 2. Lockout release by the unlocking administrator. 3. Changing time and date of system clock. a) Minimal 1. Adding and deleting administrator roles. a) Minimal 1. Changing time and date of system clock. - 1. Communication with trusted IT products (Outcome: Success/Failure, Communication IP address) 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 Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81

Page 37 of 81
Copyright (c) 2010 RICOH COMPANY, LTD. All Rights Reserved.
Functional requirements
Actions which should be auditable
Auditable events of TOE
6. Changing time and date of system
clock.
7. Deleting entire audit logs.
FMT_SM F.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