LANDesk Management Suite 8, V8

Transcription

LANDesk Management Suite 8, V8.6.1Security TargetVersion 1.0October 24, 2006Prepared forLANDesk Software, LtdPrepared by:CygnaComSuite 5200 7925 Jones Branch Drive McLean, VA 22102-3305 703 848-0883 Fax 703 848-0960

LANDesk Management Suite 8 V8.6.1 Security TargetVersion 1.0TABLE OF CONTENTSSECTION12PAGESecurity Target Introduction.51.1Security Target Identification. 51.2Security Target Overview . 51.3Common Criteria Conformance. 51.4Document Conventions. 51.5Document Organization . 6TOE Description .72.1Product Type . 72.1.12.1.22.2LANDesk Management Suite Components.8List of Management Suite tools .8TOE Physical Boundary and Scope of the Evaluation . 92.2.1 Physical Boundary .92.2.1.1LANDesk Core Server .92.2.1.2LANDesk Client .102.2.2 Evaluated Configuration .10342.3TOE Logical Boundary . 112.4IT Environment. 12TOE Security Environment.133.1Assumptions. 133.2Threats . 133.3Organizational Security Policies. 14Security Objectives .154.1Security Objectives for the TOE. 154.2Security Objectives for the Environment . 154.2.14.2.25Security Objectives for the IT Environment .15Non-IT Security Objectives .15IT Security Requirements.175.1TOE Security Functional Requirements. .10LANDesk FAU LRG.1 (exp) LANDesk report generation .17FAU LRR.1 (exp) LANDesk reports review .17FAU LRR.2 (exp) LANDesk restricted reports review .18FAU LRR.3 (exp) LANDesk selectable reports review .18FIA ATD.1 User attribute definition .19FIA LAU.2 (exp) LANDesk user authentication before any action .19FIA UID.2 User identification before any action.19FMT MTD.1a Management of TSF data .19FMT MTD.1b Management of TSF data.19FMT MTD.1c Management of TSF data .19Page 210/24/2006

LANDesk Management Suite 8 V8.6.1 Security TargetVersion 1.05.1.11 FMT MTD.1d Management of TSF data.195.1.12 FMT SMR.1 Security roles.195.1.13 FMT SMF.1 Specification of Management Functions .195.2TOE Security Assurance Requirements . 205.3Security requirements for the IT Environment . 205.3.15.3.25.3.35.3.45.3.55.46FPT STM.1 Reliable time stamps.20FIA OAU.2 (exp) OS user authentication before any action .21FPT SEP ENV.1 (exp) TSF domain separation .21FTP ITC.1 Inter-TSF trusted channel .21FPT ITT.1 Basic internal TSF data transfer protection.21Strength of Function . 21TOE Summary Specification.226.16.1.16.1.26.1.36.1.46.2IT Security Functions . 22LANDesk Report Generation Function .22Identification and authentication.25Security management.25SOF Claims.26Assurance Measures . 267PP Claims .48.2.58.38.3.18.3.28.49Security Objectives Rationale . 29Threats .29Assumptions .30Security Requirements Rationale . 31Functional Requirements .31Security Functional Requirements Dependencies.34Explicitly Stated Requirements.34Strength of Function .35EAL Justification .35TOE Summary Specification Rationale . 35IT Security Functions.35Assurance Measures .37PP Claims Rationale . 39Appendix .40LANDesk Page 310/24/2006

LANDesk Management Suite 8 V8.6.1 Security TargetVersion 1.0Table of Tables and FiguresTable or FigurePageFigure 2-1: LANDesk Management Suite console tasks.7Figure 2-2 TOE Boundary.9Figure 2-3 TOE evaluated configuration .11Table 3-1 Assumptions.13Table 3-2 Threats.13Table 4-1 Security Objectives for TOE.15Table 4-2 Security Objectives for IT Environment .15Table 4-3 Security Objectives for Non-IT Environment .15Table 5-1 Functional Components .17Table 5-2 Criteria for sorting the LANDesk security and patch manager reports .18Table 5-3 EAL2 Assurance Components .20Table 5-4 Functional Components for the IT environment.20Table 6-1 Security Functional Requirements mapped to Security Functions.22Table 6-2 Assurance Measures.26Table 8-1 Mapping of Security Environment to Security Objectives .29Table 8-2 Mapping of Security Functional Requirements to Security Objectives .31Table 8-3 Functional Requirements Dependencies Satisfied .34Table 8-4 Mapping of Functional Requirements to TOE Summary Specification.35Table 8-5 Assurance Measures Rationale .37Table 9-1 Acronyms.40Table 9-2 References .40LANDesk Page 410/24/2006

