Fiery Security White Paper

Fiery FS150 Pro /FS150 Servers running on

Microsoft® Windows® 10 IoT Enterprise 2016 LTSB

Date of Issue: May 2018

White Paper Series

Fiery Security White Paper

Table of Contents

1 Document Overview............................................................................... 3 5 Operating System Environment............................................................ 8

1.1 EFI Security Philosophy........................................................................ 3 5.1  Start-up Procedures............................................................................ 8
1.2 Configure the Security Feature Via Fiery Configure............................. 3 5.2 Linux.................................................................................................... 8
5.2.1 Linux Antivirus Software................................................................ 8
2 Hardware and Physical Security............................................................. 4 5.3  Windows 10........................................................................................ 8
2.1 Volatile Memory................................................................................... 4 5.3.1  Microsoft Security Patches........................................................... 8
2.2 Nonvolatile Memory and Data Storage............................................... 4 5.3.2  Windows Update Tools.................................................................. 8
2.2.1 Flash Memory................................................................................ 4 5.3.3  Windows Antivirus Software......................................................... 8
2.2.2 CMOS............................................................................................ 4 5.4  Email Viruses....................................................................................... 9
2.2.3 NVRAM.......................................................................................... 4
2.2.4 Hard Disk Drive.............................................................................. 4 6 Data Security...........................................................................................10
2.2.5 Physical Ports................................................................................. 4 6.1 Encryption of Critical Information.......................................................10
2.3 Local Interface..................................................................................... 4 6.2 Standard Printing................................................................................10
2.4 Removable HDD Kit Option................................................................. 4 6.2.1  Hold, Print and Sequential Print Queues.....................................10
2.4.1 For External Servers....................................................................... 4 6.2.2  Printed Queue..............................................................................10
2.4.2 For Embedded Servers.................................................................. 4 6.2.3  Direct Queue (Direct Connection)................................................10
6.2.4  Job Deletion.................................................................................10
3 Network Security..................................................................................... 5 6.2.5  Secure Erase................................................................................10
3.1 Network Ports...................................................................................... 5 6.2.6  System Memory..........................................................................11
3.2 IP Filtering............................................................................................ 5 6.3  Secure Print........................................................................................11
3.3 Network Encryption............................................................................. 5 6.3.1 Workflow......................................................................................11
3.3.1 IPsec.............................................................................................. 5 6.4  Email Printing.....................................................................................11
3.3.2 SSL and TLS................................................................................... 5 6.5  Job Management...............................................................................11
3.3.3 Certificate Management................................................................ 6 6.6  Job Log..............................................................................................11
3.4 IEEE 802.1X......................................................................................... 6 6.7 Setup..................................................................................................11
3.5 SNMP V3.............................................................................................. 6 6.8 Scanning............................................................................................11
3.6 Email Security...................................................................................... 6
3.6.1 POP before SMTP......................................................................... 6 7 Conclusion...............................................................................................12
3.6.2 OP25B............................................................................................ 6

4 Access Control......................................................................................... 7
4.1 User Authentication............................................................................. 7
4.2 Fiery Software Authentication............................................................. 7

Copyright © 2017 Electronics For Imaging, Inc. All rights reserved.

This publication is protected by copyright, and all rights are reserved. No part of it may be copied, reproduced, distributed, disclosed or transmitted in any form or by any means for any purpose without express prior written
consent from Electronics For Imaging. Information in this document is subject to change without notice and does not represent a commitment on the part of Electronics For Imaging. Electronics For Imaging, Inc. assumes
no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability,
fitness for particular purposes, and non-infringement of third party rights. The software described in this publication is furnished under license and may only be used or copied in accordance with the terms of such license.

2
1 Document Overview

This document gives end users an 1.1  EFI Security Philosophy

overview of the Fiery server’s architecture EFI understands that security is one of the top concerns
® ™

for business worldwide today, so we’ve built strong security

and functional aspects as they relate to features into the Fiery servers to protect companies’ most
device security in the Fiery FS150/FS150 valuable assets. We also proactively work with our global
Pro servers. It covers hardware, network OEM partners and our cross-functional teams to determine
companies’ current and future security requirements so that
security, access control, operating system security doesn’t become an issue with our products.
and data security. As always, we still recommend that end users combine
Fiery security features with other safeguards, such as
The document’s intent is to help end users secure password and strong physical security procedures, to
achieve overall system security.
understand all the Fiery server’s security
features that they can benefit from and to 1.2  Configure the Security Feature
understand its potential vulnerabilities. via Fiery Configure
Fiery users who access security the Fiery server via
Fiery Command WorkStation® using the Administrator
login can configure all Fiery features via Fiery Configure.
Fiery Configure can be launched from Fiery Command
WorkStation or WebTools™ under the Configure tab.

