Workcentre 58Xxi-58XX Connectkey

Total Page:16

File Type:pdf, Size:1020Kb

Workcentre 58Xxi-58XX Connectkey ConnectKey 2.0 WorkCentre 5865i/5875i/5890i 5845/5855/5865/5875/5890 Information Assurance Disclosure Version 1.0 ©2016 Xerox Corporation. All rights reserved. Xerox and the sphere of connectivity design are trademarks of Xerox Corporation in the United States and/or other counties. Other company trademarks are also acknowledged. Document Version: 1.0 (April 2016) ConnectKey 2.0 WorkCentre 58XXi/58XX Information Assurance Disclosure 1. INTRODUCTION ..................................................................................................... 4 1.1. Purpose ........................................................................................................................................................ 4 1.2. Target Audience ......................................................................................................................................... 4 1.3. Disclaimer .................................................................................................................................................... 4 2. DEVICE DESCRIPTION .......................................................................................... 5 2.1. Security-relevant Subsystems ............................................................................................................... 6 2.1.1. Physical Partitioning .................................................................................................................................... 6 2.1.2. Security Functions allocated to Subsystems ........................................................................................... 7 2.2. Controller ..................................................................................................................................................... 7 2.2.1. Purpose ......................................................................................................................................................... 7 2.2.2. Memory Components .................................................................................................................................. 8 2.2.3. External Connections ................................................................................................................................ 10 2.2.4. USB Ports .................................................................................................................................................... 11 2.3. Fax Module ................................................................................................................................................ 12 2.3.1. Purpose ....................................................................................................................................................... 12 2.3.2. Hardware ..................................................................................................................................................... 12 2.4. Scanner ...................................................................................................................................................... 13 2.4.1. Purpose ....................................................................................................................................................... 13 2.4.2. Hardware ..................................................................................................................................................... 13 2.5. Graphical User Interface (GUI) ............................................................................................................. 13 2.5.1. Purpose ....................................................................................................................................................... 13 2.6. Marking Engine (Image Output Terminal or IOT) ............................................................................. 13 2.6.1. Purpose ....................................................................................................................................................... 13 2.6.2. Hardware ..................................................................................................................................................... 13 2.7. System Software Structure ................................................................................................................... 14 2.7.1. Open-source components ........................................................................................................................ 14 2.7.2. Operating System Layer in the Controller .............................................................................................. 15 2.7.3. Network Protocols ...................................................................................................................................... 16 2.8. Logical Access ......................................................................................................................................... 17 2.8.1. Network Security ........................................................................................................................................ 17 2.8.2. Ports ............................................................................................................................................................. 18 3. SYSTEM ACCESS ................................................................................................ 25 3.1. Authentication Model .............................................................................................................................. 25 3.2. Login and Authentication Methods ..................................................................................................... 27 3.2.1. System Administrator Login [All product configurations] ...................................................................... 27 3.2.2. User authentication .................................................................................................................................... 27 3.3. System Accounts ..................................................................................................................................... 32 Ver. 1.0, April 2016 Page 2 of 62 ConnectKey 2.0 WorkCentre 58XXi/58XX Information Assurance Disclosure 3.3.1. Printing ......................................................................................................................................................... 32 3.3.2. Network Scanning ...................................................................................................................................... 32 4. SECURITY ASPECTS OF SELECTED FEATURES ............................................ 34 4.1. McAfee Enhanced Security / Integrity Control ................................................................................. 34 4.1.1 Enhanced Security ..................................................................................................................................... 34 4.1.2 Integrity Control (Optional Feature) ......................................................................................................... 34 4.1.3 ePolicy Orchestrator .................................................................................................................................. 35 4.2. Audit Log .................................................................................................................................................... 36 4.2.1 Device Audit Log ........................................................................................................................................... 36 4.2.2 Device Protocol Log ....................................................................................................................................... 36 4.2.3 Audit Log file format ...................................................................................................................................... 36 4.3. Xerox Standard Accounting .................................................................................................................. 47 4.4. User Permissions Role Based Access Control (RBAC) ................................................................ 49 4.5. SMart eSolutions ...................................................................................................................................... 50 4.6. Encrypted Partitions ............................................................................................................................... 50 4.7. Image Overwrite ....................................................................................................................................... 51 4.7.1. Algorithm ..................................................................................................................................................... 51 4.7.2. User Behavior ............................................................................................................................................. 51 4.7.3. Overwrite Timing ........................................................................................................................................ 52 4.7.4. Overwrite Completion Reporting .............................................................................................................. 52 4.8. FIPS ............................................................................................................................................................
Recommended publications
  • Activid® Activclient®
    ActivID® ActivClient® Advanced security client protects workstations and networks with smart cards and smart USB keys HID Global’s ActivID® ActivClient® ensures strong authentication of employees, contractors and suppliers when they access enterprise resources, helping IT managers, security professionals and auditors to manage the risk of unauthorized access to workstations and networks by enabling the deployment of Zero Trust security framework. AT-A-GLANCE ACTIVCLIENT BENEFITS: • Increases security with proven As a market-leading middleware for Microsoft® Outlook®, Adobe technology that is widely adopted smart cards and smart USB keys, Acrobat® and popular web because of its user-friendly, familiar, ATM-like authentication experience ActivID ActivClient consolidates browsers), smart cards, smart card identity credentials (private keys readers and smart USB keys • Optimizes productivity with a single, versatile strong authentication for public key infrastructure [PKI] • Compatibility with major certificate tool for both Windows Login and certificates and symmetric keys for authorities and encryption utilities Remote Access (e.g., PIN-protected one-time password [OTP] generation) PKI certificates or OTPs for VPN) • Simple automated deployment, on a single, secure, portable updates and diagnostics • Improves compliance with device. This capability, combined government and industry with support for a wide range of • An open, standards-based regulations desktop and network applications, architecture, which is easily • Reduces costs with easy
    [Show full text]
  • CAC Broch:Layout 1 10/5/09 10:55 AM Page 1
    CAC Broch:Layout 1 10/5/09 10:55 AM Page 1 Introducing a bizhub Solution for: Common Access Card (CAC) and Personal Identification Verification (PIV) Card Authentication CAC Broch:Layout 1 10/5/09 10:55 AM Page 2 WHO’S USING YOUR MFPS? WHICH DOCUMENTS ARE THEY SCANNING – AND WHERE ARE THEY SENDING YOUR MOST SENSITIVE INFORMATION? TO ANSWER THESE CRITICALLY IMPORTANT QUESTIONS, KONICA MINOLTA HAS TEAMED WITH ACTIVIDENTITY™ CORPORATION IN CREATING THE BIZHUB CAC (COMMON ACCESS CARD) & PIV (PERSONAL IDENTIFICATION VERIFICATION) CARD SOLUTION: A COMPREHENSIVE AUTHENTICATION SYSTEM FOR THE DEPARTMENT OF DEFENSE (DOD) AND OTHER GOVERNMENT FACILITIES UTILIZING EITHER CAC OR PIV CARD AUTHENTICATION. Who? Which? Where? With bizhub, you’ll know the answer. A smart solution for digital ID. Increase security, speed workflow. ActivIdentity and Konica Minolta. CAC and PIV cards represent the latest advance The Konica Minolta bizhub CAC & PIV Solution is This partnership solution fulfills the technically in “smart card” identification. Used by the United a comprehensive application layer developed to aggressive security requirements of the States Department of Defense as a standard ID for reside within one or more bizhub MFP devices. government – and ensures compliance with military, government and civilian employees, CAC It meets the federal government’s requirement the latest security standards and mandates, and PIV cards are used for general identification for “two factor” authentication and facilitates including FIPS 140, FIPS 201, and ISO 15408 purposes – and can also be used to control access the use of public key information (PKI) (Common Criteria) Security Certification at to computers, networks, and facilities.
    [Show full text]
  • Secure Personal Identification Systems
    Secure Personal Identification Systems: Policy, Process and Technology Choices for a Privacy-Sensitive Solution A Smart Card Alliance White Paper January 2002 Smart Card Alliance 116 John Street, Suite 814 New York, NY 10038 www.smartcardalliance.org Telephone: 212-571-0100 Overview Recent events have heightened interest in implementing more secure personal identification (ID) systems to improve confidence in verifying the identity of individuals seeking access to physical or virtual locations. A secure personal ID system must be designed to address government and business policy issues and individual privacy concerns. The ID system must be secure, provide fast and effective verification of an individual’s identity, and protect the privacy of the individual’s identity information. Smart card technology is the best platform for a secure personal ID system. A smart card based system delivers a proven, cost-effective solution that meets government and business requirements for secure and accurate identity verifica- tion, while also meeting the individual’s need for information privacy. Coupled with a secure, privacy-sensitive information technology (IT) architecture and policy framework, a smart card based secure personal ID system can provide accurate personal identification, protect an individual’s personal information, and best address the policy and legal requirements that are currently being debated. This paper describes policy, process and technology issues that need to be considered in implementing a privacy-sensitive secure personal ID system. The different ID technologies that are available are compared, and the role that smart cards can play in implementing trusted personal credentials is presented. Smart Card Alliance © 2002 1 Secure Personal ID Applications Individuals are required currently to confirm their identity for many purposes – from verifying identity and eligibility within a healthcare system, to accessing a secure network, to proving identity for travel.
    [Show full text]
  • Smart Cards: Dumb & Dangerous Ways to Use Them
    Smart Cards: Dumb & Dangerous Ways to Use Them Contactless smart cards are fast becoming the technology of choice for access control applications. Security, convenience and interoperability are the three major reasons for this growth. However, in the move toward interoperability, reader manufacturers are offering readers that bypass all of the cards security mechanisms and instead read only the Smart Card? Serial Number (CSN). Reading only the CSN on a contactless smart card for access control security actually provides a false sense of security analogous to installing a high security door without any locking mechanism. Understanding this misuse of the CSN is critical for users of the technology to ensure that access control security is maximized. If implemented and deployed properly, contactless smart cards represent one of the most secure identification technologies available today. By Michael L. Davis Michael L. Davis is the Director of Technology in HIDs Intellectual Property Department (www.hidcorp.com). Why Use Contactless Smart Cards? Contactless smart cards incorporate advanced state-of-the-art security mechanisms. Before a reader can begin a dialogue with a card, it uses "mutual authentication" to ensure that both the reader and card can trust each other. Only after this process occurs is the reader allowed to access the data stored inside the card. Usually this data is protected by cryptographic algorithms and secret keys so that if the data were somehow extracted, or even "spied" on, it would be very difficult to decipher and utilize. As with 125 kHz Prox technology, contactless smart cards are convenient for users who merely present their cards near a reader.
    [Show full text]
  • Using Smart Cards for Secure Physical Access
    Using Smart Cards for Secure Physical Access A Smart Card Alliance Report Publication Date: July 2003 Publication Number: ID-03003 Smart Card Alliance 191 Clarksville Rd. Princeton Junction, NJ 08550 www.smartcardalliance.org Telephone: 1-800-556-6828 Smart Card Alliance © 2003 1 About the Smart Card Alliance The Smart Card Alliance is the leading not-for-profit, multi-industry association of member firms working to accelerate the widespread acceptance of multiple applications for smart card technology. The Alliance membership includes leading companies in banking, financial services, computer, telecommunications, technology, health care, retail and entertainment industries, as well as a number of government agencies. Through specific projects such as education programs, market research, advocacy, industry relations and open forums, the Alliance keeps its members connected to industry leaders and innovative thought. The Alliance is the single industry voice for smart cards, leading industry discussion on the impact and value of smart cards in the U.S. For more information, visit www.smartcardalliance.org. Copyright © 2003 Smart Card Alliance, Inc. All rights reserved. Reproduction or distribution of this publication in any form is forbidden without prior permission from the Smart Card Alliance. The Smart Card Alliance has used best efforts to ensure, but cannot guarantee, that the information described in this report is accurate as of the publication date. The Smart Card Alliance disclaims all warranties as to the accuracy, completeness or adequacy of information in this report. Smart Card Alliance Members: Members can access all Smart Card Alliance reports at no charge. Please consult the member login section of the Smart Card Alliance web site for information on member reproduction and distribution rights.
    [Show full text]
  • VIRAL ATTACKS on the Dod COMMON ACCESS CARD (CAC) Partha Dasgupta, Karmvir Chatha, and Sandeep K
    1 VIRAL ATTACKS ON THE DoD COMMON ACCESS CARD (CAC) Partha Dasgupta, Karmvir Chatha, and Sandeep K. S. Gupta Department of Computer Sc. & Eng. Arizona State University, Tempe AZ {partha, karam.chatha, sandeep.gupta}@asu.edu ABSTRACT theft. Shared secret based multi-factor authentication schemes are considered to be better, The DoD CAC (Common Access Card) is a PKI- but they lack the features of data-integrity and non- enabled smartcard that provides the following repudiation (actions are not secured by signatures functions: Authentication, Data Integrity, and hashes). Confidentiality and Non-repudiation. Since the private key of the client certificates are stored in It is also well known that system utilizing public the card, and this key cannot be extracted from key systems and certificates are well suited for all the card, it provides a high degree of security the above functions, provided there is a secure even when the card is used on a untrusted method of ensuring the private key remains workstation (or point of sale). private. The DoD Common Access Card (CAC) is a particular implementation of a Public Key This paper shows that using a DoD CAC on a Infrastructure (PKI) based solution that provides untrusted workstation can allow a variety of all the above functionality [Rig03, NISTPKI05, attacks to be performed by malicious software. LiMi03, Th84, RFC2704, NIHPKI97]. These attacks range from simple PIN phishing, to more serious attacks such as signatures on As an important component of its Defense-in- unauthorized transactions, authentication of Depth strategy, DoD is moving away from users without consent, unauthorized secure vulnerability-prone user name password based access to SSL enabled web servers as well as access control to a hardware token, certificate remote usage of the DoD CAC by attackers.
    [Show full text]
  • Oberthur ID-One Cosmo 128 V5.5 for Dod Common Access Card (CAC)
    Oberthur ID-One Cosmo 128 v5.5 for DoD Common Access Card (CAC) FIPS 140-2 Level 2 Security Policy Public Version Version 3 June 5, 2015 Oberthur Technologies of America Corp. 4250 Pleasant Valley Road Chantilly, VA 20151-1221 USA +1 (703) 263-0100 © 2015 Oberthur Technologies of America Corp. This document may be reproduced only in its original entirety without revision. Oberthur ID-One Cosmo128 v5.5 for DoD CAC Smart Card Cryptographic Module FIPS 140-2 Level 2 Security Policy Document Version Information Table 1 lists the version history of this Security Policy. Version - Date Description V 1 June 5, 2009 Official Release V 2 July 19, 2010 Firmware number update V 3-June 5, 2015 Firmware number update June 5, 2015 Version 2 Page 2 of 55 © 2015 Oberthur Technologies of America Corp. This document may be reproduced only in its original entirety without revision. Oberthur ID-One Cosmo128 v5.5 for DoD CAC Smart Card Cryptographic Module FIPS 140-2 Level 2 Security Policy Table of Contents 1 INTRODUCTION ................................................................................................................................................. 6 2 MODULE OVERVIEW ........................................................................................................................................ 6 2.1 ID-ONE COSMO 128 V5.5 ............................................................................................................................... 6 2.1.1 Common Criteria Protection Mechanisms ...........................................................................................
    [Show full text]
  • CAC) to Protect Sensitive Defense Data
    Alternative Uses of Common Access Cards (CAC) to Protect Sensitive Defense Data TECHNICAL WHITEPAPER TABLE OF CONTENTS Introduction 1 Common Access Card: Background 1 Anatomy of a CAC Smart Card 2 CAC – A Secure Foundation 2 PKI Primer 4 Expanding The Use and Benefits of CAC Smart Cards 6 Data Protection 9 Conclusion 10 INTRODUCTION The Department of Defense (DoD) selected smart card technology as the best means to satisfy the various requirements for identity management years ago. The unique implementation of this smart technology for defense is known as the Common Access Card or CAC. The CAC, a “smart” card about the size of a credit card, is the standard identification for active-duty military personnel, Selected Reserve, DoD civilian employees, and eligible contractor personnel.1 Since its inception, the DoD has issued more than 24 million smart card-based secure credentials2 with 3.5 million employees using CACs to electronically sign e-mails, submit time and attendance information securely, gain physical access to controlled sites, and most significantly, log onto to the DoD network. In 2011, the DoD issued more than 10,000 cards a day to its employees.3 The architecture is proven for its express purpose of authenticating personnel before granting access to facilities and systems. Several procedures surround issuance of the credential, requiring appropriate background checks before a CAC is issued, and periodic status review to confirm continued eligibility. This paper explores the additional and alternative data security uses for smart media containing electronic credentials and highlights practical use in daily operations to further enhance overall ROI.
    [Show full text]
  • Modernizing the Common Access Card - Streamlining Identity and Improving Operational Interoperability
    OFFICE OF THE SECRETARY OF DEFENSE 1000 DEFENSE PENTAGON WASHINGTON, D.C. 20301-1000 MEMORANDUM FOR: SEE DISTRIBUTION SUBJECT: Modernizing the Common Access Card - Streamlining Identity and Improving Operational Interoperability Homeland Security Presidential Directive 12 (HSPD-12) requires Federal departments and agencies to use strong authentication credentials to access their networks and information systems. The Common Access Card (CAC) is the DoD's primary credential for fulfillingthese requirements on the Non-Secure Internet Protocol Router Network (NIPRNet). Without adjustments to DoD's CAC implementation, the Department will continue to diverge fromthe Public Key Infrastructure (PKI) standards utilized by the rest of the Federal Government, mission partners, and industrial suppliers. This memorandum makes the DoD's Personal Identity Verification (PIV)-Authentication (Auth) certificate the standard for access to DoD information technology assets on the NIPRNet across the Department. The United States warfighter's ability to interoperate with various mission partners is hampered by a lack of common identity standards. This memorandum directs the alignment of DoD's use of the CAC with the Federal PIV-Auth certificateto: • Standardize implementations and reduce inefficiencies around secure information exchange with DoD, Federal. state, local, territorial, and tribal mission partners. • Improve cybersecurity posture and simplify configurationand change management of Department network resource authentication, as well as the implementation and reporting of risk management controls, by using a common Department-wide PKI principal authenticator. • Reduce costs associated with maintaining DoD-peculiar legacy authentication mechanisms. such as legacy CAC interfaces and certain smart card middleware. • Allow the Department to use commercial products designed to read federalHSPD-12 PIV compliant PKI credentials.
    [Show full text]
  • GSA Smart Card Handbook
    GOVERNMENT SMART CARD HANDBOOK GOVERNMENT SMART CARD HANDBOOK PREFACE This guidance Handbook is the result of Government experience gained over the past several years with smart card programs that include many smart card implementations, pilots, and projects conducted throughout the Federal government. The Handbook includes very significant input from industry and academic resources. The purpose of this Handbook is to share lessons learned and to provide guidance to Federal agencies contemplating the development and deployment of smart card or integrated circuit card-based identity and credentialing systems. At this writing there is a project under way to make this Handbook as web friendly as possible. Any suggestions on how to make this Handbook more useful and convenient would be appreciated. Please e-mail comments to Jim Hunt ([email protected]) and Bill Holcombe ([email protected]). Bill Holcombe, Office of Governmentwide Policy General Services Administration February 2004 i GOVERNMENT SMART CARD HANDBOOK ACKNOWLEDGEMENTS This ‘Government Smart Card Handbook’ has been developed under the joint sponsorship of the General Services Administration Office of Governmentwide Policy and the Smart Card Interoperability Advisory Board (IAB). It would not have been possible to produce this Handbook without the contributions of knowledgeable people from government, industry, and academia. We acknowledge their contributions and give special thanks to the following direct contributors: Tim Baldridge – National Aeronautics and Space Administration
    [Show full text]
  • The Globalplatform Value Proposition for Identity Management
    The GlobalPlatform Value Proposition for Identity Management White Paper November 2007 [email protected] www.globalplatform.org © 2007 GlobalPlatform Inc. Contents About GlobalPlatform ii Publication Acknowledgements ii Executive Summary iii Section 1: The Concept of Identity Management 1 Introducing Smart Cards to Identity Management 2 Section 2: Case Study - U.S. Department of Defense (DoD) Common Access Card 4 The U.S. DoD Identity Management Concept 4 The Common Access Card (CAC) 4 Evolving DoD Systems to Support CAC 5 Section 3: What GlobalPlatform Offers the ID Card 8 Personalizing Chips and Managing Applications – Vendor (In)Dependence 8 A Card With More Than One Application 9 ID Card Security Considerations 11 The Smart ID Card Life Cycle 11 Card Issuance Processes 13 Section 4: The GlobalPlatform Proposition 14 Identity Management Roles 15 Smart Card Management Roles 16 Section 5: GlobalPlatform Specifications - Future-Proofing Government Identity Programs 18 Appendices: 20 Appendix I - Acronyms 20 Appendix II – List of GlobalPlatform Specifications 21 i © 2007 GlobalPlatform Inc. About GlobalPlatform GlobalPlatform is a member driven organization with worldwide cross-industry representation. GlobalPlatform is the leading, international association, focused on establishing and maintaining interoperable specifications for single and multiple application smart cards, acceptance devices and systems infrastructure that deliver benefits to issuers, service providers and technology suppliers. These specifications are known
    [Show full text]