A shared printer or multifunction device (MFD) is a computer with a hard drive, a network stack, a web server, and an output tray holding whatever someone printed last. Left at factory defaults, anyone who walks up to it can copy, scan to any email address, change its network settings from a browser, or pick up the salary report the previous user forgot. Four device-level controls close those gaps: user authentication, badging, audit logs, and secured prints. All four are configured on the MFD itself or on the print server that manages it, which is why they sit in the printer objective rather than in general security theory.
User authentication on the device
Out of the box, most MFDs treat everyone at the control panel the same. Turning on user authentication makes the device ask "who are you?" before it copies, scans, faxes, or releases a print job. Once it knows who is standing there, it can decide what that person is allowed to do and record what they did.
Ways an MFD can identify a user
- User codes or department codes. A short number typed at the panel. Simple and common on copiers used for departmental charge-back, but codes get shared and written on sticky notes, so accountability is weak.
- Local accounts with a PIN or password. Accounts stored on the device. Fine for a handful of users on one machine; a management burden across a fleet, because every leaver has to be removed from every device.
- Directory authentication (LDAP or Active Directory). The MFD checks the username and password against the domain, so people sign in at the panel with the same credentials they use at their PC. Disabling the account in the directory locks the person out of every printer at once. This is the setup most exam scenarios describe for a business network.
- Card or badge authentication. A tap of the employee's proximity or smart card identifies them. Covered in the badging section below.
What authentication lets you control
Authentication is the foundation for everything else on the device. With named users, the administrator can assign function permissions by user or group: staff may print in colour while students are limited to black and white; scan-to-email is enabled for the finance team only; fax is disabled for guest accounts. Scan-to-email can fill in the sender's own address from the directory, which stops one user sending scans that appear to come from someone else. Page quotas and job accounting also become possible, because every page is charged to a real name.
The administrator account counts too
The most neglected form of user authentication on a printer is the administrator password on its embedded web server (EWS), the settings site you reach by browsing to the printer's IP address. Many devices ship with a blank or well-known default password. Until it is changed, anyone on the network can alter the IP settings, redirect scan destinations, turn off logging, or factory-reset the device. Part of a proper deployment is to set a strong EWS password, switch the EWS to HTTPS, disable protocols you are not using (Telnet, FTP, SNMP v1/v2 with the public community string), keep the firmware patched, and where possible place printers on their own VLAN so only the print server and administrators can reach the management interface.
Exam tip: a scenario where "anyone can change the printer's network settings from a web browser" is pointing at the unset or default administrator password on the device's web interface, not at the users' Windows accounts.
Badging
Badging on an MFD means the same proximity or smart card that opens the office door also identifies the user at the printer. A card reader is mounted on or beside the device, and each badge's ID is linked to a user account in the print-management or authentication system. The badge does two jobs:
- Authentication. A tap signs the user in at the panel with their permissions applied, replacing a typed username and password.
- Release. A tap releases that user's held print jobs. This is badge release, the most common form of secured printing in larger organizations.
Enrolling badges
Badges have to be associated with accounts before they work. Two approaches are common.