3
2 Hardware and Physical Security

2.1  Volatile Memory is carried out at the appropriate time to securely erase
The Fiery server uses volatile RAM for the CPU’s local deleted data on the HDD.
memory and for the operating system, Fiery system 2.2.5  Physical Ports
software and image data’s working memory. Data that is
The Fiery server can be connected through the following
written to RAM is held while the power is on. When the
external ports:
power is turned off, all data is deleted.
Fiery Ports Function Access Access Control
2.2  Nonvolatile Memory and Data Storage Ethernet RJ-45 Ethernet Network connections Use Fiery IP filtering
The Fiery server contains several types of nonvolatile data connector connectivity (see printing and to control access
network connections
storage technologies to retain data on the Fiery server below)
when the power is turned off. This data includes system Copier interface Print/Scan Dedicated for sending/ N/A
programming information and user data. connector receiving to/from the
print engine
2.2.1  Flash Memory USB Port USB device Plug-and-play USB printing can be
connection connector designed turned off. Access to
Flash memory stores the self-diagnosis and boot program for use with optional USB storage devices
(BIOS) and some system configuration data. This device is removable media can be turned off
programmed at the factory and can be reprogrammed only devices through Windows’
Group Policy.
by installing special patches created by EFI. If the data is
corrupted or deleted, the system does not start.
2.3 Local Interface
A portion of the flash memory also is used to record the
use of dongle to activate Fiery software options. The user can access the Fiery functions at the FACI kit (if
enabled on a Windows 10 server) or at the Fiery LCD on
No user data is stored on this device, and the user does Fiery servers. Security access on the Fiery Server with FACI
not have data access to it. kit is controlled through a Windows administrator password
2.2.2 CMOS if the FACI kit is enabled. The Fiery LCD provides very
limited functions that do not impose any security risk.
The battery-backed CMOS memory is used to store the
server’s machine settings. None of this information is 2.4  Removable HDD Kit Option
considered confidential or private. Users may access
these settings on a Windows 10 IoT Enterprise 2016 LTSB The Fiery server supports a Removable Hard Disk Drive
(Windows 10) server via the Fiery Integrated Workstation option kit for increased security. This kit allows the user to
(FACI kit including local monitor, keyboard and mouse) lock the server drive(s) into the system for normal operation
if installed. and to remove the drives to a secure location after powering
down the server.
2.2.3 NVRAM
2.4.1  For External Servers
There are a number of small NVRAM devices in the
Fiery server that contain operational firmware. These devices Fiery servers support a Removable Hard Disk Drive option
contain non–customer specific operational information. The kit. Whether this option kit is available for a specific Fiery
user does not have access to the data contained on them. product depends on the terms of EFI’s development and
distribution agreements with its individual OEM partners.
2.2.4  Hard Disk Drive
2.4.2  For Embedded Servers
During normal print and scan operations as well as during
creation of job management information, image data is Embedded products can only offer removable HDD as an
written to a random area on the hard disk drive (HDD). OEM coordinated option because the mounting location
and brackets for the multifunction printer (MFP) must be
Image data and job management information can be deleted developed jointly with the OEM. The option kit is to take the
by an Operator or at the end of a pre-set time period, making internal HDD out from embedded chassis and mount to an
image data inaccessible. external and separately powered enclosure.
To protect the image data from unauthorized access, EFI
provides a Secure Erase feature (see section 6.2.5). Once
4
enabled by the system administrator, the selected operation
3 Network Security

Standard network security features on the Fiery server include TCP UDP Port Name Dependent Service(s)
the ability to permit only authorized users and groups to access 6310 9906 EFI ports Command WorkStation 5
and print to the output device, limiting device communications 8010 and 6, Fiery Central, EFI
8021–8022 SDK-based tools, Fiery
to designated IP addresses and controlling the availability of
8090 Printer Driver bi-di functions,
individual network protocols and ports as desired. 9906 WebTools, Fiery Direct
18021 Mobile Printing, and Native
Even though Fiery servers come with various security 18022 Document Conversion.
features, it is not an internet facing server. It should be 18081
deployed in a protected environment and its accessibility 18082
21030
should be properly configured by the network administrator. 22000
50006 - 50025*
3.1  Network Ports 9100–9103 Printing Port Port 9100
The Fiery server allows the network administrator the ability * These ports are enabled once Fiery Command WorkStation version 6.2 and later is
to selectively enable and disable the following IP ports. As a installed on an external Fiery server.

