Home » Ricoh Manuals » Laser Printers » Ricoh Aficio SP C821DNT1 » Manual Viewer

Ricoh Aficio SP C821DNT1 Design Guide - Page 86

Certification of the SDK Application

View all Ricoh Aficio SP C821DNT1 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 86 highlights

Print Controller Design Guide for Information Security 4-3-6 Certification of the SDK Application Having completed the development of the production-level (product release) version of the SDK application, the Vendor must then request Ricoh to certify the application. When applying for Ricoh certification, the Vendor must provide Ricoh with the application's functional specifications, entire object code and all relevant evaluation results. Following this, Ricoh examines the information provided by the Vendor to ascertain in detail the full scope of the operations of the application, as well as to what extent the application has already been tested. These results are then documented (If deemed necessary, Ricoh may perform further testing on the application). As mentioned in section 3.1, if Ricoh determines that the application poses no particular issues or problems, the Vendor is provided with the necessary authentication files. By providing these files, Ricoh is certifying the application. If the Vendor then makes any changes to the application after receiving the authentication files from Ricoh, this Vendor must go through the entire certification process again to obtain new authentication files. It is therefore impossible for an SDK application to be successfully installed on the MFP/LP without the correct authentication files described in section 3.1. Ricoh utilizes this system to manage and control the specifications, operations and quality of SDK applications developed by Vendors, preventing the illegal installation of any SDK application that has not been fully certified as described above. Page 86 of 86

Section	Page
04/23/2010	1
For these details, please refer to the Operating Instructions for the specific machine in question.	6
Hardware Configuration	7
MFP	7
LP	9
TPM (Trusted Platform Module): When the MFP/LP main power is turned on, this security module (chip) performs a verification on the validity of the software installed on the hardware platform, which includes checking for any illegal alterations.	10
Shared Service Layers	11
Principal Machine Functions	12
Data Security	14
External I/F	14
Protection of Program Data from Illegal Access via an External Device	14
IC card-based authentication functions: Authentication is mutual and encrypted, which prevents impersonation and ensures that data is properly protected.	16
Firmware Installation/Update	17
Remote Firmware Installation via Web SmartDeviceMonitor Professional IS (performed by the end user)	19
Verification of Firmware/Program Validity	20
Note: Produced by STMicroelectronics, TPM is a product of the ST19WP18 family, which has earned Common Criteria certification (EAL5+).	20
Authentication	21
IC Card Authentication	24
Access Control	25
In addition, it is possible to create an access control list (ACL) for each individual Address Book entry and Document Server document at both the individual user and group levels.	25
If the MLP/LP is initialized in this way, all of the user information, document data, and settings stored in the MLP/LP since installation will be initialized (erased).	26
Data Erase/Overwrite	27
To execute the overwrite, the operator can choose from two options: \	28
The execution of this feature does not clear engine-related information such as the value of the total counter, or engine-related adjustment settings contained in SP mode and UP mode.	28
Through this arrangement, the copy of the HDD storage key is automatically decrypted once the Encryption Key Restore has been completed.	31
Document Server Documents (MFP models only)	33
Access Privileges and Operations for Stored Documents	34
Without HDD: 500 entries	38
Overview of Capture Operations	39
Operations that Generate Captured Images	39
Capture Settings	41
Security Considerations	42
Captured Documents and Log Data	42
Additional Methods for Increased Security	42
(Authentication not required)	42
Copier (MFP Models Only)	43
Overview of Copier Operations	43
Data Security Considerations	43
Protection of Copy Jobs in Progress	43
Protection of Document Server Documents	43
Refer to 1.7.2 Document Server Documents (MFP models only) for details on the Document Lock feature.	44
Restricting the Available Functions for Each Individual User	45
Job/Access Log Data Collection	45
Print Backup	45
(printing out, editing, copying).	46
Overview of Printer Operations	47
Data Flow	47
Data Security Considerations	51
The \	53
Overview of Scanner Operations	54
Data Flow Security Considerations	54
Protection of Data when Performing Scanning and Sending Operations	55
Protection of Document Server Documents	56
Protection of Sending Results and Status Information	57
Protection of the Scanner Features Settings	57
Data Stored in the Job Log	58
Terminology	58
FTP (File Transfer Protocol): A protocol used when transferring files over a TCP/IP network.	58
Overview of FAX operations	59
Data Security Considerations	60
Protection of the Journal and Documents in Document Server Storage	61
Protection of FAX Transmission Operations	61
Protection of FAX Features Settings	62
The \	62
Job Log	62
Protection of Internet FAX Transmissions using S/MIME	62
Preventing FAX Transmission to Unintended Destination(s)	63
This prevents a FAX from being sent to an unintended destination when, for example, the operator accidentally touches an additional Quick Dial key.	63
Overview of NetFile Operations	64
Data Flow	65
Supplementary	65
Network Topology for a System Using Integration Server Authentication (Sample)	66
As long as the track ID is not stolen from the communication path between the PC and MFP/LP (which can be protected against by enabling SSL encryption) or from the PC itself, it is impossible to perform any unauthorized operations on these print jobs	68
Web Server Framework	69
WebDocBox (MFP models only)	70
For more details on job and access logs, please refer to 1.9 Job/Access Logs.	72
@Remote	73
Overview of @Remote Operations	73
Data Security Considerations	73
Security is increased even further by the fact that the symmetric key used is not a static key, but rather one that is generated every time a new session is initiated.	73
Overview of Copy Data Security Operations	74
Data Flow	75
Following this, an entry for the event itself is stored in the access log, along with the username.	75
Overview of Operations	77
1	77
Overview of SDK Application Functions	79
3: DSDK Œ MFP/LP Hardware Configuration	79
Scanning Functions: Sending Data Over the Network with the Copier and Scanner (MFP models only)	80
FAX Functions (MFP models only)	80
Network Functions	81
Printer Functions	81
Machine Administrative Functions (MFP models only)	81
Authentication Functions	81
Data Security Considerations	83
Preventing the Installation of Illegal Applications	83
Authentication of SDK Applications at Installation	83
Prevention of Access to Address Book Data and Machine Management Data	85
Protection Against Attacks on Principal MFP/LP Functions, Prevention of Damage to the System	85
Protection Against Attacks from External Sources	85

Match case Limit results 1 per page

Print Controller Design Guide for Information Security

Page 86 of 86

4-3-6 Certification of the SDK Application

Having completed the development of the production-level (product release) version of the SDK

application, the Vendor must then request Ricoh to certify the application. When applying for Ricoh

certification, the Vendor must provide Ricoh with the application’s functional specifications, entire

object code and all relevant evaluation results.

Following this, Ricoh examines the information provided by the Vendor to ascertain in detail the full

scope of the operations of the application, as well as to what extent the application has already been

tested. These results are then documented (If deemed necessary, Ricoh may perform further testing

on the application). As mentioned in section 3.1, if Ricoh determines that the application poses no

particular issues or problems, the Vendor is provided with the necessary authentication files. By

providing these files, Ricoh is certifying the application.

If the Vendor then makes any changes to the application after receiving the authentication files from

Ricoh, this Vendor must go through the entire certification process again to obtain new authentication

files. It is therefore impossible for an SDK application to be successfully installed on the MFP/LP

without the correct authentication files described in section 3.1.

Ricoh utilizes this system to manage and control the specifications, operations and quality of SDK

applications developed by Vendors, preventing the illegal installation of any SDK application that has

not been fully certified as described above.