Xerox 6180N FreeFlow® Print Server Security Guide - Page 34

Prevent Unauthorized Queue Changes, Roles and responsibilities

Page 34 highlights

Prevent Unauthorized Queue Changes Queue Lock • Queues can be locked and unlocked by the System Administrator. • Properties of a locked queue cannot be changed without first unlocking the queue. • Locked queues can only be deleted by the System Administrator. • Locked queues can be copied by an Operator. The resulting new queue will not be locked. • An Operator can change the Accept/Do Not Accept Jobs and Release/Do Not Release Jobs attributes on a locked queue. • Placing the cursor on the tool tip accesses the date and time the queue was last locked. Roles and responsibilities Xerox will make every effort to assist the administrator in ensuring that the customer environment is secure. Xerox responsibilities Xerox is committed to providing a level of security which will allow the Xerox FreeFlow Print Server controller to be a good network citizen in response to current security intrusions. Additional security beyond this remains the responsibility of the customer. Xerox is constantly evaluating the security of the Xerox FreeFlow Print Server controller and the Sun Solaris operating system. Xerox is committed to providing the latest Solaris security patches provided by Sun Microsystems in each major Xerox FreeFlow Print Server release. The Xerox FreeFlow Print Server development team will also add Solaris security patches in between major release cycles. All OS security patches for applications that are added during a Xerox FreeFlow Print Server install will be included, even if the application code is not normally used by Xerox FreeFlow Print Server users. Security patches for applications that are not loaded by a Xerox FreeFlow Print Server install will not be evaluated or included. Only the version of a patch impacting security will be included. If a security patch has a newer version that is not security related, then this patch will not be 30 Security Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38

30
Security Guide
Prevent Unauthorized Queue Changes
Queue Lock
Queues can be locked and unlocked by the System
Administrator.
Properties of a locked queue cannot be changed without first
unlocking the queue.
Locked queues can only be deleted by the System
Administrator.
Locked queues can be copied by an Operator. The resulting
new queue will not be locked.
An Operator can change the Accept/Do Not Accept Jobs and
Release/Do Not Release Jobs attributes on a locked queue.
Placing the cursor on the tool tip accesses the date and time
the queue was last locked.
Roles and responsibilities
Xerox will make every effort to assist the administrator in ensuring
that the customer environment is secure.
Xerox responsibilities
Xerox is committed to providing a level of security which will allow
the Xerox FreeFlow Print Server controller to be a good network
citizen in response to current security intrusions. Additional
security beyond this remains the responsibility of the customer.
Xerox is constantly evaluating the security of the Xerox FreeFlow
Print Server controller and the Sun Solaris operating system.
Xerox is committed to providing the latest Solaris security patches
provided by Sun Microsystems in each major Xerox FreeFlow
Print Server release. The Xerox FreeFlow Print Server
development team will also add Solaris security patches in
between major release cycles. All OS security patches for
applications that are added during a Xerox FreeFlow Print Server
install will be included, even if the application code is not normally
used by Xerox FreeFlow Print Server users. Security patches for
applications that are not loaded by a Xerox FreeFlow Print Server
install will not be evaluated or included. Only the version of a patch
impacting security will be included. If a security patch has a newer
version that is not security related, then this patch will not be