result, unwanted device communication and system access

via specific transport protocols can be effectively blocked. Other TCP ports, except those specified by the OEM, are
TCP UDP Port Name Dependent Service(s)
disabled. Any service dependent on a disabled port cannot
be accessed remotely.
20–21 FTP
80 HTTP WebTools, IPP The Fiery Administrator also can enable and disable the
135 MS RPC Microsoft® RPC Service
different network services provided by the Fiery server.
(Windows 10 only). An The local administrator can define SNMP read and write
additional port in the range
49152-65536 will be opened community names and other security settings.
to provide SMB-related point
and print service. 3.2  IP Filtering
137–139 NETBIOS Windows Printing
The Administrator can restrict authorized connections with
161, 162 SNMP WebTools, Fiery Central, the Fiery server from those hosts whose IP addresses fall
some legacy utilities, other
SNMP-based tools within a particular IP range. Commands or jobs sent from
427 SLP non-authorized IP addresses are ignored by the Fiery server.
443 HTTPS WebTools, IPP/s
445 SMB/IP SMB over TCP/IP
3.3  Network Encryption
500 ISAKMP IPsec 3.3.1 IPsec
515 LPD LPR printing, some legacy
IPsec or Internet Protocol security provides security to
utilities (such as WebTools,
older versions of CWS) all applications over IP protocols through encryption and
631 IPP IPP authentication of each and every packet.
3050 Firebird The Fiery server uses pre-shared key authentication to
4500 IPsec NAT IPsec establish secure connections with other systems over IPsec.
5353 Multicase DNS Bonjour Once secure communication is established over IPsec
3389 RDP Remote Desktop (Windows between a client computer and a Fiery server, all
Fiery servers only)
communications — including print jobs — are securely
3702 3702 WS-Discovery WSD
transmitted over the network.

3.3.2  SSL and TLS

SSL/TLS are application-level protocols used for transmitting
messages over the Internet securely. Fiery servers support
SSL v2/v3 and TLS v1 protocols.
Various Fiery server features support SSL/TLS. Users can
access Fiery server’s home page and Web APIs securely
5
over SSL/TLS. Connection to LDAP servers and email 3.6  Email Security
servers can be configured to work over SSL/TLS to ensure The Fiery server supports the POP and SMTP protocols.
secure communication. To protect the service against attack and improper use, the
3.3.3  Certificate Management Fiery Administrator can enable additional security features
such as the following:
Fiery servers provide a Certificate Management interface
to manage the certificates used in various SSL/TLS 3.6.1  POP before SMTP
communications. It supports the X.509 certificate format. Some email servers still support unsecured SMTP protocol
Certificate Management allows the Fiery Administrator to do that allows anyone to send email without authentication.
the following: To prevent unauthorized access, some email servers
• Create self-signed digital certificates. require email clients to authenticate over POP before using
SMTP to send an email. For such email servers, the Fiery
• Add a certificate and its corresponding private key for the Administrator would need to enable POP authentication
Fiery server.
before SMTP.
• Add, browse, view and remove certificates from a trusted
certificate store. 3.6.2 OP25B
Outbound port 25 blocking (OP25B) is an antispam measure
3.4  IEEE 802.1x whereby ISPs may block packets going to port 25 through
802.1x is an IEEE standard protocol for port-based network their routers. The email configuration interface allows the
access control. This protocol provides an authentication Fiery Administrator to specify a different port.
mechanism before the device gets access to the LAN and its
resources.
When enabled, the Fiery server can be configured to use EAP
MD5-Challenge or PEAP-MSCHAPv2 to authenticate to an
802.1x authentication server.
Fiery server authenticates at boot time or when the Ethernet
cable is disconnected and reconnected.

3.5  SNMP v3
The Fiery server supports SNMPv3 as it is a secured
network protocol for managing devices on IP networks.
SNMPv3 communication packets can be encrypted to
ensure confidentiality. It also ensures message integrity
and authentication.
The Fiery Administrator can select from three levels of security
in SNMPv3. The Fiery Administrator also has the option to
require authentication before allowing SNMP transactions and
to encrypt SNMP user names and passwords.

