Home » Ricoh Manuals » Multifunction Devices » Ricoh Aficio MP 7001 SP » Manual Viewer

Ricoh Aficio MP 7001 SP Design Guide - Page 18

to the @Remote Center GUI

View all Ricoh Aficio MP 7001 SP manuals

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

Page 18 highlights

Print Controller Design Guide for Information Security Remote Firmware Update In addition to using an SD card, it is also possible to update the firmware by transmitting the firmware files to the MFP/LP via a remote connection. Since these files are transmitted over public Internet communication paths in some cases, routed through multiple servers before reaching their destination, it is necessary to use the authentication process described above for remote updates as well. The process for remote updates is virtually the same as that for the SD card-based update described above, with the following differences: Remote headers are attached to the digital signature before the files are sent to the MFP/LP. If the update is interrupted for some reason, it is possible to retry the update by resending the file. There are three main scenarios in which a remote firmware update is performed, the process for which is the same as described above (see illustrations below). In each scenario, all of the security features described above are employed. The update is performed by a field engineer in the field via a PC The update is performed using the @Remote function, normally by an individual with access rights to the @Remote Center GUI The update is performed via Web SmartDeviceMonitor Professional IS, usually by the end user 1. Check remote headers to confirm that a remote update is being requested 4. Files are sent 2. Verification of model and target machine functions (Copier, Printer, etc.) 3. Verification of firmware version Program 5. Generate MD1 using SHA-1 If MD1 ≠ MD２ Update process is cancelled and new firmware is not installed MD１ Digital signature 7. Compare MD and MD2 6. Decryption Public key MD２ 8. Firmware is overwritten with new files If MD1 = MD2 Digital signature Ricoh distribution server Program + digital signature Program Ricoh license server 1. Generate MD using SHA-1 MD Digital signature 2. Generate digital signature Private key 3. Download Client PC Remote Firmware Installation Performed by a Field Technician (from a client PC) Page 18 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 18 of 86

Remote Firmware Update

In addition to using an SD card, it is also possible to update the firmware by transmitting the firmware

files to the MFP/LP via a remote connection. Since these files are transmitted over public Internet

communication paths in some cases, routed through multiple servers before reaching their destination,

it is necessary to use the authentication process described above for remote updates as well. The

process for remote updates is virtually the same as that for the SD card-based update described

above, with the following differences:

Remote headers are attached to the digital signature before the files are sent to the MFP/LP.

If the update is interrupted for some reason, it is possible to retry the update by resending the file.

There are three main scenarios in which a remote firmware update is performed, the process for which

is the same as described above (see illustrations below). In each scenario, all of the security features

described above are employed.

The update is performed by a field engineer in the field via a PC

The update is performed using the @Remote function, normally by an individual with access rights

to the @Remote Center GUI

The update is performed via Web SmartDeviceMonitor Professional IS, usually by the end user

Digital

signature

Program

5. Generate MD1

using SHA-1

１

２

Public key

6. Decryption

7. Compare

MD and MD2

If MD1

≠

２

Update process is cancelled and

new firmware is not installed

If MD1 = MD2

3. Verification of firmware version

8. Firmware is overwritten

with new files

2. Verification of model and target

machine functions (Copier, Printer, etc.)

Ricoh license server

Digital signature

2. Generate

digital signature

Program

1. Generate MD

using SHA-1

Private key

3. Download

1. Check remote headers to confirm that a

remote update is being requested

Ricoh distribution server

Client PC

4. Files are sent

Program + digital

signature

Digital

signature

Remote Firmware Installation Performed by a Field Technician

(from a client PC)