October 10-13, 2006 San Diego Convention Center, San Diego California Integrating Preparedness Into Everyday Operations Jeffrey Stern Vice President, Business Development

October 10-13, 2006 San Diego Convention Center, San Diego California Productivity Identifying the Goal Time TodayDisruptive Event Recovery Trajectory Partial Preparedness “Response” Zone “Target” Zone

October 10-13, 2006 San Diego Convention Center, San Diego California The Problem: 3-Parts & Cyclical Technical Issues  Change is constant  Multiple infrastructures Social Issues  Change is hard  People forget Business Issues  Change is constant  Limited resources

October 10-13, 2006 San Diego Convention Center, San Diego California Social Engineering  Practice “Teleworking”, Not “Disaster Drills”  Change-related issues mitigated  Enables adaptive workflow, knowledge and tools are in place and operational  Teleworking Goals  100% of workforce teleworking 20% of the time  Culture: Nothing special, just the way work gets done The Telework Coalition

October 10-13, 2006 San Diego Convention Center, San Diego California Social Engineering The Telework Coalition Telework Benchmark Study 2006 “A telework program pays for itself in reduced real estate needs, increased employee productivity, improved employee retention, reduced absenteeism, and the opportunity to recruit from a larger talent pool.”  Current benefits (not just “in the event of…”)

October 10-13, 2006 San Diego Convention Center, San Diego California Assessing Resiliency ApplicationsDistributed? Accessibility? DataReplicated? Frequency? HardwareRedundant? Distributed? Internet/WANMultiple connections? Speed? SecurityUnintentional barrier? Compromised? LAN/EthernetReplicable? Technical Engineering Technology Inventory Resiliency vs. Co$t? Frequency x Duration x Hourly Cost = Lost Profits Source: ComputerWorld

October 10-13, 2006 San Diego Convention Center, San Diego California LAN/ Ethernet Layer 7 Application Layer 6 Presentation Layer 5 Session Layer 4 Transport Layer 3 Network Layer 2 Data Link Layer 1 Physical OSI 7 Layer Model Layer 7 Application Layer 6 Presentation Layer 5 Session Layer 4 Transport Layer 3 Network Layer 2 Data Link Layer 1 Physical Headquarters Data In Data Out Teleworker VPN Are Not Ethernet IPSec VPNs SSL VPNs VPNs  Behavior change  Not like ‘being in the office’  Poorer performance  Some apps, net svcs, simply not supported  Flooding likely, not an everyday, everyone, everything tool  Dynamic provisioning?

October 10-13, 2006 San Diego Convention Center, San Diego California LAN/ Ethernet Layer 7 Application Layer 6 Presentation Layer 5 Session Layer 4 Transport Layer 3 Network Layer 2 Data Link Layer 1 Physical OSI 7 Layer Model Layer 7 Application Layer 6 Presentation Layer 5 Session Layer 4 Transport Layer 3 Network Layer 2 Data Link Layer 1 Physical Headquarters Data In Data Out Teleworker Ethernet is Everyday Ethernet Advantage  No Behavior change  Absorbs change  Eliminates Remote Access  Performance  Universal applicability  Universal compatibility  Major cost benefit as everything rides for free  Simple & intuitive  Everyday preparedness

October 10-13, 2006 San Diego Convention Center, San Diego California Technical Issues  Change is constant  Multiple infrastructures Social Issues  Change is hard  People forget Business Issues  Change is constant  Limited resources Aim Above the “Response Zone” Ethernet Advantage  No Behavior change  Absorbs change  Eliminates Remote Access  Performance  Universal applicability  Universal compatibility  Major cost benefit as everything rides for free  Simple & intuitive  Everyday preparedness

October 10-13, 2006 San Diego Convention Center, San Diego California Jeffrey Stern Vice President, Business Development Thank You! 4962 Fairmont Avenue Second Floor Bethesda, MD