Encryption Between Server And Embedded/On-Board Applications

This KB article relates to PaperCut MF, the edition of PaperCut that implements copier control

Some customers may have a requirement to understand how traffic is encrypted between PaperCut and the embedded or on-board applications running on their MFDs.

The following on-board application platforms, where functionality is delivered via web-services, utilise secure HTTPS for communications:

• Brother
• HP - FutureSmart
• Konica Minolta
• Riso
• Sharp
• Xerox

The following Embedded application platforms, where PaperCut software runs directly on the device, communicate over port 9193 using an XML-RPC-based protocol that encrypts sensitive data:

• Canon
• Dell
• HP - Chai
• Kyocera
• Lexmark
• Ricoh
• Samsung

Special notes for Toshiba and some Oki devices

eB3 platform:

1. Authentication is via LDAP, with credentials handled using standard LDAP mechanisms.
2. Logging is performed via SNMP traps, these traps are not encrypted. The traps report statistics such as number of pages copied, whether the pages were duplex, etc. This information is not considered. sensitive.
3. Device details via SNMPv2, which is not encrypted. This queried information covers data like the device serial number.This information is not considered. sensitive.
4. Web-services screens can be configured for HTTPS via EWB configuration during the device setup.

eBX platform:

1. Authentication is via LDAP, with credentials handled using standard LDAP mechanisms.
2. PaperCut queries usage data from the device via the Output Management SDK. HTTPS is not configurable for this connection, which does not have any sensitive data passed across it, for example device settings and job log data.
3. Web-services screens can be configured for HTTPS via EWB configuration during the device setup.

Please note Some brands may use a mixture of platforms. If unsure please contact support.