Specifications

A31003-D3000-P100-01-76A9, 10-2013

OpenStage and Desk Phone IP SIP V3, Security Checklist, Planning Guide 5

Introduction

History of Change

1 Introduction

Related Topics

1.2 General Remarks

Information and communication and their seamless integration in “Unified

Communications and Collaboration“ (UCC) are important, valuable assets

forming the core parts of an enterprise business. These assets require every

enterprise provide specific levels of protection, depending on individual require-

ments to availability, confidentiality, integrity and compliance for the communi-

cation system and IT infrastructure it utilizes.

Unify attempts to provide a common standard of features and settings of security

parameters within delivered products. Beyond this, we generally recommend

• to adapt these default settings to the needs of the individual customer and the

specific characteristic of the solution to be deployed

• to weigh the costs of implementing security measures against the risks of

omitting a security measureand to “harden” the systems appropriately.

Product Security Checklists are published as a basis to support the customer and

service department in both direct and indirect channels, as well as self-

maintainers, to document security setting agreements and discussions.

The Security Checklists can be used for two purposes:

• In the planning and design phase of a particular customer project:

Use the Product Security Checklists of every relevant product to evaluate, if

all products that make part of the solution can be aligned with the customer’s

security requirements – and document in the Checklist, how they can be

aligned. The Product Security Checklist containing customer alignments can

be identified as Customer specific Product Security Checklist.

This ensures that security measures are appropriately considered and

included in the Statement of Work to build the basis for the agreement

between Unify and the customer: who will be responsible for the individual

security measures:

Date Version What

2013-09-20 0.1 Initial Draft

2013-10-14 0.2 Update with comments received. There

are structural changes in some areas to

better align with the SCL template

2013-10-23 1.0 Update with comments received.

Added References into CLs.

Changed Siemens to Unify