IBM Security Guardium Tech Talk

Transcription

1 IBM Security Guardium Tech Talk Hints and tips for upgrading to V10 Vlad Langman Manager, Guardium L3 Support IBM Security Omar Raza Guardium QA Engineer IBM Security This call is being recorded. Please leave the web conference if you object.

2 December 3rd Tech Talk Next tech talk: 4 Things to Know About the New IBM Guardium V10 for z/os Speakers: Howie Hirsch, z/os Technical Specialist Barry Davis, Rocket Software Product Specialist Date and time: Thursday, December 3rd 11:30 AM US Eastern, 8:30 AM US Pacific Register here: 2

3 Table of contents Compatibility Considerations Enterprise Upgrade Strategy Considerations for upgrade Troubleshooting 3

4 Compatibility Considerations Compatibility limitations Appliance Technical Requirements RAM - Minimum 24G CPU/vCPU - Minimum 4 cores HD range: Upgraded appliances HD range (300G - < 2TB) Newly built appliances (only) HD range (300G - >2TB) Appliance hardware compatible with RH 6.5 version Upgrade procedure limitations V10 upgrade patch available only for 64-bit version appliances at GPU v9.0p200 or higher Upgrade procedure is not available for customers with customized partitions Upgrade procedure does not support resizing or realignments of the partitions. Restore from system backup stored in previous version V10 supports restoring system backup file from any v9.x version. 4

5 Compatibility Considerations Compatibility limitations Limitations - While "hybrid mode" is supported by Guardium, many functions are limited until all components are at the same version. (discussed in later slides) Mixed environment - Customers are strongly encouraged to choose the upgrade strategy which minimizes duration where appliances operate in mixed V9.x and V10.0 environment. Downtime - Typical upgrade of Guardium appliance expected to last for several hours. During this time, the appliance might not be accessible and would not be performing any data collection activity. Duration - Upgrade process duration most contributing factors: Size, Usage and Data distribution of internal MySQL database tables Capacity of the appliance (Virtual Memory, CPU and so on) Purge of unnecessary data from the appliance. It will significantly decreases duration of the upgrade process. Pre-upgrade Health Check enforces DB size to be below 50% capacity. Our recommendations to keep databases under 20% threshold. Language support Guardium V10 upgrade patch currently supports only English language appliances upgrade. Layout - There is no ability to keep v9 custom layout. V10 layout will be overwritten. 5

6 Compatibility Considerations Versions compatibility Transition options to migrate to version V10 appliance V10 upgrade method From v9.0p200 (64-bit) and above v9.0p200 (32-bit) and above Rebuild v10 appliance & Restore v9 system backup yes yes Apply v10 upgrade patch yes no v9.0 - v9.0p180 yes no v8.2 or earlier no no Mixed environment CM, Aggregators, Collectors or STAP agents are on different Guardium versions which is usually the case during upgrade transition period. 6

7 Compatibility Considerations Versions compatibility Recommended transition path to version V10 appliance Source system Target system Upgrade Path v8.2 v10 v9.0 (32 bit) v10 v9.0 (64 bit) Below patch 200 v9.0 (64 bit) Above patch 200 v10 v10 1. Create v8.2 system backup 2. Rebuild appliance with v9.5 (64 bit) ISO, available from Passport Advantage 3. Install v9.0p600 (64-bit) Cumulative patch 4. Restore system backup from pre-upgrade v8.2 system (For collectors upgrade all corresponding STAPs to latest v9 before proceeding to the next step) 5. Install v9.0 - v10.0 upgrade patch 1. Install v9.0p600 (v9.5) GPU patch (32 bit) (For appliances above p200, this step is optional) 2. Install v9.0p600 (32-bit) Cumulative patch (Install on entire environment before proceeding to next step) 3. Create v9 system backup 4. Rebuild appliance with v10 (64 bit) ISO, available from Passport Advantage 4. Restore system backup from v9.0 system 1. Install v9.0p600 (v9.5) GPU patch (64 bit) 2. Create v9 system backup 3. Install v9.0 - v10.0 upgrade patch available on FixCentral. 1. Create v9 system backup 2. Install v9.0 - v10.0 upgrade patch available on FixCentral. 7

