Kanguru Common Criteria Evaluated v1.21 Uživatelský manuál

Secure. Anytime. Anywhere.TMCopyright 2014, All Rights ReservedEvaluated ProductUser GuideVersion 1.21

102.4 Software RequirementsThe device client software MUST be one of the following applications. This entire document applies to all of the applicati

112.6 Requirements for administratorsWhen using the devices in an Enterprise configuration, there MUST be one or more competent individuals who are a

122.8 Requirements for connectivityWhen using KRMC, you MUST ensure that all network connections used for the communication with the KRMC are under t

133. DocumentationThe delivery of the Guidance Documents will be secured through a secure site (Kanguru.com). The document will be available as a dow

14ECG delivery to customersCustomers can download latest evaluated guide from Kanguru support site at:https://kanguru.zendesk.com/entries/88351486-Eva

154. Software InstallationThe evaluation covers a fresh installation of the management software and the initial configuration of the devices listed i

16Software Installation4.2 UKLAUKLA can be installed anywhere on your Windows system. You MUST place it in a directory that is writable by the user I

174.3 KRMCPlease refer to “KRMC - Enterprise Edition - Install Guide v5.pdf” for instructions on installing KRMC and the prerequisite software (MS SQ

184.4 KDMThe Defender 2000 and Elite200 flash devices come pre-loaded with firmware and KDM client software. For all drives, the delivery to the cust

194.4.2 Verifying the KDM Client Edition Users can open the version.ini file in CD-ROM partition to verify whether their device is running a Cloud edi

2Notices and InformationPlease be aware of the following points before using your Kanguru productCopyright © 2014 Kanguru Solutions. All rights reserv

20Verifying the files loaded to your Defender deviceThe user MUST check the authenticity of the client software on their Defender drive to ensure that

214.4.3 Updating Your Defender DeviceFor the purposes of this section, the word “device” is taken to refer to either the Kanguru Defender 2000 or Kan

224.4.3.1 Updating Cloud/Standard Edition Devices To prevent you from accidentally updating your device to a non-Common Criteria certified client ver

234.4.3.2 Updating KRMC Enterprise Edition Devices Enterprise edition Defender devices are managed by the Kanguru Remote Management Console (KRMC). U

24Software Installation4.4.3.3 Updating No-Comms Edition Devices To prevent you from accidentally updating your device to a non-Common Criteria certi

255. Common Criteria Certified VersionsDefender Elite200’s with the following specifications have been certified by Common Criteria: • Client softwa

266. Device Self TestAll devices feature an LED that indicates the state of the device as follows:• After the device has been powered on via USB the

277. Standalone Device SetupA standalone device is not managed by UKLA or KRMC. All setup responsibility solely lies with the user. The use of the de

289. Password Selection RecommendationThe following password policy MUST be enabled for all parts of the TOE where possible (not all parts or prerequ

2911. Verifying Your Files Using SHA256 ChecksumTo verify the integrity of the KDM updater that you downloaded, please use the HashMyFiles SHA256 Che

3End User License AgreementEnd User License AgreementThis legal document is an agreement between you, the end user (“Licensee”), and Kanguru Solutions

3011.1 SHA256 Checksum ValuesIf the checksum generated by the HashMyFile tool matches the checksum published below, then your files are genuine. Defe

31Defender 2000 Cloud Edition Client Application Files (KDM2000 v 1.2.1.8 -2)File name SHA256 Checksum valueKDM2000 cfe4236c88133c863693555a7f77eca09a

32Defender 2000 No-Comms Edition Client Application Files (KDM2000 v 1.2.1.8 -6)File name SHA256 Checksum valueKDM2000 8f313a05556d7b80fd84d66ff41e741

33Defender Elite200 Enterprise Edition Client Application Files (KDME200 v 2.0.0.0 -3)File name SHA256 Checksum valueKDMElite200 c03eed99ad8a2e7e86e0f

3412. Changelogv1.3 updated 5/30/2013• Updated CC certified client version of KDME to 2.7.1.9• Updated CC certified client version of KDM1000 to 1.

35v1.11 updated 7/17/2014• Consolidate all hash checking to a single chapter• Change the Hash tool used to Hashmyfiles.exe• Add SHA hashing for KRM

Secure. Anytime. Anywhere.TMLegal terms and conditions available at www.kanguru.com. Please review and agree before use. Thank you.Kanguru Solutions 1

4End User License AgreementLimitations of DamagesIn no event shall Licensor, or anyone else who has been involved in the creation, distribution, or de

5Table of ContentsTable of Contents 1. Introduction ... 61.1 Pu

61. Introduction1.1 Purpose of this documentThe Kanguru Defender Family of encrypted storage devices is designed to provide secure and reliable port

71.2 How to use this documentThe key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “O

82. Requirements and Assumptions2.1 What is a CC compliant system?A system can be considered to be “CC compliant” if it matches an evaluated and cer

92.2 Identifying Your Defender DeviceThere are currently two Defender models that are certified for Common Criteria: 2000 and Elite200. You can visua