Certification Report
EAL 3 Evaluation of Thales Communications S. A.
Internal Communications Management System
(ICMS)
Version 3.7.1.0
Issued by:
Communications Security Establishment
Certification Body
Canadian Common Criteria Evaluation and Certification Scheme
© 2004 Government of Canada, Communications Security Establishment
Document number: 383-4-25-CR
Version: 1.0
Date: 19 August 2004
Pagination: i to iv, 1 to 10
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
DISCLAIMER
The Information Technology (IT) product identified in this certification report, and its
associated certificate, have been evaluated at an approved evaluation facility – established
under the Canadian Common Criteria Evaluation and Certification Scheme (CCS) – using
the Common Methodology for Information Technology Security Evaluation, Version 1.0, for
conformance to the Common Criteria for IT Security Evaluation, Version 2.1. This
certification report and its associated certificate, apply only to the identified version and
release of the product in its evaluated configuration. The evaluation has been conducted in
accordance with the provisions of the CCS, and the conclusions of the evaluation facility in
the evaluation report are consistent with the evidence adduced. This report, and its
associated certificate, are not an endorsement of the IT product by the Communications
Security Establishment (CSE), or any other organization that recognizes or gives effect to
this report, and its associated certificate, and no warranty for the IT product by the CSE, or
any other organization that recognizes or gives effect to this report, and its associated
certificate, is either expressed or implied.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page i of iv -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
FOREWORD
The Canadian Common Criteria Evaluation and Certification Scheme (CCS) provides a
third-party evaluation service for determining the trustworthiness of Information Technology
(IT) security products. Evaluations are performed by a commercial Common Criteria
Evaluation Facility (CCEF) under the oversight of the CCS Certification Body, which is
managed by the Communications Security Establishment.
A CCEF is a commercial facility that has been approved by the CCS Certification Body to
perform Common Criteria evaluations; a significant requirement for such approval is
accreditation to the requirements of ISO Standard 17025, General requirements for the
accreditation of calibration and testing laboratories. Accreditation is performed under the
Program for the Accreditation of Laboratories Canada (PALCAN), administered by the
Standards Council of Canada.
The CCEF that carried out this evaluation is DOMUS IT Security Laboratories, located in
Ottawa, Ontario.
By awarding a Common Criteria certificate, the CCS Certification Body asserts that the
product complies with the security requirements specified in the associated security target. A
security target is a requirements specification document that defines the scope of the
evaluation activities. The consumer of certified IT products should review the security
target, in addition to this certification report, in order to gain an understanding of any
assumptions made during the evaluation, the IT product's intended environment, its security
requirements, and the level of confidence (i.e., the evaluation assurance level) that the
product satisfies the security requirements.
This certification report is associated with the certificate of product evaluation dated 19
August 2004, and the security target identified in Section 4 of this report.
The certification report, certificate of product evaluation and security target are posted on the
CCS Certified Products list at:
http://www.cse-cst.gc.ca/en/services/common_criteria/trusted_products.html
This certification report makes reference to the following trademarked names: Solaris and
SOLSTICE which are trademarks of Sun Microsystems Inc.; Sybase, SQL Server, Open
Server, Open Client and DB-Library which are trademarks of Sybase Inc; and MOTIF which
is a registered trademark of The Open Group in the United States and other countries.
Reproduction of this report is authorized provided the report is reproduced in its entirety.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page ii of iv -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
TABLE OF CONTENTS
Disclaimer....................................................................................................................................... i
Foreword........................................................................................................................................ii
Executive Summary...................................................................................................................... 1
1 Identification of Target of Evaluation ................................................................................ 3
2 TOE Description ................................................................................................................... 3
3 Evaluated Security Functionality........................................................................................ 3
4 Security Target...................................................................................................................... 3
5 Common Criteria Conformance.......................................................................................... 4
6 Security Policy....................................................................................................................... 4
7 Assumptions and Clarification of Scope............................................................................. 4
7.1 SECURE USAGE ASSUMPTIONS................................................................................... 5
7.2 ENVIRONMENTAL ASSUMPTIONS ............................................................................... 5
7.3 CLARIFICATION OF SCOPE.......................................................................................... 5
8 Architectural Information ................................................................................................... 5
9 Evaluated Configuration...................................................................................................... 6
10 Documentation ...................................................................................................................... 6
11 Evaluation Analysis Activities ............................................................................................. 6
12 ITS Product Testing.............................................................................................................. 7
12.1 ASSESSING DEVELOPER’S TESTS ............................................................................... 7
12.2 INDEPENDENT FUNCTIONAL TESTING ........................................................................ 8
12.3 INDEPENDENT PENETRATION TESTING....................................................................... 8
12.4 CONDUCT OF TESTING ............................................................................................... 9
12.5 TESTING RESULTS...................................................................................................... 9
13 Results of the Evaluation...................................................................................................... 9
14 Evaluator Comments, Observations and Recommendations ........................................... 9
15 Acronyms and Abbreviations .............................................................................................. 9
___________________________________________________________________________
Version 1.0 19 August 2004
- Page iii of iv -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
16 References............................................................................................................................ 10
___________________________________________________________________________
Version 1.0 19 August 2004
- Page iv of iv -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
Executive Summary
The Internal Communications Management System Version 3.7.1.0, from Thales
Communications S.A., is the Target of Evaluation (TOE) for this Evaluation Assurance
Level (EAL) 3 evaluation.
The Internal Communications Management System (ICMS) Version 3.7.1.0, together with
the External Communications Management System (ECMS) Version 4.1, form the
Communications Control and Monitoring System (CCMS) which manages all internal and
external communications equipment on shipboard communications systems.
The ICMS is a software application that runs on a CCMS workstation. It manages the
following aspects of the communications system:
• The local area network which links together all the communications equipment (radios,
voice/data terminals, etc.);
• The radios, terminals and other equipment connected to the local area network; and
• Communications services such as telephony, intercom and radio communications.
DOMUS IT Security Laboratories is the Common Criteria Evaluation Facility that conducted
the evaluation. This evaluation was completed on 12 August 2004, and was carried out in
accordance with the rules of the Canadian Common Criteria Evaluation and Certification
Scheme (CCS).
The scope of the evaluation is defined by the security target, which identifies assumptions
made during the evaluation, the intended environment for the ICMS, the security
requirements, and the level of confidence (evaluation assurance level) at which the product is
intended to satisfy the security requirements. Consumers of the ICMS are advised to verify
that their own environment is consistent with the security target, and to give due
consideration to the comments, observations and recommendations in this certification
report.
The results documented in the evaluation technical report1
for this product provide sufficient
evidence that it meets the EAL 3 assurance requirements for the evaluated security
functionality. The evaluation was conducted using the Common Methodology for IT Security
Evaluation, Version 1.0 (with applicable final interpretations), for conformance to the
Common Criteria for IT Security Evaluation, version 2.1.
1
The evaluation technical report is a CCS document that contains information proprietary to the developer
and/or the evaluator, and is not releasable for public review.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 1 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
The Communications Security Establishment, as the CCS Certification Body, declares that
the ICMS evaluation meets all the conditions of the Arrangement on the Recognition of
Common Criteria Certificates and that the product will be listed on the CCS Certified
Products List.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 2 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
1 Identification of Target of Evaluation
The Target of Evaluation (TOE) for this Evaluation Assurance Level (EAL) 3 evaluation is
the Internal Communications Management System Version 3.7.1.0, from Thales
Communications S.A.
2 TOE Description
The Internal Communications Management System (ICMS) Version 3.7.1.0, together with
the External Communications Management System (ECMS) Version 4.1, form the
Communications Control and Monitoring System (CCMS) which manages all internal and
external communications equipment on shipboard communications systems.
The ICMS is a software application that runs on a CCMS workstation. It manages the
following aspects of the communications system:
• The local area network which links together all the communications equipment (radios,
voice/data terminals, etc.);
• The radios, terminals and other equipment connected to the local area network; and
• Communications services such as telephony, intercom and radio communications.
The ICMS security services enforce the ICMS Security Policy (identified in Chapter 6 of this
report).
3 Evaluated Security Functionality
The complete list of evaluated security functionality for the ICMS is identified in Section 5.1
of the security target (ST).
4 Security Target
The ST associated with this Certification Report (CR) is identified by the following
nomenclature:
Title: Security Target Internal Communications Management System
Version: Issue 1.4
Date: July 23, 2004
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 3 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
5 Common Criteria Conformance
The evaluation was conducted using the Common Methodology for IT Security Evaluation,
Version 1.0, for conformance to the Common Criteria for IT Security Evaluation, version 2.1
incorporating all final interpretations issued prior to 23 May 2003. The ICMS is:
a) Common Criteria Part 2 conformant, with security functional requirements based
only upon functional components in Part 2;
b) Common Criteria Part 3 conformant, with security assurance requirements based
only upon assurance components in Part 3; and
c) Common Criteria EAL 3 conformant, with all the security assurance requirements in
the EAL 3 package.
6 Security Policy
The ICMS Security Policy states the rules by which the ICMS manages communications
resources. The complete ICMS Security Policy is identified in the ST. The following
statements are representative of the ICMS Security Policy:
Identification and Authentication. Users of the ICMS are required to successfully identify
and authenticate before they are granted access to the functional aspects of the software.
Access Control. The ICMS implements and enforces a discretionary access control
environment. Within this environment, two (2) distinct sets of controls exist:
1. only authorized administrators may modify the user security attributes; and
2. each user’s access to controlled peripherals and system components within the
application is determined by the user’s assigned role. The system controls access to
several peripheral devices such as radios, terminals, telephony and intercom services
and the local area network linking these peripherals together.
Audit. The audit component of the ICMS generates audit logs upon use of the identification
and authentication mechanisms and upon modification or revocation of certain security
attributes. The audit records are protected by ensuring that only authorized users have access
to the audit records. The audit records are protected from deletion, modification and system
failures.
7 Assumptions and Clarification of Scope
Consumers of the ICMS should consider assumptions about usage and environmental
settings as requirements for the product’s installation and its operating environment. This
will help to ensure the proper and secure operation of the ICMS.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 4 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
7.1 Secure Usage Assumptions
For purposes of this evaluation, the users are assumed to be trusted and to understand the
correct usage of the system. The users must operate the ICMS following the guidance in
the ICMS Operating Instructions.
7.2 Environmental Assumptions
The following assumptions are made about the operating environment of the ICMS:
a) The components of the ICMS will be located within controlled access facilities which
will prevent unauthorised physical access;
b) Administrators are non-hostile and will not attempt to compromise the ICMS
functionality; and
c) Logical and physical protection will be provided for the communications with
peripheral devices.
For more information about the ICMS security environment, refer to Section 3 of the ST.
7.3 Clarification of Scope
The ICMS provides a level of protection that is appropriate for an assumed non-hostile and
well-managed user community. While it is designed to protect its user community against
inadvertent or casual attempts to breach system security, it is not intended for situations in
which determined attempts by hostile and well-funded attackers use sophisticated attacks to
violate system security, particularly from within the physical zone or domain of deployment.
8 Architectural Information
The ICMS is a software application that resides on a Sun Server running the Solaris™ 2.8
operating system.
The Sun Server is accessed via a keyboard, mouse and monitor that is shared with the ECMS
system and controlled by a Keyboard Video Mouse (KVM) switch. With the KVM switch set
to the Sun Server, a user is able to log in to the server as either a normal user or an
administrative user. When logged on as a normal user, the user has no access to the Solaris™
environment and an ICMS interface is automatically started. The user then has to log on to
the ICMS application. Alternatively, when logged on to the server as an administrator, the
user has access to the Solaris™ environment and must manually start the ICMS application.
The TOE is denoted in figure 2.1 of the ST as the ICMS Core and comprises the following
subsystems:
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 5 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
a) CUBAS2, that manages the identification and authentication user interface;
b) CUDHM2, that manages user access in the application;
c) CUCLI2, that provides the background identification and authentication service; and
d) CUOBJ2, that provides the background execution of application commands.
9 Evaluated Configuration
The TOE is evaluated under the same configuration as indicated in the ST, except that no
radio equipment which the TOE is designed to command was available due to transportation
constraints.
The ICMS application runs on a Sun Server and uses the following software:
• Solaris™ 2.8
• CDE X11R5 MOTIF® V1.2
• ILOGVIEWS V3.1 patch 31227
• NETSCAPE V4.04
• SOLSTICE™ V9.2 patch 108669-02
• Sybase™ SQL Server™ 11.9.2, Open Server™ V11.1.1, Open Client™ and DB-
Library™ V11.1.1
• SunHSI PCI DRIVER V3.0.
10 Documentation
The documentation for the ICMS consists of the ICMS Operating Instructions (Issue
06/2004) which is described in Section 11 below.
11 Evaluation Analysis Activities
The evaluation analysis activities involved a structured evaluation of the ICMS, including the
following areas:
Configuration management: An analysis of the ICMS development environment and
associated documentation was performed. The evaluators found that the ICMS configuration
items were clearly marked, and could be modified and controlled. The developer’s
configuration management system (SPMS+) was observed during a site visit, and it was
found to be mature and well developed. In particular, the developer uses an integrated suite
of commercial tools to perform software configuration management and problem tracking.
Secure delivery and operation: The evaluators examined the delivery documentation and
determined that it described all of the procedures required to maintain the integrity of the
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 6 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
ICMS during distribution to the consumer. The evaluators examined the installation,
generation and start-up procedures, and determined that they were complete and sufficiently
detailed to result in a secure configuration.
Design documentation: The evaluators analysed the ICMS functional specification and
high-level design; they determined that the documents were internally consistent, and
completely and accurately instantiated all interfaces and security functions. The evaluators
also independently verified that the correspondence mappings between the design documents
were correct.
Guidance documents: The evaluators examined the ICMS Operating Instructions (Issue
06/2004) document and determined that it sufficiently and unambiguously described how to
securely use and administer the product, and that it was consistent with the other documents
supplied for evaluation. The ICMS Operating Instructions document includes both the user
and administrator manuals.
Life-cycle support: The evaluators assessed the development security procedures during a
site visit and determined that the procedures detailed sufficient security measures for the
development environment to protect the confidentiality and integrity of the ICMS design and
implementation.
Vulnerability assessment: The ICMS Security Target’s claims for the strength of function
claims were validated through independent evaluator analysis. The evaluators examined the
developer's vulnerability analysis, and found that it sufficiently described each of the
potential vulnerabilities along with sound rationale as to why it was not exploitable in the
intended environment. Additionally, the evaluators conducted an independent review of
public domain vulnerability databases, and all evaluation deliverables to provide assurance
that the developer had considered all potential vulnerabilities.
All these evaluation activities resulted in PASS verdicts.
12 ITS Product Testing
Testing at EAL3 consists of the following three steps: assessing developer tests, performing
independent functional tests, and performing independent vulnerability tests.
12.1 Assessing Developer’s Tests
The evaluators verified that the developer had met their testing responsibilities by examining
their test evidence, and reviewing their test results, as documented in the Evaluation
Technical Report (ETR)2
.
2
The evaluation technical report is a CCS document that contains information proprietary to the developer
and/or the evaluator, and is not releasable for public review.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 7 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
The evaluators analyzed the developer’s test coverage analysis and test depth analysis, and
found it to be complete and accurate. The correspondence between tests identified in the
developer’s test documentation and the functional specification and high-level design was
complete.
12.2 Independent Functional Testing
During this evaluation, the evaluators developed independent functional tests by examining
the design and guidance documentation, examining the developer’s test documentation,
executing a sample of the developer’s test cases and creating test cases that augmented the
developer tests.
All testing was planned and documented to a sufficient level of detail to allow repeatability
of the testing procedures and results.
Independent functional testing focused on the ICMS Security Policy, specifically:
a) Creation of Roles by the Administrator;
b) Creation of Users by the Administrator;
c) Testing that User Interfaces and User Roles corresponded;
d) Testing of Role and User attributes management by the Administrator;
e) Testing of access control;
f) Testing of audit;
g) Abstract machine testing; and
h) Consequence of successive failed login attempts.
12.3 Independent Penetration Testing
Subsequent to the examination of the developer’s vulnerability analysis and test activities,
limited independent evaluator penetration testing was conducted. Penetration testing did not
uncover any exploitable vulnerabilities for the ICMS in the anticipated, restrictive operating
environment.
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 8 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
12.4 Conduct of Testing
The ICMS was subjected to a comprehensive suite of formally-documented, independent
functional tests. The testing took place at the DOMUS IT Security Laboratories located in
Ottawa, Ontario. The CCS Certification Body witnessed a portion of the independent testing.
The detailed testing activities, including configurations, procedures, test cases, expected
results and observed results are documented in the ETR.
12.5 Testing Results
The developer tests and independent functional tests yielded the expected results, providing
assurance that the ICMS behaves as specified in its ST and functional specification.
13 Results of the Evaluation
This evaluation has provided the basis for an EAL 3 level of assurance. The overall verdict
for the evaluation is PASS. These results are supported by evidence in the ETR.
14 Evaluator Comments, Observations and Recommendations
The ICMS must be operated in accordance with the ICMS Operating Instructions and must
be installed within a non-hostile and well-managed user community.
15 Acronyms and Abbreviations
Acronym/Abbreviation/Initialization Description
CCEF Common Criteria Evaluation Facility
CCRA Common Criteria Recognition Arrangement
CCS Common Criteria Evaluation and Certification
Scheme
CEM Common Methodology for Information Technology
Security Evaluation
CR Certification Report
CSE Communications Security Establishment
EAL Evaluation Assurance Level
ETR Evaluation Technical Report
ISO International Organisation for Standardisation
IT Information Technology
ITSET Information Technology Security Evaluation and
Testing
ECMS External Communications Management System
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 9 of 10 -
Certification Report Thales Communications S.A.
Internal Communications Management System (ICMS)
Version 3.7.1.0
___________________________________________________________________________
Version 1.0 19 August 2004
- Page 10 of 10 -
ICMS Internal Communications Management System
PALCAN Program for the Accreditation of Laboratories
Canada
ST Security Target
TOE Target of Evaluation
16 References
This section lists all documentation used as source material for this report:
a) Common Criteria for Information Technology Security Evaluation, CCIMB-99-
031/032/033, Version 2.1, August 1999.
b) Common Methodology for Information Technology Security Evaluation, CEM-
99/045, Part 2: Evaluation and Methodology, Version 1.0, August 1999.
c) CCS #4: Technical Oversight for TOE Evaluation, Canadian Common Criteria
Evaluation and Certification Scheme (CCS), Version 1.0, 3 October 2002.
d) Security Target Internal Communications Management System, Version 3.7.1.0,
Issue 1.4, 23 July 2004.
e) Evaluation Technical Report (ETR) Internal Communications Management System,
Version 1.0, 11 August 2004.