6
4 Access Control

4.1  User Authentication 4.2  Fiery Software Authentication

The Fiery server user authentication feature allows the The Fiery server defines Administrator, Operator and Guest
Fiery server to do the following: users. These users are specific to the Fiery software and
• Authenticate user names. are not related to Windows-defined users or roles. It is
• Authorize actions based on the user’s privileges. recommended that Administrators require passwords to
access the Fiery server. Additionally, EFI recommends that
The Fiery server can authenticate users who are:
the Administrator change the default password to meet the
• Domain-based: users defined on a corporate server end user’s security requirements.
and accessed via LDAP.
• Fiery-based: users defined on the Fiery server. The three users on the Fiery server allow access to the
following privileges:
The Fiery server authorizes a users’ actions based on their
group membership. Each group is associated with a set of • Administrator — Gets full control over all of the Fiery server’s
functionalities.
privileges (e.g., Print in B&W, Print in color or B&W), and the
• Operator — Has most of the same privileges as the
actions of group members are limited to those privileges. Administrator, but has no access to some server functions,
The Fiery Administrator can modify the privileges of any such as set-up, and cannot delete the job log.
Fiery Group with the exception of the Administrator, • Guest (default; no password) — Has most of the same
privileges as the Operator but cannot access the job log, cannot
Operator and Guest accounts. make edits and cannot make status changes to print jobs and
For this version of User Authentication, the different privilege preview jobs.
levels that can be edited or selected for a group are as follows:
• Print in B&W — This privilege allows group members to
print jobs on the Fiery server. If the user does not have the
“Print in Color and B&W” privilege, the Fiery server forces the
job to print in black and white (B&W).
• Print in Color and B&W — This privilege allows group members
to print jobs on the Fiery server with full access to the color
and grayscale printing capabilities of the Fiery servers. Without
this or the Print in B&W privilege, the print job fails to print and
users are not able to submit the job via FTP (color devices only).
• Fiery Mailbox — This privilege allows group members to
have individual mailboxes. The Fiery server creates a mailbox
based on the username with a mailbox privilege. Access to
this mailbox is limited to users with the mailbox username/
password.
• Calibration — This privilege allows group members to perform
color calibration.
• Create Server Presets — This privilege allows group members
to create Server Presets in order to allow other Fiery users
access to commonly used Job Presets.
• Manage Workflows — This privilege allows group members to
create, publish or edit Virtual Printers.

Note: User Authentication replaces Member Printing/Group

Printing features.

7
5 Operating System Environment

5.1  Start-up Procedures 5.3.2  Windows Update Tools

