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

Ricoh Aficio SP C820DN Design Guide - Page 84

Digital Authentication Type 2 only

View all Ricoh Aficio SP C820DN manuals

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

Page 84 highlights

Print Controller Design Guide for Information Security inside randomly-generated data. The locations of these hash values inside the key file are not disclosed to the Vendor. Using a special tool, Ricoh generates a unique key file for every SDK application that is approved. Among the entire group of specialists at Ricoh engaged in SDK application-related activities, only a select number of engineers have been granted the access rights to use and manage this special tool. When the SD card is inserted in the MFP/LP slot, the SAS reads the raw form of the product ID contained in the product ID file, as well as the hash value for the ID contained in the key file. The SAS then applies a unique hash function to the raw form of the product ID, and compares the resulting value with the hash value read from the key file. If these two values match, the SAS then reads the raw form of the SDK application object code stored in the SD card, as well as the hash value for the code contained in the key file. The SAS applies a unique hash function to the entire code, and then compares the resulting value with the hash value read from the keyfile. If these two values match, the name of the SDK application appears on the installation screen and the application can be installed on the MFP/LP. As demonstrated above, it is not possible to install an SDK application on the MFP/LP unless both of the following conditions have been satisfied: The SD card contains the key file and raw form of the product ID provided by Ricoh, as well as the raw form of the application object code developed by the Vendor, AND The two hash values generated by the MFP/LP for the product ID and application object code match those contained in the key file on the SD card. Digital Authentication (Type 2 only) For Type 2 applications, Ricoh embeds a digital signature inside the JAR files received from the Vendor, assigns an appropriate access level, and then returns the files to the Vendor. This allows the MFP/LP to authenticate the application as well as restrict its operations once installed. As a general rule, Ricoh assigns relatively restricted access privileges to Type 2 applications. These applications are normally prohibited from performing operations such as file storage to MFP/LP media or opening and closing sockets to communicate over the network. Vendors who wish to utilize such functions must make this request to Ricoh when applying for the digital signature. After having fully ascertained all relevant details on the proposed SDK application, including the Vendor's specific purpose for using the application on the MFP/LP in question, and having determined that the application poses no security threat to the MFP/LP, Ricoh approves the application and assigns the appropriate access level. Page 84 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 84 of 86

inside randomly-generated data. The locations of these hash values inside the key file are not

disclosed to the Vendor.

Using a special tool, Ricoh generates a unique key file for every SDK application that is approved.

Among the entire group of specialists at Ricoh engaged in SDK application-related activities, only a

select number of engineers have been granted the access rights to use and manage this special tool.

When the SD card is inserted in the MFP/LP slot, the SAS reads the raw form of the product ID

contained in the product ID file, as well as the hash value for the ID contained in the key file. The SAS

then applies a unique hash function to the raw form of the product ID, and compares the resulting

value with the hash value read from the key file.

If these two values match, the SAS then reads the raw form of the SDK application object code stored

in the SD card, as well as the hash value for the code contained in the key file. The SAS applies a

unique hash function to the entire code, and then compares the resulting value with the hash value

read from the keyfile. If these two values match, the name of the SDK application appears on the

installation screen and the application can be installed on the MFP/LP.

As demonstrated above, it is not possible to install an SDK application on the MFP/LP unless both of

the following conditions have been satisfied:

The SD card contains the key file and raw form of the product ID provided by Ricoh, as well as the

raw form of the application object code developed by the Vendor, AND

The two hash values generated by the MFP/LP for the product ID and application object code

match those contained in the key file on the SD card.

Digital Authentication (Type 2 only)

For Type 2 applications, Ricoh embeds a digital signature inside the JAR files received from the

Vendor, assigns an appropriate access level, and then returns the files to the Vendor. This allows the

MFP/LP to authenticate the application as well as restrict its operations once installed.

As a general rule, Ricoh assigns relatively restricted access privileges to Type 2 applications. These

applications are normally prohibited from performing operations such as file storage to MFP/LP media

or opening and closing sockets to communicate over the network. Vendors who wish to utilize such

functions must make this request to Ricoh when applying for the digital signature. After having fully

ascertained all relevant details on the proposed SDK application, including the Vendor’s specific

purpose for using the application on the MFP/LP in question, and having determined that the

application poses no security threat to the MFP/LP, Ricoh approves the application and assigns the

appropriate access level.