Ricoh C400DN Security Target - Page 68

Security Requirements Rationale

Page 68 highlights

Assurance Classes AVA: Vulnerability assessment ATE_IND.2 AVA_VAN.2 Assurance Components Independent testing - sample Vulnerability analysis Page 67 of 91 6.3 Security Requirements Rationale This section describes the rationale for security requirements. If all security functional requirements are satisfied as below, the security objectives defined in "4 Security Objectives" are fulfilled. 6.3.1 Tracing Table 31 shows the relationship between the TOE security functional requirements and TOE security objectives. Table 31 shows that each TOE security functional requirement fulfils at least one TOE security objective. Table 31 : Relationship between Security Objectives and Functional Requirements O.DOC.NO_DIS O.DOC.NO_ALT O.FUNC.NO_ALT O.PROT.NO_ALT O.CONF.NO_DIS O.CONF.NO_ALT O.USER.AUTHORIZED O.INTERFACE.MANAGED O.SOFTWARE.VERIFIED O.AUDIT.LOGGED O.STORAGE.ENCRYPTED O.RCGATE.COMM.PROTECT FAU_GEN.1 FAU_GEN.2 FAU_STG.1 FAU_STG.4 FAU_SAR.1 FAU_SAR.2 FCS_CKM.1 FCS_COP.1 FDP_ACC.1(a) FDP_ACC.1(b) FDP_ACF.1(a) FDP_ACF.1(b) X X X X X X X X X X X X X X X X Copyright (c) 2012 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
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92

Page 67 of
91
Copyright (c) 2012 RICOH COMPANY, LTD. All rights reserved.
Assurance Classes
Assurance Components
ATE_IND.2
Independent testing - sample
AVA:
Vulnerability assessment
AVA_VAN.2
Vulnerability analysis
6.3
Security Requirements Rationale
This section describes the rationale for security requirements.
If all security functional requirements are satisfied as below, the security objectives defined in "4 Security
Objectives" are fulfilled.
6.3.1
Tracing
Table 31 shows the relationship between the TOE security functional requirements and TOE security
objectives. Table 31 shows that each TOE security functional requirement fulfils at least one TOE security
objective.
Table 31 : Relationship between Security Objectives and Functional Requirements
O.DOC.NO_DIS
O.DOC.NO_ALT
O.FUNC.NO_ALT
O.PROT.NO_ALT
O.CONF.NO_DIS
O.CONF.NO_ALT
O.USER.AUTHORIZED
O.INTERFACE.MANAGED
O.SOFTWARE.VERIFIED
O.AUDIT.LOGGED
O.STORAGE.ENCRYPTED
O.RCGATE.COMM.PROTECT
FAU_GEN.1
X
FAU_GEN.2
X
FAU_STG.1
X
FAU_STG.4
X
FAU_SAR.1
X
FAU_SAR.2
X
FCS_CKM.1
X
FCS_COP.1
X
FDP_ACC.1(a)
X
X
X
FDP_ACC.1(b)
X
FDP_ACF.1(a)
X
X
X
FDP_ACF.1(b)
X