8 Compatibility Considerations Versions compatibility Mixed environment compatibility V10 Appliance compatibility Source appliance v9.0p200 (64-bit) and above v9.0p200 (32-bit) and above Central Management Aggregation STAP agents yes yes yes yes yes yes v9.0 - v9.0p180 no yes yes v8.2 or earlier no no no Mixed environment CM, Aggregators, Collectors or STAP agents are on different Guardium versions which is usually the case during upgrade transition period. 8

9 Compatibility Considerations Versions compatibility Mixed environment known limitations Unable to distribute any configurations from v10 CM to v9p200+ MU The following reports will result in a SQL error when viewed on v9p200+ managed units: Agg/Archive Log Connections Quarantined Installed Patches Inactive Inspection Engines S-TAP Verification Unable to register additional v9p200+ MUs after upgrading CM to v10 Note: Units registered prior to the upgrade will remain registered after the upgrade Unable to distribute policy on v9p200+ MUs via v10 CM Note: Policies already installed on the MUs prior to the upgrade will remain unchanged. Portal sync will continue synching between v10 CM and v9p200+ MUs Unable to distribute PATCH BACKUP settings from v10 CM to v9p200+ MUs Note: PATCH BACKUP settings defined prior to upgrade will remain unchanged UI layout customization and distribution is not supported from v10 CM to v9p200+ MUs Enterprise Search (ES) will work in a mixed environment that consists of a v10 CM managing v9p530+ MUs. Please note the GUI will need to be restarted in order to reinitialize ES. Managed units prior to GPU500 will be unable to take advantage of ES although Quick Search (QS) will still be available locally Unable to view remote data on v10 CM from v9p200+ MUs. This extends to any report that relies on the use of remote data sources 9

10 Enterprise Upgrade Strategy 10

11 Enterprise Upgrade Strategy Upgrade Planning Upgrade of large enterprise environments requires thorough planning and preparation. Upgrade strategy and logistics Scope (be conservative) Change control management Required personnel availability Contingency planning The upgrade process usually cannot be done simultaneously on all appliances and all S-TAPs. Therefore it requires multi-staged upgrade approach. During transition period, Guardium environment will operate in hybrid mode with Version 9.0 and Version 10.0 Guardium software (Mixed environment). Upgrade IBM InfoSphere Guardium environment in Top-to-Bottom order 11

12 Enterprise Upgrade Strategy Installation Procedure Upgrade checklist: 1. Check system requirements 2. Purge the systems 3. Make a system backup (req. 50% available appliance space). 4. If enabled, turn off high-availability 5. Stop Export process 6. Install latest version of Pre-Upgrade HealthCheck patch Pre-Upgrade HealthCheck is mandatory prerequisite for v10 upgrade Download the latest version of HC prior to installation Verify that HC is successfully completed before attempting next step 7. Install Upgrade Patch Use upgrade patch 9.0p10000_Upgrade_to_Version_10.0 This patch could be install on any type of Guardium appliance. Patch consist of full v10 RPM ISO content + migration utilities and tools. Patch size is currently over 2.5G 12

13 Enterprise Upgrade Strategy Contingency Planning Before attempting to rebuild the appliance Create System Backup to generate a snapshot of current data and configuration. Download latest Pre-upgrade Health Check patch Download latest Product v10 ISO from PA Download Product Licenses from PA (to be used after ISO installation and restore). In unlikely case of upgrade process failure (which can t be repaired by IBM Support) Proceed with rebuild/restore option: Run Latest v9 Health Check patch (if possible) Run HC patch to identify and prevent potential issues with restore system backup Rebuild appliance: Build/rebuild new v10 appliance using v10 64-bit product ISO available on PA Restoring System backup data: Use restore db-from-prev-version command to restore system backup. V10 Restore from system backup supported for any v9.x system backup. V10 Restoring Guardium Archives supported from v9.x and older versions. V10 Supports Import Definition from v9.x based exports. 13

14 Enterprise Upgrade Strategy Top-to-Bottom / Vertical Approach Central Manager A B Aggregators Collectors Guardium agents 14

15 Enterprise Upgrade Strategy Migration Procedure for environments below GPU 200 V8.2 - V9.0p180 V9.0p600+ V10 Central Manager Upgrade Upgrade (64bit) Rebuild (32bit) Aggregators Upgrade Upgrade (64bit) Rebuild (32bit) Collectors Upgrade Upgrade (64bit) Rebuild (32bit) Guardium agents Live Update Live Update 15