LANDesk Management Suite 8 V8.6.1 Security TargetVersion 1.01 Security Target Introduction1.1 Security Target IdentificationTOE Identification: LANDesk Management Suite 8, Version 8.6.1The following updates must be applied to the client systems: LD-861-Mimi-Rollup-February-2006 (contains 15 fixes), and LD-861-SP1 that update installs LANDesk Software 8.6.1 Service Pack.ST Title:LANDesk Management Suite 8, V8.6.1 Security TargetST Version:Version 1.0ST Authors:CygnaCom Solutions, Inc.ST Date:October 24, 2006Assurance Level:EAL2Strength of Function: SOF BasicRegistration: To be filled in upon registration Keywords:Identification, Authentication, Access Control, Security Management,Vulnerability Scanner, LANDesk Management Suite1.2 Security Target OverviewThis Security Target (ST) defines the Information Technology (IT) security requirements forLANDesk Management Suite 8, version 8.6.1.LANDesk Management Suite 8 (LDMS) is a remote desktop management solution which enablesnetwork administrators to view, configure, and manage the devices on a network. It includes a fullrange of remote administration tools that can manage complex, heterogeneous computingenvironments by supporting multiple OS platforms, directories, databases and hardware platforms.It provides an integrated systems and a security management solution that can be used to distributesoftware packages, monitor software usage, deploy OS images and migrate profiles, remote controldevices, and complete many other management tasks.1.3 Common Criteria ConformanceThe TOE is Part 2 extended, Part 3 conformant, and meets the requirements of EvaluationAssurance Level (EAL) 2 from the Common Criteria for Information Technology Security EvaluationVersion 2.3, (CC v2.3), August 2005.1.4 Document ConventionsThe notation, formatting, and conventions used in this security target (ST) are consistent withversion 2.3 of the Common Criteria for Information Technology Security Evaluation. All of thecomponents are taken directly from Part 2 of the CC except the ones noted with “(exp)” in thecomponent name. Font style and clarifying information conventions were developed to aid thereader.The CC permits four functional component operations: assignment, iteration, refinement, andselection to be performed on functional requirements. These operations are defined in CC Part 1and Part 2, and this ST identifies them as the following:LANDesk Page 510/24/2006

LANDesk Management Suite 8 V8.6.1 Security TargetVersion 1.0 Assignment: allows the specification of an identified parameter. In this ST the assignmentsare specified in italicized text (e.g. assignment). Iteration:allows a component to be used more than once with varying operations.Iterations are identified with a lower case letter following the typical CC requirement namingfor each new iteration (e.g. FMT MOF.1a). Refinement: allows the addition of details or the narrowing of requirements. In this ST,refinements are specified in italicized, bold, underlined text for additional text (e.g.additional text), and strikethrough for deletion text (e.g. deletion text). Selection:allows the specification of one or more elements from a list. Selections arespecified in bold text in this ST (e.g. selection).Explicitly Stated Requirements will be noted with a “(exp)” added to the component name in this ST.1.5 Document OrganizationThe main sections of an ST are the ST Introduction, Target of Evaluation (TOE) Description, TOESecurity Environment, Security Objectives, IT Security Requirements, TOE Summary Specification,and Rationale.Section 2, TOE Description, describes the product type and the scope and boundaries of the TOE.Section 3, TOE Security Environment, identifies assumptions about the TOE’s intended usage andenvironment and threats relevant to the secure TOE operation.Section 4, Security Objectives, defines the security objectives for the TOE and its environment.Section 5, IT Security Requirements, specifies the TOE Security Functional Requirements (SFR),Security Requirements for the IT Environment, and the Security Assurance Requirements.Section 6, TOE Summary Specification, describes the IT Security Functions and AssuranceMeasures.Section 7, Protection Profile (PP) Claims, is not applicable, as this product does not claimconformance to any PP.Section 8, Rationale, presents evidence that the ST is a complete and cohesive set of requirementsand that a conformant TOE would provide an effective set of IT security countermeasures within thesecurity environment. The Rationale has three main parts: Security Objectives Rationale, SecurityRequirements Rationale, and TOE Summary Specification Rationale.Section 9 provides acronyms, definitions and references.LANDesk Page 610/24/2006

LANDesk Management Suite 8 V8.6.1 Security TargetVersion 1.02 TOE DescriptionLANDesk Management Suite enables administrators to automate desktop management tasks andproactively control, and update desktops, servers and mobile devices. It consists of tools that canbe used to view, configure, and manage the devices in a complex, heterogeneous computingenvironment (Windows NT, Windows 2000/2003, NetWare, Macintosh, Linux, and UNIX networks).All of the following tasks can be done through the LANDesk Management Suite main console: Maintains security and keeps up with patches and updates Efficiently installs and maintains software on the desktop Provides Asset Management by inventorying devices on the network Migrates users and their profiles to new operating systems.Figure 2-1: LANDesk Management Suite console tasks2.1 Product TypeLANDesk Management Suite 8 (LDMS) is a remote desktop management solution which enablesnetwork administrators to view, configure, and manage the devices on a network. It includes a fullrange of remote administration tools that can manage complex, heterogeneous computingenvironments by supporting multiple OS platforms, directories, databases and hardware platforms.It provides an integrated systems and a security management solution that can be used to distributesoftware packages, monitor software usage, deploy OS images and migrate profile

LANDesk Management Suite 8, V8.6.1 Security Target Version 1.0 October 24, 2006 Prepared for LANDesk Software, Ltd Prepared by: CygnaCom Suite 5200 7925 Jones Branch