Transcript Survivable Network Analysis --Oracle Financial

Oracle Financial System
Project Team:
Aseem Gupta
Jeng Toa Lee
Jun Lu
Kevin
Patrick Zhu
Thomas Verghese
Weicheng Wong
Xuegong Wang ( Jeff )
Date : 26th September, 2001
AGENDA
•Project Objective
•Project Scope and Plan
•Team Charter
•Communication Plan
•System Understanding
Sept 26, 2001
Survivable Network Analysis
2
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, 2001
Survivable Network Analysis
3
Define Intrusion
Scenarios
D 1.1 Project Team Created,
Team Charter
D 2.1 Developing Usage
scenarios
D 1.2 Communication Plan
D2.2 Identifying Essential
Services and Assets
• Identify resources, time, tools,
risk,access and objectives of
the attackers
D2.3 Identifying essential
service/ assets usage scenarios
D3.2 Develop Intrusion
Scenarios
D1.3 Understanding Existing
System
•Network Topology
•Hardware and Software
Components
•User Functions and Workflows
•Critical Services and Assets
D2.4 Identifying Essential
Components
•Administrative Control Domains
•Identify required architecture
parts
•Vendor Dependencies
•Tracing Scenarios
D 3.1 Create Attacker Profiles
• Determine usage scenarios
• Identify compromisable
components
D3.3 Customer review
4
Survivability
Analysis
Milestone
4
Define Essential
Services
3
Milestone
3
2
Milestone
2
1
System
Understanding
Milestone
1
Milestone Chart
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
•Connectivity with other Systems
•Security Components and
Policies
D4.5 Customer Review
D2.5 Customer Review
•Attack and Intrusion Experience
D 1.4 Project Plan Created
Sept 26, 2001
Survivable Network Analysis
4
Project Plan
Sept 26, 2001
Survivable Network Analysis
5
Team Charter
S.No
1
2
3
4
5
6
7
8
Sept 26, 2001
Name
Kevin
Thomas Verghese
Assem Gupta
Jeng Toa Lee
Jun Lu
Xuegong Wang (Jeff)
Weicheng Wang
Patrick Zhu
Responsibilty
Lead module 1
Lead module 1
Lead Module 2
Lead Module 2
Lead Module 3
Lead Module 3
Lead Module 4
Lead Module 4
Email
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
Survivable Network Analysis
Contact Number
412 238 2657, 412 422 5926
412 661 8976
412 422 5926
412 862 2757, 412 519 5553
412 363 6197
412 606 1062
412 687 1392
6
Communication Plan
S.No
1
2
3
Sept 26, 2001
Description
Purpose
Medium
Review Project
Progress and
Work on Next
Steps
Person to Person
Get system
understanding from
the client and
Client Meeting
review with him
Person to Person
Interaction between Work on action
team members
actions
Email
Weekly Meeting
Between team
members
Frequency
Attendees
Once a week
All team members
As required
Selected team members
As required
All team members
Survivable Network Analysis
7
System Understanding
Sept 26, 2001
Survivable Network Analysis
8
System Architecture
Sept 26, 2001
Survivable Network Analysis
9
System Topology
Wind, ES450
2 CPUs, 1GB RAM
Testing
Ethernet
Mistral, Sun E4500
8 CPUs, 8GB RAM
Production
Chinook, SUN E3500
8CPUs, 8GB RAM
Disaster Recovery
Sept 26, 2001
Firewall
Survivable Network Analysis
Outside
Firewall
10
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, 2001
Survivable Network Analysis
11
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, 2001
Survivable Network Analysis
12
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, 2001
Survivable Network Analysis
13
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, 2001
Survivable Network Analysis
14
Disaster Recovery

Backup

- The production system shut down at 4am for 1-1.5 hours
 - Flush over to the Recovery system every 10-15 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, 2001
Survivable Network Analysis
15
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, 2001
Survivable Network Analysis
16
Next Steps
•Identify Intruder Profiles
•Identify Intrusion Scenarios
Sept 26, 2001
Survivable Network Analysis
17