TMS zl Module Planning and Implementation Guide 2009-08
Table Of Contents
- Contents
- Glossary of Acronyms and Abbreviations
- 1.0 Purpose
- 2.0 Intended Audience
- 3.0 Objectives
- 4.0 Prerequisites
- 5.0 Skills
- 6.0 The HP ProCurve Threat Management Services zl Module
- 7.0 Common TMS Security Control Points
- 8.0 Deployment Considerations
- 9.0 Installation and Preparation of the TMS zl Module
- 10.0 Configuration of the TMS zl Module
- 11.0 Using multiple HP ProCurve Threat Management Services zl Modules
- Appendix A – Additional References
- Appendix B – Sample Company Information Assets Spreadsheet
- Sample “Information Assets” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- “Server Network Details” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- “TMS Zones” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- “Firewall Rules” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- /Sample “Company Information Assets” Microsoft Excel 2003 spreadsheet
- Appendix C – Information Gathering Tools
- Appendix D - Updating Switch Software
- Appendix E – Emergency Recovery Process
Page 5
1.0 Purpose
The purpose of this technical guide is to provide a technical understanding of the expected use cases for
the HP ProCurve Threat Management Services (TMS) zl Module in more complex networking
environments. It is intended to assist in the sale, design and implementation of HP ProCurve security
solutions using the TMS zl Module and also provides some specific, technical “how to” configuration
information.
2.0 Intended Audience
It is assumed that the tasks discussed in this document will be performed by technically skilled HP
Services professionals, HP and ProCurve Channel Partners, and enterprise purchasers of the HP
ProCurve TMS zl Module. The concepts may also be helpful as a basis for technical discussions
involving HP Solutions Architects/Technical Consultants.
ADD ASSUMPTION
It is also appropriate for those seeking guidance on the overall process of integrating HP ProCurve
security control products, including the HP ProCurve TMS zl Module, into enterprise customer
networking environments.
3.0 Objectives
The objectives of this technical guide are to:
1. Introduce the features of the HP ProCurve TMS zl Module.
2. Illustrate typical, expected use cases of the HP ProCurve TMS zl Module.
3. Provide a methodology for developing a de-facto security policy, if no customer security
policy(ies) exist(s), that will be used to create the security controls required for an initial
implementation.
4. Illustrate how to link security policy(ies) with security controls to be implemented on the HP
ProCurve TMS zl Module.
5. Show configuration examples of the major security control features of the HP ProCurve TMS
zl Module.
6. Discuss deployment scenarios where multiple HP ProCurve TMS zl Modules would meet
more complex business requirements.
4.0 Prerequisites
A security assessment of the environment into which the HP ProCurve TMS zl Module will
be introduced, including up-to-date physical, logical connectivity diagrams and any existing
security requirements
A security policy for the environment into which the HP ProCurve TMS zl Module is being
introduced
A set of clearly articulated goals for the implementation of the HP ProCurve TMS zl Module