Fdp_sos.1 by assurance requirement, Toe security functional requirements dependency – Konica Minolta BIZHUB 920 User Manual
Page 81
are successfully identified and authenticated. It prevents the HDD1 and HDD2 from the
unauthorized access.
Therefore, OE.HDD can be realized by the correspondent security functional requirements.
8.2.1.3. Adequateness for supporting of security functional requirements - FDP_MTD.1 and
FDP_SOS.1 by assurance requirement
FDP_MTD.1 executes only changing “TSF data” of FMT_MTD.1 to “administrator data” and
means the same as FMT_MTD.1 “control the security function”. FDP_SOS.1 executes only
changing “secret” of FIA_SOS.1 to “secret for IT environment” and means the same as FIA_SOS.1
“validation of secret”.
Therefore, they can apply to the same assurance requirement with FMT_MTD.1 and FIA_SOS.1,
namely the present assurance requirement.
8.2.2. TOE Security Functional Requirements Dependency
All of the necessary dependent relationship of TOE security functional requirements is fulfilled as
shown in Table 8.3 Dependence Relationship of TOE Security Functional Requirements.
Table 8.3 Dependence Relationship of TOE Security Functional Requirements
No
TOE security
functional
requirement
Lower level
Dependent
Reference
No
Notes
1 FIA_UID.2
FIA_UID.1 None
2
FIA_UAU.2
FIA_UAU.1
FIA_UID.1
1
As the mediate action of
FIA_UID.1 is unnecessary,
FIA_UID.2 is used.
3
FIA_UAU.7
None
FIA_UAU.1
2
As the mediate action of
FIA_UAU.1 is unnecessary,
FIA_UAU.2 is used.
4
FIA_AFL.1
None
FIA_UAU.1
2
As the mediate action of
FIA_UAU.1 is unnecessary,
FIA_UAU.2 is used.
5 FIA_SOS.1[1]
None
None
6 FIA_SOS.1[2]
None
None
7 FDP_SOS.1
None
None
8 FDP_ACC.1[1]
None
FDP_ACF.1 10
Copyright© 2005 KONICA MINOLTA BUSINESS TECHNOLOGIES, INC., All Rights Reserved