Transcript
Page 1: Mike Rogers Director of Development, Reflection 2007
Page 2: Mike Rogers Director of Development, Reflection 2007

Mike RogersDirector of Development, Reflection 2007Deploying Reflection for IBM 2007 for Maximum Security

Page 3: Mike Rogers Director of Development, Reflection 2007

Agenda• Goals of secure deployment• Deployment preparation walkthrough

– Securing of data stream– Limiting user capabilities– Preventing unauthorized configurations and macros– Protecting sensitive data– Preparing your workstation installation

• Strategic future directions• Where to get more information• Q & A

Page 4: Mike Rogers Director of Development, Reflection 2007

Deployment PreparationWalkthrough

Page 5: Mike Rogers Director of Development, Reflection 2007

Security Considerations

5

Secure D

eployment

Page 6: Mike Rogers Director of Development, Reflection 2007

6

Securing the Data Stream

• Goals– Protect sensitive data from being transmitted in “the

clear.”– Utilize strong certificate-based authentication methods.– Use ELF for sign on to IBM Mainframes.

• Tools– Security Configuration in Reflection for IBM 2007– Reflection Certificate Manager

• Results– Configuration files that will be deployed to end-users

Page 7: Mike Rogers Director of Development, Reflection 2007

7

Limiting User Capabilities

• Goals– Prevent users from reconfiguring key configuration values.– Hide product functions from users.

• Tools– Access Configuration Utility– Ribbon UI Designer

• Results– Access Security Configuration Files– UI Configuration Files– Capability of elevating to Administrator on end-user PCs

Page 8: Mike Rogers Director of Development, Reflection 2007

8

Preventing Unauthorized Configurations and Macros

• Goals– Prevent users from running “uncontrolled” macros.– Allow users to only connect to hosts you want them to.– Centrally manage macros and configuration files.

• Tools– Trusted Locations Configuration User-Interface

• Results– Application Configuration File

Page 9: Mike Rogers Director of Development, Reflection 2007

9

Protecting Sensitive Data

• Goals– Prevent users from capturing sensitive data on the

clipboard, to the printer, and to other applications such as Microsoft Office.

– Allow users to capture pertinent non-sensitive data while masking sensitive data.

– Define custom data patterns that are deemed sensitive.• Tools

– Privacy Filters• Results

– Application Configuration File

Page 10: Mike Rogers Director of Development, Reflection 2007

10

Preparing Your Workstation Installation

• Goals– Create an pre-configured installation that can be used for a

group of users.– Pre-package configuration data, macros and other files

with the product installation.– Deliver data into “best practice” locations on the PC.

• Tools– Reflection Customization Tool

• Results– Microsoft Installer Transform File– Companion Installer(s) for configuration data and user data

Page 11: Mike Rogers Director of Development, Reflection 2007

Future Directions

Page 12: Mike Rogers Director of Development, Reflection 2007

12

Future Directions

• Communication Security– Continued Support for Emerging Industry Standards and

Certifications.• Information Privacy

– Filtering of on-screen data– Masking of user-input

• Configuration and Macro Security– Signed macros and session files

• Platform Integration– Microsoft Group Policy Support

Page 14: Mike Rogers Director of Development, Reflection 2007

14

Where to get more information (continued)

• Reflection for IBM 2007 Evaluation Guide: http://www.attachmate.com/docs/Reflection/2007/R1/Eval/R2007EvalGuide.pdf

• Bryan Grunow, lead software engineer, [email protected]

• Kris Lall, product manager, [email protected]

• Damon Dreke, product marketing manager, [email protected]

Page 15: Mike Rogers Director of Development, Reflection 2007

Q & A


Recommended