Specifications

Print Controller Design Guide for Information Security:
Page 12 of 92
4. Communication between the MFP/LP and its peripherals is conducted via the peripheral I/F using
Ricoh-unique protocols. These exchanges are limited to pre-determined commands and data, and only
take place after the MFP/LP has recognized the peripheral device. If the MFP/LP receives illegal data
from the peripheral, it will judge that a perhiperal device failure has occurred or that the device is not
connected. This prevents any illegal access to internal programs or data.
5. The MFP communicates with external coin/card-operated devices through the External Charge Device
I/F in accordance with the same protocols used for its peripherals described in #4 above. It is possible
to utilize such devices in tandem with the access control settings for each user, in which case the
device and MFP exchange the relevant information (e.g. User Code data).
6. With the @Remote function, the MFP/LP is connected via the network to a Ricoh-developed device
known as RC Gate, which is then connected to the @Remote Center, or to the @Remote Center
directly. When connecting to the center directly, the MFP/LP communicates via a LAN connection over
the Internet. Before transferring any data, mutual authentication is performed using digital certificates
between the MFP/LP and RC Gate or MFP/LP and @Remote Center, which ensures that the MFP/LP
cannot connect to any device other than RC Gate or to its single, pre-assigned @Remote Center.
Communication between RC Gate/@Remote Center and the MFP/LP modules responsible for
@Remote operations is performed over exclusive socket-based connections, as described in #2 above.
In addition, it is also possible to change the MFP/LP settings to prohibit @Remote communication.
7. Communication with an external controller is performed via the VideoLink board over a serial
connection, which uses a Ricoh-original communication protocol. The internal arrangement is
designed such that the external controller cannot gain access to the MFP internal modules until after it
has successfully cleared the device registration process.
In addition, although the external controller is capable of operations such as issuing printing
instructions, sending data for storage in the MFP Document Server and downloading/restoring data to
and from the MFP, the controller is not able to alter any of the original files already stored in the MFP.
(e.g. When the controller restores a file back to the MFP, it is always saved as a separate file).
8. The standard IEEE1284 parallel I/F, USB I/F (Type B), and Bluetooth I/F treat all incoming data as print
data. This print data can only be sent to pre-specified modules responsible for executing printing
operations. In addition, using MFP/LP settings, it is possible to disable each interface individually.