rfg042419 PDF
rfg042419 PDF
2/3/2011
Technical Information:
Network Security
White Paper
Document Version H.1.1
Brand
Product
Code
Ricoh
Savin
Gestetner
Lanier
D023
D025
Aficio MP C2800
Aficio MP C3300
C2828
C3333
MP C2800
MP C3300
MP C2800/LD528C
MP C3300/LD533C
D027
D029
Aficio MP C4000
Aficio MP C5000
C4040
C5050
MP C4000
MP C5000
MP C4000/LD540C
MP C5000/LD550C
D038
D041
Aficio MP C2050
Aficio MP C2550
C9020
C9025
MP C2050
MP C2550
MP C2050/LD520C
MP C2550/LD525C
D037
D040
Aficio MP C2030
Aficio MP C2530
C9020L
C9025L
MP C2030
MP C2530
MP C2030/LD520CL
MP C2530/LD525c
G190
Aficio SP C411DN
Aficio SP C410DN
CLP31DN
CLP27DN
C7531dn
C7526dn
LP231c/SP C411
LP226c/SP C410
Page 1 of 68
NOTICE:
This document may not be reproduced or distributed in whole or in part, for any purpose or in any
fashion without the prior written consent of Ricoh Company limited. Ricoh Company limited retains the
sole discretion to grant or deny consent to any person or party.
All product names, domain names or product illustrations, including desktop images, used in this
document are trademarks, registered trademarks or the property of their respective companies. They are
used throughout this book in an informational or editorial fashion only. Ricoh Company, Ltd. does not
grant or intend to grant hereby any right to such trademarks or property to any third parties. The use of
any trade name or web site is not intended to convey endorsement or any other affiliation with Ricoh
products.
The content of this document, and the appearance, features and specifications of Ricoh products are
subject to change from time to time without notice. While care has been taken to ensure the accuracy of
this information, Ricoh makes no representation or warranties about the accuracy, completeness or
adequacy of the information contained herein, and shall not be liable for any errors or omissions in these
materials. The only warranties for Ricoh products and services are as set forth in the express warranty
statements accompanying them. Nothing herein shall be construed as constituting an additional
warranty. Ricoh does not provide legal, accounting or auditing advice, or represent or warrant that our
products or services will ensure that you are in compliance with any law. Customer is responsible for
making the final selection of solution and technical architectures, and for ensuring its own compliance
with various laws such as the Gramm-Leach-Bliley Act, the Sarbanes-Oxley Act and the Health
Insurance Portability and Accountability Act (HIPAA).
Version
Issue Date
Revised item
H1.0
Initial release
H.1.1
11,24,2010
NOTE:
Throughout this document you may see references such as 04A (2004 Autumn) or 05S (2005 Spring).
You will only see an A (Autumn) or S (Spring) attached to the last two digits of a year.
These two seasons reflect the time period the machines were manufactured.
Target Readers:
1. All end users: The information contained in the document can be distributed to end users as long as
you follow the restrictions outlined on page 2.The main target readers are IT Administrators. When
distributing this document to end users, region specific information including model names must be
modified.
2. The regional support and marketing staff of each regional company
3. The support and marketing staff of Ricoh Sales companies including Ricoh family group companies
and their subsidiaries.
4. Technical support personnel (CEs) of dealers.
Page 2 of 68
Terms:
The following terms are used in this document. Please familiarize yourself with them.
The products: This refers to the digital multifunction and printing devices covered by this document, as
noted in the Model Cross Reference table. The term the products refers to all of these machines
collectively.
Host Interface: This refers to the physical interface of the Ethernet board on the products.
SSL: SSL: Is a communication technology used for secure connections between 2 hosts. The primary
goal of the SSL Protocol is to provide privacy and reliability between two communicating applications.
SSL is layered on top of some reliable transport protocol (e.g., TCP). SSL allows the server and client to
authenticate each other and to negotiate an encryption algorithm and cryptographic keys before the
application protocol transmits or receives its first byte of data.
SSH2 (Secure Shell): Is intended as a replacement for rlogin, rsh, and rcp. Additionally, ssh provides
secure X connections and secure forwarding of arbitrary TCP connections. Ricohs implementation of
SSH is based on OpenSSH 3.9.
Product
Code
Ricoh
Savin
Gestetner
Lanier
D023
D025
Aficio MP C2800
Aficio MP C3300
C2828
C3333
MP C2800
MP C3300
MP C2800/LD528C
MP C3300/LD533C
D027
D029
Aficio MP C4000
Aficio MP C5000
C4040
C5050
MP C4000
MP C5000
MP C4000/LD540C
MP C5000/LD550C
D038
D041
Aficio MP C2050
Aficio MP C2550
C9020
C9025
MP C2050
MP C2550
MP C2050/LD520C
MP C2550/LD525C
D037
D040
Aficio MP C2030
Aficio MP C2530
C9020L
C9025L
MP C2030
MP C2530
MP C2030/LD520CL
MP C2530/LD525c
G190
Aficio SP C411DN
Aficio SP C410DN
CLP31DN
CLP27DN
C7531dn
C7526dn
LP231c/SP C411
LP226c/SP C410
NOTE: Parts of this document may not apply to some models. For example, printer models do not have
scanners. Therefore some uses of RSH (for scanning) do not apply to these models.
Page 3 of 68
Table of Contents:
1. Introduction .................................................................................................................. 7
1-1
1-2
TELNET .......................................................................................................................... 8
1-3
1-4
1-5
1-6
1-7
1-8
1-9
1-2-1
1-2-2
Potential threats.............................................................................................................. 8
FTP ............................................................................................................................... 10
1-3-1
1-3-2
1-3-3
1-4-2
1-4-3
Recommended Precaution............................................................................................ 12
HTTP ............................................................................................................................ 13
1-5-1
1-5-2
1-5-3
HTTPS .......................................................................................................................... 14
1-6-1
1-6-2
1-6-3
1-7-2
1-7-3
SNMP v3 ....................................................................................................................... 16
1-8-1
1-8-2
1-8-3
1-9-2
1-9-3
1-10 LPD............................................................................................................................... 18
1-10-1
1-10-2
1-10-3
Recommended Precaution............................................................................................ 18
Page 4 of 68
1-11-2
1-11-3
Recommended Precaution............................................................................................ 19
1-12-2
1-12-3
1-13-2
1-13-3
1-14-2
1-14-3
Recommended Precaution............................................................................................ 21
1-15-2
1-15-3
Recommended Precaution............................................................................................ 22
1-16-2
1-16-3
Recommended Precaution............................................................................................ 22
1-17-2
1-17-3
Recommended Precaution............................................................................................ 23
1-18-2
1-18-3
Recommended Precaution............................................................................................ 24
Page 5 of 68
2-2
Overview ...................................................................................................................... 25
2-1-2
IPsec ............................................................................................................................. 27
2-2-1
Overview ...................................................................................................................... 27
2-2-2
3. APPENDIX ................................................................................................................... 29
3-1
3-2
3-3
3-2-2
3-2-3
3-2-4
3-2-5
3-2-6
3-2-7
3-4
Configuration ................................................................................................................ 53
3-4-2
3-4-3
3-4-4
3-4-5
Page 6 of 68
1.
Einführung
This document describes potential network threats and recommended precautions for them.
The products have built-in network services for providing a variety of features for wired and wireless
network clients, such as network scanning, printing or faxing, and also client services for accessing
network servers running outside the products, such as an LDAP server, Netware server, or Mail server.
This document focuses on how-to protect against potential threats from external attacks.
As the products are designed for use inside an Intranet where network clients and servers are protected
by firewalls, the products rely on the Intranets security policy, like the security provided by other network
servers and clients. However, some customers require more strict security levels for network devices,
because potential threats from inside the firewalls are increasing, and some configurations even use a
secure connection to the Internet as a part of the Intranet.
To satisfy these demands, the products are all evaluated by security scanning applications during
development, and also are checked for known vulnerability issues reported by Internet security
organizations, such as CERT Coordination Center (CERT/CC : HTTP:// www.cert.org/ ). Whenever we
find security vulnerabilities in the products, we provide appropriate countermeasures.
Page 7 of 68
We also recommend using the Access Control function for added security. Access Control is a list of
safe client host addresses. Once Access Control is setup for specific IP addresses, the products will
receive print or scan requests from the specified hosts only. Access Control can be applied to LPR
printing, RSH/RCP access, Bonjour access, HTTP/HTTPS access, FTP printing, TCP raw printing
(DIPRINT), SMB printing, IPP printing, scanning from DeskTopBinder. Access Control can also be used
for WSD-printing, WSD-Scanning, IPDS printing, and RHPP printing. For information on how to set up
Access Control, please refer to the Appendix section entitled Access Control.
In the following sections, the potential threats and recommended precautions are given for each service.
For added security, the recommended precautions should be accompanied by a firewall and Access
Control.
1-2 TELNET
1-2-1 Function Overview:
The TELNET service provides a virtual terminal service in order to use the maintenance shell (mshell). It
is compliant with RFC 854. The mshell uses TCP port 23 and provides a dedicated command interface
for the following functions.
Configuring network settings of the products from remote terminals
Monitoring device status and settings from remote terminals
Getting system logs from remote terminals
Unlike shell services for UNIX/Linux, the mshell provides a command interface for configuration
purposes only. Access to the file system or kernel, or modifying system files inside the products is very
unlikely.
Page 8 of 68
Page 9 of 68
1-3 FTP
1-3-1 Function Overview
The FTP (File Transfer Protocol) service is compliant with RFC 959. TCP port 20 is used for the FTPdata service and TCP port 21 is used for the FTP-control service. In order to work with the products, FTP
clients must be compliant with RFC 959.
The following functions are provided by the FTP service.
Description
Attribute
Syslog
System log
Read-only
Stat
Printer Status
Read-only
Prnlog
Print log
Read-only
Info
Printer Information
Read-only
Help
Help
Read-only
SmartDeviceMonitor for
Fax counter
Admin/Client is required
by users.
rwx - - - - - -
RFU requires Machine administrator privileges. When Web Smart Device Monitor is used for RFU, TCP
port 10020/10021 are used to send firmware files via the FTP protocol. However, port 21 is used to
negotiate the transfer. All 3 ports must be open. RFU is a proprietary process defined by Ricoh and is
extremely difficult to emulate. However if a strict security policy is to be maintained, that port can be
closed via TELNET.
Page 10 of 68
Page 11 of 68
Page 12 of 68
1-5 HTTP
1-5-1 Function Overview
The HTTP (Hypertext Transfer Protocol) service provides web services. This service is compliant with
RFC 1945. TCP port 80 is used for the HTTP service.
The following functions are provided by the HTTP server service.
Access to the products address book using Address Management Tool in SmartDeviceMonitor
for Admin.
NOTE: When logging into Web Image Monitor in Administrator mode, the user must enter the username
and password. It is the same as the username and password used for the mshell.
Page 13 of 68
1-6 HTTPS
1-6-1 Function Overview
HTTPS is HTTP over SSL (Secure Socket Layer). HTTPS provides the same functions as HTTP. HTTPS
maintains higher security than HTTP because SSL provides the following features:
Identity verification
Data integrity verification
Communicating with the client PC for Scanning using the TWAIN driver.
Although the SNMP service is not protected by a password, it is protected using unique community
names and assigned access rights (read-only, read-write and trap) within those communities. Access
rights allow users read or modify data in the MIB embedded in the products.
Default settings of SNMP community names are follows:
Read-only: public
Read-Write: admin
Page 15 of 68
1-8 SNMP v3
1-8-1 Function Overview
SNMP v3 provides the same functions as SNMP v1/v2. SNMP v3 maintains higher security than SNMP
v1 and v2 because SNMP v3 has the following features:
User Authentication
Data Encryption
Page 16 of 68
1-10 LPD
1-10-1 Function Overview
The LPD service is compliant with RFC 1179 and uses TCP port 515 for connections with an RFC 1179
compliant client. The following functions are provided by this service.
Monitoring the status of the printer and print queues from LPR clients.
Page 18 of 68
1-11 IPP
1-11-1 Function Overview
The IPP (Internet Printing Protocol) service is used for Internet printing from IPP clients. This service is
compliant with RFC 2565 and it uses TCP port 631.
The following functions are provided by the IPP service.
The IPP service can have up to 10 password protected user accounts for the IPP the service. Both
BASIC and DIGEST authentication are supported. BASIC authentication sends the username and
password in clear text. DIGEST authentication is more secure with the username and password
hashed.
Both authentication methods are selectable in Web Image Monitor and mshell.
IPP authentication can also be disabled. In this case, usernames and passwords are not authenticated
(The default setting is disabled.).
Page 19 of 68
1-13 SMB
1-13-1 Function Overview.
The SMB service uses NBT (NetBIOS over TCP/IP) as its base layer.
The NBT service provides the NetBIOS service over TCP/IP instead of NetBEUI. Using this service, a
remote host can access network services of the products by the NetBIOS name (Computer Name)
instead of IP address. This service uses 3 ports, UDP port 137 for NetBIOS-NS (NetBIOS Name
Service), UDP port 138 for NetBIOS-DGM (NetBIOS Datagram Service) and TCP port 139 for NetBIOSSSN (NetBIOS Session Service). SMB (Server Message Block) over TCP/IP provides the following
services:
Page 20 of 68
1-14 MDNS
1-14-1 Function Overview
MDNS (Multicast DNS) is a way of using familiar DNS programming interfaces, packet formats and
operating semantics, in a small network where no conventional DNS server has been installed. The
products only use MDNS for Bonjour. If Bonjour is not being used, this port can be closed.
Page 21 of 68
1-15 H323hostcall/SIP
1-15-1 Function Overview
H323/SIP services are used to provide VoIP (Voice over IP) for IP-Fax. The H.323 hostcall service is
compliant with ITU-T standards and uses TCP port 1720. The SIP service is compliant with RFC3261
and uses TCP/UDP port 5060.
1-16 SSDP
1-16-1 Function Overview
SSDP (Simple Service Discovery Protocol) is used for both advertising services and searching for
services on UPnP network. SSDP uses UDP port 1900. If UPnP is not being used, this port can be
closed.
Page 22 of 68
1-17 WS-Device
1-17-1 Function Overview
WS-Device (Web Service Device) is a Windows Vista standard. This service is compliant with Device
Profile for Web Services (February 2006).
The following functions are provided by the WS-Device service.
Providing details about the device and available services. (WS-Transfer / WSMetadataExchange)
1-18 IPDS
1-18-1 Function Overview
Intelligent Printer Data Stream (IPDS) is a structured field data stream. It allows both data and
commands to be streamed to the printer via channels, controllers or any type of networking link, which
supports the transparent transmission of data to print processes that are resident in the device.
This service uses following TCP/UDP port:
TCP 5001: Used for transmitting data and printer control commands.
Page 23 of 68
1-19 RHPP
Though MFPs of all regions support RHPP, Ricoh has not released any RHPP servers outside of Japan.
So we do not force the need for this service in the near future. Please close the ports.
This service uses the following TCP/UDP port:
TCP 59100: Used for transmitting data and printer control commands.
NOTE: As of 2008, there are no RHPP print servers on the market outside of Japan.
1-20 Others
TCP port 7443 and 7444 are reserved for @Remote. If a strict security policy is to be maintained, those
ports can be closed via TELNET. (Please refer to the Appendix for a list of ports)
HTTPS is used for this service as an underlying layer. Please refer to the HTTPS section for the
potential threats and recommended precautions for HTTPS.
Page 24 of 68
2.
The Previous section dealt mainly with physical port based network services. This section will describe
security related information for network services not based on physical ports.
WPA
WEP
TKIP
CCMP
Encryption algorithm
RC4
RC4
AES
40/104 bit
104 bit
128 bit
No / No
Yes / Yes
Page 25 of 68
WPA employs four authentication modes: WPA-PSK, WPA2-PSK, WPA (802.1X) and WPA2
(802.1X). WPA-PSK and WPA2-PSK are similar to WEP in that a pre-shared key is used to join the
network. However, a new encryption key is generated in handshake process, making WPA-PSK and
WPA2-PSK more secure than WEP. WPA (802.1X) and WPA2 (802.1X) are much more strict than the
PSK protocols. Only users that can be authenticated by a RADIUS server using EAP are allowed to join
the network. Supported EAP authentication types are:
EAP-TLS
EAP-TTLS
PEAP
LEAP
SSID only (no encryption)
All data (including the SSID) is transmitted in plain text. It is easily readable by anyone within range of
the wireless transmission.
WEP
WEP provides RC4 encryption of data and is therefore more secure than using only an SSID. However
the weaknesses of RC4 encryption and WEP in general are well documented.
NOTE: WPA TKIP uses RC4. However, because the keys are being constantly refreshed, the key will
change before it can be cracked.
WPA
In WPA, the encryption key is generated at interval by TKIP or CCMP. The key does not need to be
entered manually. As the key is refreshed so often, a brute force attack is almost impossible.
Furthermore, CCMP uses AES, which is a stronger encryption method than RC4. As an added
precaution, WPA (802.1X) /WPA2 (802.1X) provide user authentication.
2-2 IPsec
2-2-1 Overview
Internet Protocol Security (IPsec) is a suite of protocols which provides secure communication over the
network layer. IPsec provides authentication, data integrity, and protection against replay attacks. Unlike
SSL which functions between the application and transport layers, IPsec functions in the network layer.
The products can offer the following header extensions.
AH
Authentication, integrity (IP header and the payload).
No encryption.
ESP
Authentication, encryption, (payload only).
AH+ESP
Authentication, encryption, (IP header and the payload).
The Ricoh implementations for the encryption and authentication algorithm are:
Encryption:
Clear Text (No encryption)
DES
3DES
AES-128
AES-192
AES-256
Authentication:
HMAC-MD5-96
HMAC-SHA1-96
The encryption or authentication keys can be set manually or generated automatically using IKE.
NOTE: IPsec are disabled for DHCP, DNS, WINS, and HTTPS by default. IPsec can be applied to these
protocols by enabling it in mshell.
Page 28 of 68
3.
APPENDIX
Port Num.
Login
TELNET
23/TCP
FTP-control
21/TCP
HTTP
80/TCP
netbios-ns
137/UDP
netbios-dgm 138/UDP
netbios-ssn 139/TCP
Username
Password
Password
Note
Changeable
Changeable
This is the same username and password as
Y
Y
Y
are used for Web Image Monitor.
N
N
N
For RFU, administrator privilege is required.
This is the same username and password as
Y
Y
Y
are used for TELNET. The unauthorized users
can only read access is available.
N
SNMP
161/UDP
SNMPv3
161/UDP
HTTPS
443/TCP
514/TCP
515/TCP
RSH/RCP
(shell)
LPD
IPP
631/TCP
H323gatestat 1719/UDP
Port Num.
H323hostcall 1720/TCP
Login
Password
Username
Password
Note
Changeable
Changeable
products can register its information with
gatekeeper.
N
SSH
22/TCP
SIP
5060/TCP, UDP
MDNS
5353/UDP
@Remote
7443/TCP
7444/TCP
SSDP
1900/UDP
DIPRINT
9100/TCP
RFU
10021/TCP
WS-Printer
WS-Scanner
WS-Device
WSDiscovery
IPDS
RHPP
53001/TCP
53002/TCP
N
N
N
N
N
N
N
N
53000/TCP
3702/TCP
5001/TCP
59100/TCP
N
N
N
N
N
N
N
N
Page 30 of 68
Protocol
Protocol Suite
IP
ICMP
UDP
TCP
FTP-data
FTP-control
SMTP
Domain (DNS)
BOOTP
DHCP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP, IPX/SPX
TCP/IP
POP
TCP/IP
110/tcp, udp
SNTP
NETBIOS-NS
NETBIOS-DGM
NETBIOS-SSN
IMAP
SNMP-trap
LDAP
syslog
TCP/IP
123/tcp, udp
137/tcp, udp
138/tcp, udp
139/tcp, udp
143/tcp, udp
162/tcp, udp
389/udp, tcp
514/udp
TCP/IP
TCP/IP, IPX/SPX,
NetBEUI
TCP/IP
TCP/IP, IPX/SPX
TCP/IP
TCP/IP
Page 32 of 68
Login as Administrator
Page 33 of 68
Page 34 of 68
Input the range of IP addresses that you wish to permit communication with.
Click the OK button to commit the changes.
Page 35 of 68
E.g.1 Input the following command to permit only access from 172.16.1.0 to 172.16.2.0
msh> access 1 range 172.16.1.0 172.16.2.0
E.g.2 Input the following command to clear all access ranges.
msh> access flush
Page 36 of 68
If changes have been made, the following question will appear when the user tries to logout. Do
you save configuration data? Input yes to commit the changes, Input no to discard them.
Service/Prot
ocol
Port
Web Image
Monitor
mshell
Netware
AppleTalk
Y
IPv4
IPv6
Y
IPv4
Comment
Setting Netware to down,
disables the IPX/SPX
protocol and NCP/IP.
Therefore if Netware is
down, printing in the
IPX/SPX environment and
in the pure IP environment
is unavailable. LPR in
NDPS and iPrint (IPP
Printing) are unaffected.
IPv6
TCP/IP
FTP
21
SSH/SFTP
22
TELNET
23
SMTP
25
HTTP
80
IPP
631
NBT
137/138
SMB
139
SNMP
161
SSL
443
RSH/RCP
514
LPR/LPD
515
H.323
1720
SSDP
1900
MDNS
5353
SIP
5060
@Remote
7443/74
44
DIPRINT
9100
RFU
10021
RHPP
59100
IPDS
WS Discovery
/
WS Device
WS Printer
WS Scanner
5001
3702
53000
53001
53002
via mshell.
Setting SSDP to down
makes UPnP unavailable
and closes the SSDP port
(1900/UDP)
In order to close this port,
set Bonjour to down.
In order to close this port:
Configuration > Fax > IPFax Settings > Enable SIP
> Off (Web Image
Monitor).
This port cannot be closed
via mshell.
In order to disable this
service, type set nrs down
in mshell.
If this port is closed,
printing from diprint clients
is unavailable.
If this port is closed,
remote firmware update
will still be available via ftp.
However, if RFU is to be
used, we recommend
keeping this port open as
the ftp password is sent in
clear text.
If this port is closed, RHPP
is not available.
When either WS Device or
WS Printer/WS Scanner is
disabled via Web Image
Monitor or mshell, these
ports are both closed.
Page 39 of 68
Page 40 of 68
Page 41 of 68
Page 42 of 68
Page 43 of 68
Page 44 of 68
Ciphertext/Clear Text: Permit both HTTPS and HTTP connections. No forwarding of HTTP to
HTTPS.
Ciphertext Priority: Any incoming HTTP request that can be forwarded to HTTPS will be
forwarded. With this setting it will be possible to use HTTPS from Internet Explorer, Netscape
Navigator, etc. (HTTP will be forwarded) but not using IPP from SmartDeviceMonitor for Client
etc. (these requests can not be forwarded). If the request cannot be forwarded to HTTPS, HTTP
will be permitted.
Ciphertext Only: Permit only HTTPS connections. All incoming HTTP requests will be forwarded
to HTTPS. If the request cannot be forwarded, the connection will be rejected.
Page 45 of 68
HTTP/HTTPS settings
Security > SSL/TLS
In addition to the features described on the previous page, this feature is new .
NOTE:
The new features will only appear if specific versions of the firmware are applied:
MFP Model
Network Support
Web Support
D023/D025
8.30 or later
1.11 or later
D027/D029
8.30 or later
1.11 or later
D038/D041
D037/D040
8.30 or later
1.01 or later
Printer Model
Network Support
Web Support
Printer Support
G190
8.06
1.06
1.08
Page 46 of 68
Support for certificate signing using an RSA key length of 2048 bits.
Support for RSA encryption with a key length of 2048 bits (used for SSL).
512 bits
(md5WithRSA)
Page 47 of 68
SNMP
(This setting can be configured either from here or from the SNMPv3 settings.)
Enable: Opens the SNMP port
Disable: Closes the port completely. No SNMP communication of any version can be used.
SNMP v1/v2 Function
Enable: Allows the use of SNMP v1/v2.
Disable: Does not allow connections using SNMP v1/v2. This is recommended because SNMP v1/v2
doesnt have any mechanism for encryption or authentication, we recommend using Disable for
this setting unless absolutely necessary.
Permit Settings by SNMP v1 and v2
On: This enables SNMP set. It is used to write changes to settings.
Off: This disables SNMP set. Only get will be permitted. Therefore, settings can be read but not
changed.
Page 48 of 68
SNMP
(This setting can be configured either from here or from the SNMPv1/v2 settings.)
Enable: Opens the SNMP port
Disable: Closes the port completely. No SNMP communication of any version can be used.
SNMP v3 Function Enable: Allows communication using SNMP v3. Disable: Does not allow
communication via SNMP v3.
Authentication Algorithm
SHA1: Hashes the username and password using the SHA1 hashing algorithm.
MD5: Hashes the username and password using the MD5 hashing algorithm.
Permit SNMPv3 communication
Encryption Only: The username and password must be encrypted using the hashing algorithm selected
above.
Encryption/Clear Text: The username and password can be sent either encrypted or unencrypted.
Page 49 of 68
There are 3 different types of accounts that can be used for SNMPv3 connections. Only the User
account can be fully configured here. For information about fully configuring the Machine and Network
Administrator accounts, please refer to the Appendix section entitled Administrator Account Settings.
Account Name (User): This is the username that the user will use to login to SNMPv3.
Authentication Password (User): This is the password that the user will use to login to SNMPv3.
Encryption Password (User): This is the key used for SHA1 or MD5 hashing of the username and
password.
Page 50 of 68
mshell
You can configure SNMP settings using snmp commands from mshell. These commands can be
displayed by typing help snmp in mshell.
Page 51 of 68
MFP Administrator account settings can be changed from here. Administrator roles can be assigned to
any or all of up to 4 Administrators.
These settings affect the Administrator logins for TELNET, Web Image Monitor and SNMP v3.
Page 52 of 68
Page 53 of 68
Port open
Port 443
Port 7443/7444
Port open
Port open
Port 80
Port open
Port 443
Port open
Port 631
Port open
SSL
Encryption Mode
Ciphertext
Priority
DIPRINT
Port 9100
Port open
LPR
Port 515
Port open
FTP
SSH/SFTP
RFU
Port 21
Port 22
Port 10021
Port open
Port open
Port open
RSH/RCP
Port 514
Port open
Port
SNMP v1/v2 (Read)
SNMP v1/v2 (Write)
SNMP v3
Port open
Enabled
Enabled
Enabled
Automatic
TELNET
Port 23
Port open
SSDP
(UPnP)
Port 1900
Port open
mDNS
Port 5353
Port open
NBT
Port 137/138
Port open
SMB
Port 139
Port open
WS-Device
Port 3702/53000
Port open
WS-Printer
WS-Scanner
Port 53001
Port 53002
Port open
RHPP
Port 59100
Port open
IPDS
Port 5001
Port open
HTTP/HTTPS
IPP
TCP/IP
SNMP
Netware
AppleTalk
Netware
AppleTalk
Enabled
Enabled
Level 2
Disabled
Disabled
Enabled
Enabled
Port
Port open
open*1
Port open
Port open
Port open
Port open
Port open
Port open
*1
Port open
Port open
Port
Port open
closed
Ciphertext Ciphertext
Priority
Only *2
Port
Port open
closed
Port
Port open
closed
Port open
Port open
Port open
Port open
Port open
Port open
Port
Port open
closed
Port open
Port open
Enabled
Disabled
Disable
Disabled
Enabled
Enabled
Ciphertext
Automatic
Only
Port
Port closed
closed
Port
Port open
closed
Port
Port open
closed
Port
Port open
closed
Port
Port open
closed
Port
Port open
closed
Port
Port open
closed
Port
Port open
closed
Port
Port open
closed
Enabled
Disabled
Enabled
Disabled
*1: The port is open but cannot be used to access the web service because the SSL setting is Ciphertext Only.
*2: If the SSL setting is Ciphertext only, the products will still accept IPP jobs using port 80.
Page 54 of 68
Page 55 of 68
Communication Mode
802.11 Ad-hoc Mode: Ad-hoc connection using SSID.
Infrastructure Mode: Communicates using an access point and SSID.
Channel
Sets the radio frequency used. If Infrastructure mode is being used, this setting is unimportant as the
channel defined by the access point will be used automatically.
Security Method
Inactive: No encryption of data.
WEP: Uses WEP security.
WPA: Uses WPA security.
Page 56 of 68
WEP
WEP settings can only be configured if WEP is selected in IEEE802.11b Settings -> Security Type.
WEP Authentication
Open System: Anyone with the correct SSID can join the network.
NOTE: As the system uses a WEP key, simply joining the network is not enough to be able to receive or
send readable communications.
Shared Key: WEP key required to join the network.
WEP key number
Up to four WEP keys can be saved in the MFP. Select one of them.
WEP Key
Set the WEP key used for WEP encryption. If 64-bit key is used, 10 hexadecimal characters or 5
alphanumeric characters need to be entered. If a 128-bit key is used, 26 hexadecimal characters or 13
alphanumeric characters need to be entered.
Page 57 of 68
[WPA]
WPA settings can only be configured if WPA is selected in IEEE802.11b Settings -> Security Type.
WPA Encryption Method TKIP: Uses TKIP. CCMP: Uses CCMP.
WPA Authentication Method
WPA : Uses WPA (802.1X).
WPA2: Uses WPA2 (802.1X)
WPA-PSK: Uses WPA-PSK.
WPA2-PSK: Uses WPA2-PSK.
WPA-PSK/WPA2-PSK
PSK: Sets the pre-shared key used.
Page 58 of 68
Page 59 of 68
User Name: This is the username used for EAP authentication on the Radius server.
Domain Name: This is the domain name used for the authentication on the Radius server.
EAP Type: EAP-TLS, LEAP, EAP-TTLS, or PEAP
IEEE 802.1X Client Certificate Status: Displays the status of the device certificate specified for wireless
LAN connection in [Certification] on the [Device Certificate] page(None, Requesting, Installed,
Installed/Requesting)
Password: This is the password used for EAP authentication on the Radius server.
Phase 2 User Name: This is the user name used in phase 2 of EAP-TTLS and PEAP.
Phase 2 Methods (EAP-TTLS): If EAP-TTLS is selected as the EAP type, a Phase2 authentication
method must be selected. Select from CHAP, MSCHAP, MSCHAPv2, PAP, or MD5
Page 60 of 68
Phase 2 Methods (PEAP): If PEAP is selected as the EAP type, a Phase2 authentication method must
be selected. Select from MSCHAPv2 or TLS.
Authentication Server Certificate: Select whether the Radius Server is required to send a certificate to
connecting WPA (802.1x) client.
Trust Intermediate Certificate Authority: Select whether the certificate provided by the Radius Server
must be signed by a trusted CA.
Server ID: This is the CN (or the DC) of server certificate.
Permit Sub-domain: Select whether the server certificate is permitted for the sub-domain of server ID.
mshell
Configure Wireless LAN settings using wiconfig commands from mshell. For a list of commands, type
help wiconfig in mshell.
Page 61 of 68
Page 62 of 68
IPsec:
IPsec
Active: Activate IPsec
Inactive: Deactivate IPsec
Exclude HTTPS Communication
Active: Exclude HTTPS Communication for IPsec policy
Inactive: Do not exclude HTTPS communication for IPsec policy
Encryption Key Manual Settings
Active: When specifying SA parameters manually, select Active.
Inactive: When specifying SA parameters automatically, select Inactive
Page 63 of 68
Page 64 of 68
Security Protocol
ESP: Uses ESP
AH: Uses AH
AH+ESP: Uses dual mode (AH + ESP)
Authentication Algorithm: Select from HMAC-MD5-96 or HMAC-SHA1-96 as hashing algorithm
Authentication Key: Set the Authentication key used for hashing. For HMAC-MD5-96, enter up to 32 in
hexadecimal number, or up to 16 ASCII. For HMAC-SHA1-96, enter up to 40 in hexadecimal number, or
up to 20 ASCII
Encryption Algorithm: Select from Clear Text, DES, 3DES, AES-128, AES-192, or AES-256.
Encryption Key: Set the encryption key. If AH is selected as security protocol, this is grayed out. For
DES, enter up to 16 in hexadecimal number, or up to 8 ASCII. For 3DES, enter up to 48 in hexadecimal
number, or up to 24 ASCII. For AES-128, enter up to 32 in hexadecimal number, or up to 16 ASCII. For
AES-192, enter up to 48 in hexadecimal number, or up to 24 ASCII. For AES-256, enter up to 64 in
hexadecimal number, or up to 32 ASCII.
Page 65 of 68
Page 66 of 68
PFS
Inactive: Do not generate the encryption or authentication keys again.
1, 2, or 14: Diffie-Hellman Group for establishing IPsec SA in Phase 2.
Validity Period: Enter the number between 300 and 172800 seconds.
mshell
Configure IPsec settings using ipsec commands from mshell. For a list of commands, type help ipsec
in mshell.
Page 67 of 68
4.
REFERENCE LIST
RFC: HTTP://www.faqs.org/rfcs/
CVE: HTTP://cve.mitre.org/
CERT: HTTP://www.cert.org/
CIAC: HTTP://www.ciac.org/ciac/
NESSUS: HTTP://www.nessus.org/index2.html
Page 68 of 68