Oracle Financial System Project Team: Aseem Gupta Jeng Toa Lee Jun Lu Kevin Patrick Zhu Thomas Verghese Weicheng Wong Xuegong Wang ( Jeff ) Date : 26 th September, 2001

Sept 26, 2001Survivable Network Analysis2 AGENDA Project Objective Project Scope and Plan Team Charter Communication Plan System Understanding

Sept 26, 2001Survivable Network Analysis3 Project Objective Understand Survivability Risks and Strategies to improve survivability  A university-wide accounting and financial system  Services  Financial service modules  Self-service applications  Application desktop integrator (ADI)  Budget spreadsheet  Integrate feeder systems  Billing, reporting, reconciliation

Sept 26, 2001Survivable Network Analysis4 D 2.1 Developing Usage scenarios D2.2 Identifying Essential Services and Assets D2.3 Identifying essential service/ assets usage scenarios D2.4 Identifying Essential Components Identify required architecture parts Tracing Scenarios D2.5 Customer Review D 4.1 Identify Strategies for Survivability Resistance Recognition Recovery D 4.2 Develop Criteria for choice of strategy to the architecture D 4.3 Make Recommendations D4.4 Identify Next Steps D4.5 Customer Review System Understanding Define Essential Services Survivability Analysis D 1.1 Project Team Created, Team Charter D 1.2 Communication Plan D1.3 Understanding Existing System Network Topology Hardware and Software Components User Functions and Workflows Critical Services and Assets Administrative Control Domains Vendor Dependencies Connectivity with other Systems Security Components and Policies Attack and Intrusion Experience D 1.4 Project Plan Created Define Intrusion Scenarios D 3.1 Create Attacker Profiles Identify resources, time, tools, risk,access and objectives of the attackers D3.2 Develop Intrusion Scenarios Determine usage scenarios Identify compromisable components D3.3 Customer review Milestone 1 Milestone 2 Milestone 3 Milestone 4 Satyajeet Grover for any queries Milestone Chart

Sept 26, 2001Survivable Network Analysis5 Project Plan

Sept 26, 2001Survivable Network Analysis6 Team Charter

Sept 26, 2001Survivable Network Analysis7 Communication Plan

Sept 26, 2001Survivable Network Analysis8 System Understanding

Sept 26, 2001Survivable Network Analysis9 System Architecture

Sept 26, 2001Survivable Network Analysis10 System Topology Wind, ES450 2 CPUs, 1GB RAM Wind, ES450 2 CPUs, 1GB RAM Mistral, Sun E CPUs, 8GB RAM Chinook, SUN E3500 8CPUs, 8GB RAM Chinook, SUN E3500 8CPUs, 8GB RAM Ethernet Outside Firewall Testing Production Disaster Recovery

Sept 26, 2001Survivable Network Analysis11 System Transactions Transaction volume – Database grows at 2GB/month Traffic – Self-services users: around 4,000 people – Every day users: around 100 people System developer – 1 project leader – 2.5 DBAs

Sept 26, 2001Survivable Network Analysis12 All Stakeholders Module users – Super user who own a module and is responsible for it Purchasing module Accounts payable module Accounts receivable module Grants module General ledger Labor distribution module Power users – Business administrator, Government fund manager System developers – Project manager, DBAs Individual users

Sept 26, 2001Survivable Network Analysis13 System Requirements Support all major campus desktop platforms Achieve excellent performance on all platforms Implement a “thin client” Minimize software installation, distribution and maintenance Leverage existing infrastructure Mitigate any/all security risks

Sept 26, 2001Survivable Network Analysis14 Security/Survivability Strategies Signed Java Applet RSA RC4 40-bit standard from of encryption Secure Socket Layer Kerberos-based authentication IP filtering Firewall Disaster Recovery

Sept 26, 2001Survivable Network Analysis15 Disaster Recovery Backup - The production system shut down at 4am for hours - Flush over to the Recovery system every minutes - The disaster recovery system also keeps 1 day and 5 minute transactions Survivability risks – If the production system is down, it takes 2 hours to fill over – Minor system upgrade takes 6 months Ever attacked? – Nobody intruded or found intruded. – The system was down twice due to the hardware failure. The longest was half a day.

Sept 26, 2001Survivable Network Analysis16 Security Policies Badge: to access the system machines Andrew ID: to log into the first system Application Password: to launch the applications IP address filtering Module owners have different access right based on the properties of their modules DBAs have limited access right to the production system

Sept 26, 2001Survivable Network Analysis17 Next Steps Identify Intruder Profiles Identify Intrusion Scenarios