Xerox FreeFlow 보안 매뉴얼 - 페이지 34

{카테고리_이름} Xerox FreeFlow에 대한 보안 매뉴얼을 온라인으로 검색하거나 PDF를 다운로드하세요. Xerox FreeFlow 38 페이지. For color 560/570 printer
Xerox FreeFlow에 대해서도 마찬가지입니다: 설치 매뉴얼 (34 페이지), 브로셔 (2 페이지), 릴리스 노트 (23 페이지), 설치 매뉴얼 (2 페이지), 릴리스 노트 (33 페이지), 중요 설치 정보 (2 페이지), 사용자 설명서 (50 페이지), 매뉴얼 (18 페이지), 빠른 연결 매뉴얼 (2 페이지), 항공사 절차 매뉴얼 (28 페이지)

Xerox FreeFlow 보안 매뉴얼

Prevent Unauthorized Queue Changes

Queue Lock

Roles and responsibilities

Xerox responsibilities

30
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.
Xerox will make every effort to assist the administrator in ensuring
that the customer environment is secure.
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
Security Guide