{"product_id":10150,"v_id":10150,"product_name":"Ricoh Hard Disc Security Module with imagio Security Module Type A, imagio Security Card Type A, DataOverwriteSecurity Unit Type A, and DataOverwriteSecurity Unit Type B","certification_status":"Not Certified","certification_date":"2007-05-16T00:05:00Z","tech_type":"Miscellaneous","vendor_id":{"name":"Ricoh USA, Inc.","website":"www.ricoh-usa.com"},"vendor_poc":null,"vendor_phone":"+81-3-5742-6765","vendor_email":"masahiro.itoh@nts.ricoh.co.jp","assigned_lab":{"cctl_name":"COACT, Inc. Labs"},"product_description":"<p class=\"textfollowingheader12\"><span lang=\"EN-GB\">The Hard Disk Security Module (HSM) is a software module executed on Multi-Function Printer (MFP) hardware and is contained on an SD memory card or DIMM-ROM providing adaptability to various MFP devices.<span style=\"\">&nbsp; </span>The HSM is delivered in a kit and each kit is adaptable to a suitable MFP device.<span style=\"\">&nbsp; </span>The kit contains the software either on a SD memory card or DIMM-ROM, an Operating Instruction Booklet or a CD-ROM containing the Operating Instruction Booklet and a Keytop version for each type of MFP device.<span style=\"\">&nbsp; </span>Table 1 in the Security Target identifies and describes the HSM kit, the item, and the MFP devices suitable for each HSM kit type.<span style=\"\">&nbsp; </span></span></p>\r\n<p style=\"margin-bottom: 6pt; text-align: justify;\" class=\"MsoNormal\">The HSM software provides the MFP with functionality that overwrites the Temporary Area of the Hard Disk Device (HDD).<span style=\"\">&nbsp; </span>The HSM function is automatic.<span style=\"\">&nbsp; </span>Once installed on the MFP device, the overwriting function becomes effective immediately.<span style=\"\">&nbsp; </span>It cannot be turned off, unless the software is removed.<span style=\"\">&nbsp; </span>There is, however, a priority scheme.<span style=\"\">&nbsp; </span>For practical MFP usability, the HSM function will become suspended if another application job accesses the HDD for writing or reading data.<span style=\"\">&nbsp; </span>Once that job is completed, the HSM resumes.<span style=\"\">&nbsp; </span>If the MFP power is disrupted either during HSM execution or if HSM is idle, upon power restore HSM is executed before user functionality can begin.<span style=\"\">&nbsp; </span>An icon on the printer control panel displays indicates when the HSM overwrite process has completed.<span style=\"\">&nbsp; </span><strong><o:p></o:p></strong></p>","evaluation_configuration":null,"security_evaluation_summary":"<p style=\"margin-bottom: 6pt; text-align: justify;\" class=\"MsoNormal\">The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The evaluation demonstrated that the Hard Disc Security Module with imagio Security Module Type A, imagio Security Card Type A, DataOverwriteSecurity Unit Type A, and DataOverwriteSecurity Unit Type B<span lang=\"EN-GB\" style=\"\"> TOE </span>meets the security requirements contained in the Security Target. <span style=\"background: yellow none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;\"><o:p></o:p></span></p>\r\n<p style=\"margin-bottom: 6pt; text-align: justify;\" class=\"MsoNormal\">The criteria against which the Hard Disc Security Module with imagio Security Module Type A, imagio Security Card Type A, DataOverwriteSecurity Unit Type A, and DataOverwriteSecurity Unit Type B<span lang=\"EN-GB\" style=\"\"> TOE were </span>judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.2. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 2.2. The COACT, Inc. CAFE Lab determined that the evaluation assurance level (EAL) for the Hard Disc Security Module with imagio Security Module Type A, imagio Security Card Type A, DataOverwriteSecurity Unit Type A, and DataOverwriteSecurity Unit Type B<span lang=\"EN-GB\" style=\"\"> TOE </span>is EAL 3. The TOE, configured as specified in the installation guide, satisfies all of the security functional requirements stated in the Security Target. <span style=\"background: yellow none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;\"><o:p></o:p></span></p>\r\n<p style=\"margin-bottom: 6pt; text-align: justify;\" class=\"MsoNormal\">A Validator on behalf of the CCEVS Validation Body monitored the evaluation carried out by the COACT, Inc. CAFE Lab. The evaluation was completed in March 2007. Results of the evaluation and associated validation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report.</p>","environmental_strengths":"<p>The TOE&rsquo;s Security Functions are:<br />\r\n<br />\r\nSF.RANDOMBUFFERS<br />\r\n<br />\r\nThe TOE Security Function SF.RANDOMBUFFERS generates buffers containing two passes of random data and one pass of nulls that are passed to the OS and used by the OS to overwrite copy and print data located in the Temporary Storage Area of the MFP HDD.&nbsp; SF.RANDOMBUFFERS inspects a table resident in memory (maintained by the IT Environment) for notification that residual data exists in the Temporary Storage Area of the MFP HDD.&nbsp; Upon discovery of the existence of residual data, SF.RANDOMBUFFERS seeks permission to begin the overwrite process.&nbsp; Once permission is given SF.RANDOMBUFFERS obtains random numbers from the IT Environment and generates buffers containing two passes of random data and one pass of nulls and sends these buffers to the OS to perform the overwrite.&nbsp; The TOE uses the standard rand() Unix function call for generating random numbers to populate the buffers with random data, but the TOE does not claim the use of a &ldquo;random number generator&rdquo; as specified by FIPS 140-2.&nbsp; The IT Environment is responsible for writing the supplied buffers to the designated locations on the HDD.<br />\r\n<br />\r\n<strong>SF.SELFPROTECT</strong><br />\r\n<br />\r\nAt each start-up, MFP firmware outside the TOE boundary checks to see if the TOE is physically installed (i.e., the DIMM or SD memory card is present).&nbsp; If the TOE is present, the IT Environment loads it into RAM for execution as a separate process.&nbsp; In order to remove the software from the MFP, the DIMM or SD memory card must be physically removed and the MFP device restarted.&nbsp; The TOE uses limited interfaces and cannot be directly accessed by a user.&nbsp; These interfaces use standard Unix socket-based communication channels where each communication path has a specified ID that ensures an exclusive connection and prevents access by other modules.&nbsp;</p>","features":[]}