1. Is Your Enterprise Ready For A MetaDirectory??? Presented by Brian Picard CISSP

2. Personal Background Progressive Insurance – Security Architect ◦ 11 Long Years ( 6 years in Identity/Security ) ◦ CISSP, GIAC – GSEC, Microsoft Server/Client Certified ◦ Wide range of background experience ( ie Server Administration, Networking, Development, Identity, and Security Architecture ) Private Consulting – Anything Technical ◦ 10 Years ( 5 years in Identity/Security ) ◦ Network Development ◦ Server Implementations ◦ Custom Development ◦ Security Consultations and Instruction

3. Agenda What is a MetaDirectory? Timeframes Pre Work Implementation Post Implementation

4. What is a Meta Directory Definition: A system that provides data flow between dissimilar data stores.

5. Timeframes Pre Work ◦ Involved Teams ◦ Product Selection ◦ Documentation Implementation ◦ Design ◦ Elevation Procedures Post Work ◦ Care and Feeding ◦ Additional Uses

6. Involved Teams ◦ Human Resources ◦ Telecom ◦ Real Estate ◦ Network OS ◦ Corporate Directory ◦ Mainframe Access ◦ Email Systems ◦ External Compliance Vendors ◦ Employee DB History ◦ Physical Access ◦ Application Teams ◦ …

7. Product Selection My Magic Triangle IBM Directory Integrator (IDI) Identity Lifecycle Manager (ILM) Sun Directory Server Ent Edition (DSEE)

8. Microsoft’s ILM Pros ◦ Good For High #’s of Changes ◦ No remote agents Cons – Slower – Lots of Custom Code Overview TelecomHR ILM Server Real Estate Corp Directory Active Directory Application A Read Write Application B

9. IBM’s IDI Pros ◦ Extremely Fast Changes ◦ Limited Coding Cons – Limited Transformations – Remote Agents Overview HRTelecomReal Estate Corp Directory Application AApplication B Agent Read Write

10. Sun’s DSEE Pros ◦ Extremely Fast Changes ◦ Most Accurate Data Cons – Slower Data Retrieval – Remote Agents Overview HR Telecom Real Estate Agent Read Write Sun DSEE Application A

11. Documentation Attribute Mapping Elevation Work Flow Cycle Processing Maps Prioritization matrix Customer/Provider Surveys

12. Attribute Mapping

13. Elevation Work Flow

14. Cycle Processing Maps

15. Prioritization matrix Technical Level is used to gauge the difficulty of moving this customer into the Meta Directory. 1-3 This is a high level of work involving multiple teams and a full project. 5-6 This is a medium level of difficulty requiring only a few teams and no project 9-10 This is a low level of difficulty and requires only a single team and very little time.

16. Surveys Provider ◦ What attributes can you provide? ◦ What attributes are open for general distribution? ◦ What attributes do you want to approve for distribution? ◦ What level of SLA do you have? Consumer ◦ What attributes do you need? ◦ What platform are they being moved to? ◦ How many server support this? ◦ What level of SLA do you have?

17. Design Business and Technical Requirements Hardware/Physical Layout Processing Cycle Metaverse Design (Attribute Mapping) Custom Code Sub Designs Monitoring Testing Backup and Restore

18. Elevation Procedures Don’t forget about software elevations best practices Follow the elevation process flow, that’s why you made it Take your time rolling out new systems and verify things are working properly before moving on

19. Care and Feeding Log Review ◦ Look for errors in the processing cycle ◦ Verify the correct cycles are running at the correct times ◦ Verify non-prod systems are available as described in your SLA Performance Review ◦ Verify your processing cycles aren’t running long ◦ Verify your server doesn’t get inundated when new systems come on board

20. Additional Uses Version Upgrades ◦ Peoplesoft Upgrade Product Changes ◦ Directory Servers

21. Wrap-Up Spend the time to do the upfront documentation Think through how this will fit into your enterprise both technically and non- technically Explain your SLAs, Designs, and Prioritization to everyone involved ahead of the actual implementation Be sure that all implemented systems are meshing well together before moving onto the next system.

22. Brian Picard CISSP GSEC MCP Brian_Picard@Progressive.com