16 Enterprise Upgrade Strategy Migration Procedure for environment with GPU 200 and up V9.0p200 - V9.0p600+ V10 Central Manager Upgrade (from 64bit) Rebuild (from 32bit) Aggregators Upgrade (from 64bit) Rebuild (from 32bit) Collectors Upgrade (from 64bit) Rebuild (from 32bit) Guardium agents Live Update 16

17 Enterprise Upgrade Strategy Migration Procedure using BACKUP CM appliance V9.0p200 - V9.0p600+ V10 Backup Central Manager Upgrade (from 64bit) Rebuild (from 32 bit) CM BCM Central Manager Upgrade (from 64bit) Rebuild (from 32 bit) CM Aggregators Upgrade (from 64bit) Rebuild (from 32 bit) Collectors Upgrade (from 64bit) Rebuild (from 32 bit) Guardium agents Live Update 17

18 Upgrade Considerations 18

19 V10 Upgrade Considerations 64-bit Environment What do I need to keep in mind before starting? Do I meet hardware requirements? Do I have enough system space to migrate to V10? Do I have a backup CM environment? How will product licensing be affected? Do I have everything that I need for the upgrade? What should I expect during the procedure? 1. Installing the patch 2. OS Installation What should I consider afterwards? If only upgrading the CM, am I aware of the limitations? Have all my managed units been moved over successfully? Are my systems operating as they should? 19

20 V10 Upgrade Considerations 32-bit Environment What do I need to keep in mind before starting? Wait can I still use the upgrade patch? Do I meet hardware requirements? Do I have a backup CM environment? How will product licensing be affected? What should I expect during the procedure? 1. Installing the ISO 2. Restore db-from-prev-version What should I consider afterwards? If only migrating the CM, am I aware of the limitations? Have all my managed units been moved over successfully? Are my systems operating as they should? 20

21 Troubleshooting 21

22 Upgrade Patch Installation Flow Patch 9.0p10000 Phase 1 Install guard_network, migrator.sh, pathuuid Copy upgrade RPMs into local HD folder (/var/guardium_iso) Check migration requirements Phase 2 Create the Migration folder (/var/guardium_migration) Stop non-db Services (Tomcat,snif,snif_buff_usage, ) Copy Configuration data to Migration folder Stop DB + Slide DB data into Migration folder Slide additional data into Migration folder (Lucene/Solr files, etc) Add a copy of the RHEL 6.5 kernel, initrd and upgrade.ks into /boot dir Update grub boot config Phase 3 Restart system onto RHEL6 kernel on RAM Disk Find and Protect Migration folder partition (/var) Install RPMs from the local HD folder Phase 4 First boot onto v10 (recognize upgrade mode) Restore data and config from /var/guardium_migration Upgrade data to v10 structure Brings up services and Completes installation. Step 1 2: monitoring of the progress using regular patch installation commands: GUI Guardium Monitor -> Installed Patches CLI -> show system patch installed Step 3: Appliance is not available and not connected to the network. Monitor the progress using appliance console (KVM for hardware appliances or ESXi tools). Step 4: Monitor progress using: CLI show upgrade-status command which displays step by step progress of the upgrade 22

23 Upgrade Patch Installation Flow Patch 9.0p

