Operating instructions

CRP-C0266-01
30
items of the TOE" are developed by the developer and are used after confirming that they are
normally operated.
Table 7-2 Tools for the Developer Testing
Name of tool Outline and purpose of use
WireShark 1.0. 2 Tool to obtain or monitor packets over LAN (software)
Zenmap 4.68 Tool to investigate use of communication port of
computer connected with network (software)
Debugging console to
monitor the TOE
internal operation
A debugging console to monitor the TOE internal
operation is software installed in the computer. This tool
was developed by RICOH COMPANY, LTD. for testing
and is not publically available. The computer with the
installed debugging console and the controller board for
the TOE were connected by special serial connectors and
a special debugging serial cable. This tool was used to
specify necessary testing items to check TOE internal
operations.
SD card for changing or
overwriting the internal
configuration items of
the TOE
The SD card stores programs and data for testing that
performs changing and overwriting the internal
configuration items of the TOE, which were developed
in accordance with the testing items. This tool was used
to specify necessary testing items to check TOE internal
operations.
<Content of execution of the developer testing>
The values of testing plans expected in advance that is described in the expected testing
results of individual testing specifications which are evidence materials provided by the
developer was compared with the values of the developer testing results described in the
notes of the individual testing items (judgments) of the individual testing result reports
which are evidence materials provided by the developer as well. As a result, it was found that
the expected results are consistent with the actual testing results of testing evidence
materials.
b. Scope of Execution of the Developer Testing
The developer testing is executed about 513 items (1008 cases) by the developer.
By the coverage analysis, it was verified that all Security Functions and external interfaces
described in the functional specification had been tested.
By the depth analysis, it was verified that all subsystems and subsystem interfaces indicated
in the TOE design had been tested enough.
c. Result
The evaluator confirmed consistencies between the testing results expected by the developer
and the actual testing results executed by the developer.
The evaluator confirmed an approach of the executing developer testing and legitimacy of
tested items, and confirmed consistencies between testing approach described in the testing
plan and actual testing approach.
7.3.2 Evaluator Independent Testing
The evaluator executed the evaluator independent testing to reconfirm that Security
Functions are certainly implemented from the evidence shown by the process of the
evaluation. The following explains the evaluator independent testing executed by the