Kanguru Common Criteria Evaluated v1.21 - Manual (Page 10)

10
2.4 Software Requirements
The device client software MUST be one of the following applications. This entire document applies
to all of the applications unless explicitly noted. The appropriate device specific Kanguru Defender
Manager has to be used.
• Kanguru Defender Manager Elite200:
○ KDME200 v 2.0.0.0 - 2
○ KDME200 v 2.0.0.0 - 3
○ KDME200 v 2.0.0.0 - 6
• Kanguru Defender Manager 2000:
○ KDM2000 v 1.2.1.8 - 2
○ KDM2000 v 1.2.1.8 - 3
○ KDM2000 v 1.2.1.8 - 6
• Universal Kanguru Local Administrator: Version Release 3.2.0.3
• Kanguru Remote Management Console: Version 5.0.2.6
Important! Your Defender security device MUST be running the Kanguru Defender Manager software
version listed above in order to be considered CC compliant. It is the user’s responsibility to ensure that
their hardware is in compliance. For instructions on determining what version of Kanguru Defender
Manager your device is running, please refer to section 4.4 KDM on page 18.
2.5 Requirements for the system’s environment
The security target covers devices that use Linux, MacOS and Windows hosts for access via the
appropriate Kanguru Defender manager (KDM).
It is assumed that the value of the stored assets merits moderately intensive penetration or masquerading
attacks. It is also assumed that physical controls in place would alert the system authorities to the physical
presence of attackers within the controlled space.
You MUST use the devices only on trustworthy hosts that can be relied on to not have any malware
installed.
The Kanguru Remote Management Console MUST be installed on a Windows 2008 System with MS
SQL Server 2005, MS SQL Server 2008 or MS SQL Express and IIS already installed and the latest
security patches applied.
The Kanguru Remote Management Console MUST be installed on a physically protected system that is
only used for KRMC.
The Kanguru Central Server MUST NOT be used in the evaluated configuration.
Requirements and Assumptions