24 Support commands show upgrade-status CLI prompt> show upgrade-status Tue Aug 18 18:55:21 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:1.0:INFO:Starting Migration of v9 system to v10 Tue Aug 18 18:55:22 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:1.0:INFO:Invoked with args: --localisodir --check Tue Aug 18 18:55:37 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:1.0:SUCCESS:Passed Requirements Checks Tue Aug 18 18:55:37 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:1.0:INFO:Starting Migration of v9 system to v10 Tue Aug 18 18:55:37 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:1.0:INFO:Invoked with args: --localisodir --patch --reboot Tue Aug 18 18:55:38 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:1.0:SUCCESS:Passed Requirements Checks Tue Aug 18 18:56:38 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.0:SUCCESS:Migration Tree Creation Tue Aug 18 18:56:38 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.0:SUCCESS:Grabbed Network Information Tue Aug 18 18:56:39 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.1:SUCCESS:Shutting down nondb Services Tue Aug 18 18:56:39 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.1:INFO:Starting PreDBShutdown Preservation Tue Aug 18 18:56:40 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.1:SUCCESS: PreDBShutdown Preservation Tue Aug 18 18:58:47 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.2:SUCCESS:Shut down MySQL Tue Aug 18 18:58:47 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.3:INFO:Starting PostDBShutdown Preservation Tue Aug 18 18:58:48 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.3:SUCCESS:PostDBShutdown Preservation Tue Aug 18 18:58:48 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.4:SUCCESS:RHEL6 Kernel & Initrd Prep Tue Aug 18 18:58:48 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.4:SUCCESS:Guardium Hint Put into Place Tue Aug 18 18:58:49 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.5:SUCCESS:Grub Prepped Tue Aug 18 18:58:49 EDT 2015 INFO: GV9_UPGRD_PHASEMSG:2.6:SUCCESS:Rebooting onto Install Kernel and Image GV10_UPGRD_PHASEMSG:3.0:INFO:Booted onto Installation Kernel GV10_UPGRD_PHASEMSG:3.1:SUCCESS:Found Migration Directory GV10_UPGRD_PHASEMSG:3.2:INFO:Protecting data on /dev/sda2 GV10_UPGRD_PHASEMSG:3.2:INFO:Removing old /var/tmp GV10_UPGRD_PHASEMSG:3.3:INFO:About to start V10 and OS Installation GV10_UPGRD_PHASEMSG:3.5:SUCCESS:Upgrade mode detected, setting upgrade flag GV10_UPGRD_PHASEMSG:3.4:SUCCESS:Applying Permission and security adjustments GV10_UPGRD_PHASEMSG:3.5:SUCCESS:Post RPM Installation Upgrade Log Saving GV10_UPGRD_PHASEMSG:3.5:SUCCESS:Post RPM Installation Configuration GV10_UPGRD_PHASEMSG:3.6:INFO:About to Shutdown and Reboot onto V10.. Phase 1 Phase 2 Phase 3 24