The operating system and Fiery system software are loaded Windows-based Fiery servers are capable of using standard
from the local HDD during startup. Microsoft methods to update all applicable Microsoft
The BIOS resident on the Fiery motherboard is read-only security patches. The Fiery server does not support any
and stores the information needed to boot up the operating other third-party update tools for retrieving security patches.
system. Changes to the BIOS (or removal of the BIOS) EFI has its own dedicated system update tool to handle
prevent the Fiery server from functioning properly. Fiery software patches.
The Configuration Page lists the values specified during 5.3.3  Windows Antivirus Software
setup. Some information, such as FTP proxy information, In general, antivirus software can be used with a Fiery
password information, and SNMP Community Names, are server. Antivirus software comes in many varieties and
not included on the Configuration Page. may package many components and features to address
a particular threat. Here are a few guidelines to help
5.2 Linux customers have confidence in the antivirus software they
Linux systems do not include a local interface that allows choose. Please note that antivirus software is most useful in
access to the operating system. a local FACI kit configuration, where users have the potential
to infect the Fiery server with a virus through standard
5.2.1  Linux Antivirus Software
Windows actions. For Fiery servers without a FACI kit, it is
The Linux operating system used on Fiery servers is a still possible to launch antivirus software on a remote PC
dedicated OS for Fiery servers only. It has all of the OS and scan a shared Fiery server hard drive. However, EFI
components needed by a Fiery server, but not some suggests that the Fiery Administrator work directly with the
of the general-purpose components for Linux systems, such antivirus software manufacturer for operational support. The
as Ubuntu. In addition to having better performance, this following are the EFI guidelines for each of the components
dedicated OS is not subject to the same virus vulnerability of Windows antivirus software:
as a general-purpose Linux system and Microsoft OS. The
Virus engine — When an antivirus engine scans the Fiery
antivirus software designed for a general-purpose Linux OS
server, regardless of whether it’s a scheduled scan or not, it
may not be able to run on Fiery servers.
may affect Fiery performance.
5.3  Windows 10 Antispyware — An antispyware program may affect Fiery
The Fiery server ships with a default Windows 10 performance when files are coming into a Fiery server.
administrator password. It is recommended that the Examples are incoming print jobs, files that download
administrator change the password upon installation. during a Fiery System Update or an automatic update of
It is also highly recommended to change the password applications running on a Fiery server.
regularly in compliance with the organization’s IT policy. The Built-in firewall — Since the Fiery server has a firewall,
administrator password gives a user full access to the antivirus firewalls are not generally required. EFI
Fiery server locally and/or from a remote workstation. recommends that customers work with their own IT
That includes, but is not limited to, the file system, system department and refer to section 3.1 of this document if there
security policy and registry entries. In addition, this user is a need to install and run a built-in firewall that comes as
can change the administrator password, denying anyone else part of antivirus software.
access to the Fiery server. Antispam — Fiery supports print-via-email and scan-to-email
5.3.1  Microsoft Security Patches features. We recommend that a server-based spam filtering
mechanism be used. Fiery servers can also be configured
Microsoft regularly issues security patches to address to print documents from specified email addresses. The
potential security holes in the Windows 10 operating antispam component is not required because running a
system. The default setting of Windows Update to notify separate email client (such as Outlook) on the Fiery server is
users of patches without downloading them is disabled. not a supported operation.
As a result, the Windows Update status is not up to date.
Clicking on “Check for updates” enables the automatic
updates and starts the update immediately.
8
Whitelist and blacklist — The whitelist and blacklist
functionalities should not typically have adverse effects
on the Fiery server. EFI strongly recommends that the
customer configure this functionality so that it does not
blacklist Fiery modules.

HID and application control — Because of the complex

nature of HID and application control, the antivirus configu-
ration must be tested and carefully confirmed when either
of these features is in use. When tuned properly, HID and
application control are excellent security measures and
coexist with the Fiery server. However, it is very easy to
cause server issues with the wrong HID parameter settings
and wrong file exclusions — many times caused by
“accepting the defaults.” The solution is to review the
selected options in HID and/or application control settings in
conjunction with Fiery server settings such as network ports,
network protocols, application executables, configuration
files, temp files and so on.

5.4  Email Viruses

Typically, viruses transmitted via email require some type
of execution by the receiver. Attached files that are not PDL
files are discarded by the Fiery server. The Fiery server also
ignores email in RTF or HTML or any included JavaScript.
Aside from an email response to a specific user based on
a received command, all files received via email are treated
as PDL jobs. Please see the details on Fiery email printing
workflow in Section 6.4 in this document.

9
6 Data Security

6.1  Encryption of Critical Information EFI does not recommend printing to the Direct Queue. Fiery
Encryption of critical information in the Fiery server ensures deletes all jobs sent via the direct connection after printing.
that all passwords and related configuration information are However, EFI does not guarantee that all temporary files
secure when stored in the Fiery server. NIST 2010 compliant relating to the job will be deleted.
cryptographic algorithms are used. Jobs of VDP, PDF or TIFF file types are rerouted to the Print
Queue when sent to the Direct Queue. Jobs sent via the
6.2  Standard Printing SMB network service may be routed to the Print Queue
Jobs submitted to the Fiery server may be sent to one of when sent to the Direct Queue.
the following print queues published by the Fiery server:
6.2.4  Job Deletion
• Hold Queue
When a job is deleted from the Fiery automatically or using
• Print Queue
Fiery tools, the job cannot be viewed or retrieved using Fiery
• Sequential Print Queue
tools. If the job was spooled to the Fiery HDD, the job’s elements
• Direct Queue direct connection
may remain on the HDD and could theoretically be recovered
• Virtual Printers (custom queues defined by the
Fiery Administrator). with certain tools, such as forensic disk analysis tools.

The Fiery Administrator can disable the Print Queue and 6.2.5  Secure Erase
Direct Queue to limit automatic printing. With passwords Secure Erase is designed to remove the content of a
enabled on the Fiery server, this feature limits printing to submitted job from the Fiery HDD whenever a Fiery function
Fiery Operators and Administrators. deletes a job. At the instance of deletion, each job source file
is overwritten three times using an algorithm based on US
6.2.1  Hold, Print and Sequential Print Queues DoD specification DoD5220.22M.
When a job is printed to the Print Queue or the Hold Queue, The following limitations and restrictions apply to Secure Erase:
the job is spooled to the hard drive on the Fiery server. Jobs
• It does not apply to job files located in systems other than the
sent to the Hold Queue are held on the Fiery hard drive Fiery server, such as the following:
until the user submits the job for printing or deletes the job – Copies of the job load balanced to another Fiery server.
using a job management utility, such as the Fiery Command – Copies of the job archived to media or network drives.
WorkStation, Fiery Command WorkStation ME or Clear Server. – Copies of the job located on client workstations.
The Sequential Print Queue allows the Fiery to maintain the job – Pages of a job merged or copied entirely into another job.
order on certain jobs sent from the network. The workflow will • It does not delete any entries from the job log.
be “First In, First Out” (FIFO), respecting the order in which the • If the system is manually powered off before a job deletion has
completed, there is no guarantee that the job will be fully deleted.
jobs were received over the network. Without Sequential Print
• Jobs deleted before this feature is enabled are not securely
Queue enabled, print jobs submitted through the Fiery can get erased.
out of order due to many factors, such as the Fiery allowing • It does not delete any job data that may have been written to
smaller jobs to skip ahead while larger jobs are spooling. disk due to disk swapping.
• It disables automatic defragmentation on Windows OS. If
6.2.2  Printed Queue enabled, the OS could move job data around as it defragments.
Jobs sent to the Print Queue are stored in the Printed In that case, portions of the job data in the original location
might not be overwritten for a secure erase.
Queue on the Fiery server, if enabled. The Administrator
• Jobs submitted through an FTP server may be saved by the FTP
can define the number of jobs kept in the Printed Queue. client before being passed to the Fiery system software. Because
When the Printed Queue is disabled, jobs are deleted the Fiery system software has no control over this process, the
automatically after being printed. system cannot securely erase the jobs saved by the FTP client.
• Jobs printed via SMB go through the spooler on the Fiery,
6.2.3  Direct Queue (Direct Connection) which saves the jobs to disk. Because the Fiery system
software has no control over this process, the system
Direct Queue is designed for font downloading and cannot securely erase these jobs.
applications that require direct connection to PostScript
module in Fiery controllers. Note: Disk swapping occurs to create more virtual memory
than there is physical memory. This process is handled
in the operating system layer, and the Fiery server has
10
no control over it. However, disk swap space is regularly 6.6  Job Log
rewritten during the operating system operation as various The job log is stored on the Fiery server. Individual records of
segments of memory are moved between memory and the job log cannot be deleted. The job log contains print and
disk. This process can lead to some job segments being scan job information, such as the user who initiated the job;
stored to disk temporarily. the time the job was carried out; and characteristics of the
6.2.6  System Memory job in terms of paper used, color and so on. The job log can
be used to inspect the job activity of the Fiery server.
The processing of some files may write some job data to the
operating system memory. In some cases, this memory may A user with Operator access can view, export or print the
be swapped to the HDD and is not specifically overwritten. job log from Fiery Command WorkStation. A user with
Administrator access can delete the job log from the Fiery
6.3  Secure Print Command WorkStation. A user with Guest access can print
The Secure Print function requires the user to enter a job- the job log from the Fiery LCD only if this access is granted
specific password at the Fiery server to allow the job to print. by the Administrator.
This feature requires an LCD interface local to the Fiery server.
6.7 Setup
The feature’s purpose is to limit access to a document to a
Setup requires an administrator password. The Fiery server
user who (a) has the password for the job and (b) can enter
can be set up either from the Fiery Configure tool or from
it locally at the Fiery server.
setup in Fiery LCD. The Fiery Configure tool can be launched
6.3.1 Workflow from the Fiery WebTools and Fiery Command WorkStation.
The user enters a password in the Secure Print field in the
6.8 Scanning
Fiery Driver. When this job is sent to the Fiery server’s Print
or Hold Queue, the job is queued and held for the password. The Fiery server allows an image placed on the copier glass
to be scanned back to the workstation that initiated the scan
Note: Jobs sent with a secure print password are not
using a Fiery TWAIN plug-in. The plug-in is supported with
viewable from Fiery Command WorkStation or Fiery
the Adobe® Photoshop and Textbridge applications. When a
Command WorkStation ME.
scan function is initiated from a workstation, the raw bitmap
From the Fiery LCD, the user enters a Secure Print window image is sent directly to the workstation.
and enters a password. The user can then access the jobs
The user can scan documents to the Fiery server for
sent with that password and print and/or delete the jobs.
distribution, storage and retrieval. All scanned documents are
The printed secure job is not moved to the Printed Queue. written to disk. The Administrator can configure the Fiery server
The job is deleted automatically, once it has finished printing. to delete scan jobs automatically after a predefined timeframe.
6.4  Email Printing Scan jobs can be distributed via the following methods:
The Fiery server receives and prints jobs sent via email. • Email — In this process, an email is sent to a mail server,
where it is routed to the desired destination. Note: If the file
The Administrator can store a list on the Fiery server of size is greater than the Administrator-defined maximum, the job
authorized email addresses. Any email received from an is stored on the Fiery HDD, which is accessible through a URL.
email address that is not in the authorized email address list • FTP — The file is sent to a FTP destination. A record of the
is deleted. The Administrator can turn off the email printing transfer, including the destination, is kept in the FTP log, which
is accessible from the LCD Print Pages command. An FTP Proxy
feature. The email printing feature is off by default. Server can be defined to send the job through a firewall.
• Fiery Hold Queue — The file is sent to the Fiery Hold Queue
6.5  Job Management (see 6.2.1 section above) and is not kept as a scan job.
Jobs submitted to the Fiery server can only be acted • Internet Fax — The file is sent to a mail server where it is
upon by using a Fiery job management utility with either routed to the desired Internet fax destination.
Administrator or Operator access. Guest users (those • Mailbox — The file is stored on the Fiery server with a mailbox
code number. The user needs to enter the correct mailbox number
users with no password) can view the file names and job to access the stored scan job. Some Fiery server versions also
attributes but can neither act upon nor preview these jobs. require a password. The scan job is retrievable through a URL.