25 Support commands show upgrade-status (Cont d). GV10_UPGRD_PHASEMSG:4.0:INFO:Firstboot onto V10 GV10_UPGRD_PHASEMSG:4.1:SUCCESS:Upgrade flag detected, starting upgrade Tue Aug 18 19:11:15 EDT 2015 INFO [pre-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.2:INFO:Upgrading a Unit of type 76 Tue Aug 18 19:11:18 EDT 2015 INFO [pre-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.2:INFO:Copying LUCENE files Tue Aug 18 19:11:18 EDT 2015 INFO [pre-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.2:INFO:Copying ANALYTIC files Tue Aug 18 19:11:19 EDT 2015 INFO [pre-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.2:INFO:Copying DATAMART files Tue Aug 18 19:11:19 EDT 2015 INFO [pre-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.2:INFO:Copying Previous Network Configuration Files Tue Aug 18 19:11:25 EDT 2015 INFO [pre-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.3:SUCCESS:Network Info migrated and normalized to V10 Tue Aug 18 19:11:26 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.4:INFO:Moving DB Data to V10 location Tue Aug 18 19:11:27 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.4:INFO:Moved DB Data to V10 location Tue Aug 18 19:11:27 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.4:INFO:Setup DB Config files Tue Aug 18 19:11:27 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.5:INFO:Starting MySQL daemon Tue Aug 18 19:11:33 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.5:SUCCESS:Started MySQL daemon Tue Aug 18 19:11:33 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.5:INFO:MySQL Should be up now Tue Aug 18 19:11:33 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.6:INFO:Pre-adjusted UNIT TYPE before DB Migration Tue Aug 18 19:11:33 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.6:INFO:About to start Database Migration Tue Aug 18 19:11:33 EDT 2015 INFO [db_migration.sh]: GV10_UPGRD_PHASEMSG:4.6:INFO:DB Migration to V10 Schema starting Tue Aug 18 19:11:34 EDT 2015 INFO [db_migration.sh]: GV10_UPGRD_PHASEMSG:4.7:INFO:Ran mysql_init_db_maint.sql Wed Aug 19 10:07:44 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.8:SUCCESS:Finished Database Migration Wed Aug 19 10:07:49 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.9:INFO:Licenses Upgraded Wed Aug 19 10:08:10 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.10:INFO:PSML Upgraded Wed Aug 19 10:08:10 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.11:INFO:Language is English Wed Aug 19 10:08:10 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.12:INFO:Reconfiguring Database onto V10 Schema Wed Aug 19 10:08:33 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.12:INFO:Restarting Database with V10 Config Wed Aug 19 10:08:37 EDT 2015 INFO [mysql-mig-setup]: GV10_UPGRD_PHASEMSG:4.12:INFO:Database now on V10 Config Wed Aug 19 17:35:45 EDT 2015 INFO [guard-upgrade]: GV10_UPGRD_PHASEMSG:4.13:INFO:Starting Key and Certificate Migration Wed Aug 19 17:36:01 EDT 2015 INFO [guard-upgrade]: GV10_UPGRD_PHASEMSG:4.13:INFO:Completed Key and Cert Migration Wed Aug 19 17:36:02 EDT 2015 INFO [guard-upgrade]: GV10_UPGRD_PHASEMSG:4.14:INFO:Completed Migration of Search Data Wed Aug 19 17:36:02 EDT 2015 INFO [guard-upgrade]: GV10_UPGRD_PHASEMSG:4.15:INFO:Completed Migration of Passwords Wed Aug 19 17:36:02 EDT 2015 INFO [guard-upgrade]: GV10_UPGRD_PHASEMSG:4.16:INFO:guard_sender configured to run as in v9 Wed Aug 19 17:36:10 EDT 2015 INFO [post-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.16:INFO:About to apply Security Policies Wed Aug 19 17:36:21 EDT 2015 INFO [post-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.16:INFO:Security Policies applied Wed Aug 19 17:36:21 EDT 2015 INFO [post-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.17:INFO:About to Clean up after Migration Wed Aug 19 17:36:34 EDT 2015 INFO [post-guard-upgrade]: GV10_UPGRD_PHASEMSG:4.17:INFO:Cleaned up after Migration Wed Aug 19 17:36:34 EDT 2015 INFO [post-guard-upgrade]: GV10_UPGRD_PHASEMSG:5.0:INFO:Migration Complete Phase 4 25

26 Troubleshooting Installation Log location changed: $GUARD_HOME/installlog (Original /var/log/guard/diag/depot) Installlog directory content: installlogs]# ll -tr total rw-r--r-- 1 root root May 7 10:59 V9MIGRATIONLOG -rw-r--r-- 1 root guardium May 7 12:34 install.log -rw-r--r-- 1 root guardium May 7 12:39 upgrade.log -rw-r--r-- 1 root guardium May 7 12:40 setup.log 26

27 Additional Materials 27

28 Additional Materials Guardium v10 Detailed Release Notes 01.ibm.com/support/docview.wss?uid=swg &myns=swgimgmt&mynp=OCSSMPHH&mync=E&cm_sp=swgimgmt --OCSSMPHH-%3CA%20HREF=%27index.php?page=-OCSSMPHH- &from=released_documents%27%3e?%3c/a%3e-e Guardium System Requirements / Platforms Supported: Guardium: High upgrade roadmap: Guardium: step by step upgrade procedure document: Supplied for Controlled Upgrade customers. Will be published on FixCentral at a later date. 28

29 29

30 Statement of Good Security Practices: IT system security involves protecting systems and information through prevention, detection and response to improper access from within and outside your enterprise. Improper access can result in information being altered, destroyed, misappropriated or misused or can result in damage to or misuse of your systems, including for use in attacks on others. No IT system or product should be considered completely secure and no single product, service or security measure can be completely effective in preventing improper use or access. IBM systems, products and services are designed to be part of a lawful, comprehensive security approach, which will necessarily involve additional operational procedures, and may require other systems, products or services to be most effective. IBM DOES NOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES ARE IMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THE MALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY. Copyright IBM Corporation All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. 30

31 Legal notices and disclaimers Copyright 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS document is distributed "AS IS" without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided. Any statements regarding IBM s future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation. It is the customer s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right. Other company, product, or service names may be trademarks or service marks of others. A current list of IBM trademarks is available at Copyright and trademark information