11
 7 Conclusion

EFI offers a robust set of standard features and

options on the Fiery server to help our customers
meet the need for a comprehensive and customizable
security solution for any environment. EFI is committed
to ensuring that our customers’ businesses run at
top efficiency and effectively protect the Fiery server
against vulnerabilities from either malicious
or unintentional use. Therefore, EFI is continually
developing new technologies to provide comprehensive
and reliable security solutions for the Fiery server.

6750 Dumbarton Circle Auto-Count, BioVu, BioWare, ColorWise, Command WorkStation, Digital StoreFront, DocBuilder, DocBuilder Pro, DocStream, EDOX, the EFI logo, Electronics For Imaging,
Fabrivu, Fiery, the Fiery logo, Inkware, Jetrion, MicroPress, OneFlow, PressVu, Printellect, PrinterSite, PrintFlow, PrintMe, PrintSmith Site, Prograph, RIP-While-Print, UltraVu
Fremont, CA 94555 and VUTEk are registered trademarks of Electronics For Imaging, Inc. in the U.S. and/or certain other countries. BESTColor is a registered trademark of Electronics For Imaging
650-357-3500 GmbH in the U.S. The APPS logo, AutoCal, Balance, ColorPASS, Dynamic Wedge, EFI, Estimate, Fast-4, Fiery Driven, the Fiery Driven logo, Fiery Link, Fiery Prints, the Fiery
Prints logo, Fiery Spark, FreeForm, Hagen, the Jetrion logo, Logic, Pace, Printcafe, the PrintMe logo, PrintSmith, Print to Win, PSI, PSI Flexo, Rastek, the Rastek logo, RIPChips,
www.efi.com SendMe, Splash, Spot-On, UltraPress, UltraTex, UV Series 50, VisualCal, the VUTEk logo and WebTools are trademarks of Electronics For Imaging, Inc. in the U.S. and/or certain
other countries. Best, the Best logo, Colorproof, PhotoXposure, Remoteproof and Screenproof are trademarks of Electronics For Imaging GmbH in the U.S. and/or certain other
countries. All other terms and product names may be trademarks or registered trademarks of their respective owners, and are hereby acknowledged.

© 2017 Electronics For Imaging GVP.057.06.17_US