session 1 framework

129
Session 1 Framework Security Threat Responsibility and Policy Architecture Response Flow Preparation

Upload: berg

Post on 24-Jan-2016

49 views

Category:

Documents


1 download

DESCRIPTION

Session 1 Framework. Security Threat Responsibility and Policy Architecture Response Flow Preparation. Emergency Response. Yan Wang 2006.09. Agenda. Framework & Technology Security Monitoring Response Measure Case Study & Discussion. Security Threat. Threat Evolution and Trends - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Session 1   Framework

Session 1 Framework

Security Threat

Responsibility and Policy

Architecture

Response Flow

Preparation

Page 2: Session 1   Framework

Emergency Response

Yan Wang

2006.09

Page 3: Session 1   Framework

Agenda

Framework & Technology

Security Monitoring

Response Measure

Case Study & Discussion

Page 4: Session 1   Framework

Security Threat

Threat Evolution and Trends

Threat Categories

Attacks Fundamental

Page 5: Session 1   Framework

Evolution of Availability Threats

Page 6: Session 1   Framework

Exploit Trends

Page 7: Session 1   Framework

Three Key Threat Categories• Reconnaissance

Unauthorized discovery and mapping of systems, services, or vulnerabilities

• Access

Unauthorized data manipulation, system access, or privilege escalation

• Denial of Service

Disable or corrupt networks, systems, or services

Page 8: Session 1   Framework

How do these impact ISPs?

• Reconnaissance – Happens all the time. It is part of

the “attack noise” of the Internet (along with low level

attacks and backscatter).

• Access – Break-ins on the edge of an ISP’s network

(I.e. customer CPE equipment) can impact the ISP’s core.

• DOS – The core threat to an ISP – knocking out

customers, infrastructure, and services.

Page 9: Session 1   Framework

Reconnaissance Methods

• Common commands and administrative utilities nslookup, ping, netcat, telnet, finger, rpcinfo, File Explorer, sr

vinfo, dumpacl

• Public tools Sniffers, SATAN, SAINT, NMAP, custom scripts

Page 10: Session 1   Framework

Network Sniffer

Page 11: Session 1   Framework

nmap

Page 12: Session 1   Framework

nmap

Page 13: Session 1   Framework

Why Do We Care?

Page 14: Session 1   Framework

Why Do We Care?

Page 15: Session 1   Framework

Access Methods

Page 16: Session 1   Framework

Access Methods (cont.)

Page 17: Session 1   Framework

Denial of Service Methods• Resource Overload Disk space, bandwidth, buffers, ...

Ping floods, SYN flood, UDP bombs, ...

• Software bugs Out of Band Data Crash: Ping of death, fragmentation…

• Toolkits TRINOO, Tribal Flood Net and friends

• Distributed attacks for amplification

Page 18: Session 1   Framework

DoS

Page 19: Session 1   Framework

DoS type• Resource Overload

Disk space, bandwidth, buffers, ...

Ping floods, SYN flood, UDP bombs, ...

• Out of Band Data Crash

Ping of death, ...

• Routing Capacity

Fill up packet buffers, queues, flow tables, and processing capabilities.

Page 20: Session 1   Framework

DoS Sequence

Page 21: Session 1   Framework

DDoS

Page 22: Session 1   Framework

DDoS Step 1: Crack Handlers and Agents

Page 23: Session 1   Framework

DDoS Step 2: Install Trojan & Covert Communication Channel

Page 24: Session 1   Framework

DDoS Step 3: Launch the Attack

Page 25: Session 1   Framework

DDOS Attack Characteristics• DDOS Arrays (handlers and agents) a maintenance i

ntensive. Take time and effort to create.• Launching attacks from an agent can be considered

a one shot weapon. Once the attack is launched, there is a risk of traceback. If someone traces back to the agent, they could watch and wait to see if the perpetrator returns to the agent.

Page 26: Session 1   Framework

Attacks Fundamental

Page 27: Session 1   Framework

Address Resolution Protocol (ARP)

Page 28: Session 1   Framework

ARP Datagram

Page 29: Session 1   Framework

Internet Protocol

Page 30: Session 1   Framework

IP Header

Page 31: Session 1   Framework

Internet Control Message Protocol (ICMP)

Page 32: Session 1   Framework

User Datagram Protocol (UDP)

Page 33: Session 1   Framework

Transport Control Protocol

Page 34: Session 1   Framework

TCP Header

Page 35: Session 1   Framework

TCP Establishment and Termination

Page 36: Session 1   Framework

Packet Spoofing

Page 37: Session 1   Framework

IP Spoofing

Page 38: Session 1   Framework

TCP Blind Spoofing

Page 39: Session 1   Framework

TCP blind spoofing (Cont.)

Page 40: Session 1   Framework

ARP Based Attacks

Page 41: Session 1   Framework

Gratuitous ARP

Page 42: Session 1   Framework

Misuse of Gratuitous ARP

Page 43: Session 1   Framework

A Test in the Lab

Page 44: Session 1   Framework

A Collection of Tools to Do:

Page 45: Session 1   Framework

ARP spoof in Action

Page 46: Session 1   Framework

More on ARP Spoof

Page 47: Session 1   Framework

Selective Sniffing

Page 48: Session 1   Framework

SSL/SSH Interception

Page 49: Session 1   Framework

SSL/SSH Interception

Page 50: Session 1   Framework

SSL/SSH Interception

Page 51: Session 1   Framework

ICMP Based Attacks-smurf

Page 52: Session 1   Framework

Smurf’s Script Kiddy Tool

Page 53: Session 1   Framework

ICMP Unreachable Teardown

Page 54: Session 1   Framework

IP Based AttacksIP Normal Fragmentation

Page 55: Session 1   Framework

IP Normal Fragmentation (Cont.)

Page 56: Session 1   Framework

IP Normal Reassembly

Page 57: Session 1   Framework

IP Reassembly Attack

Page 58: Session 1   Framework

IP Reassembly Attack (Cont.)

Page 59: Session 1   Framework

Ping of Death Attack Denial of Service

Page 60: Session 1   Framework

Ping of Death Attack Denial of Service

Page 61: Session 1   Framework

UDP Based Attacks

Looping UDP

Page 62: Session 1   Framework

DoS - Fraggle Attack

Page 63: Session 1   Framework

TCP Based Attacks

SYN Attack

Page 64: Session 1   Framework

TCP SYN Flood

Page 65: Session 1   Framework

TCP SYN Flood

Page 66: Session 1   Framework

TCP Session Hijacking

Page 67: Session 1   Framework

TCP DDOS Reflection Attacks

Page 68: Session 1   Framework

TCP DDOS Reflection Attacks

Page 69: Session 1   Framework

TCP DDOS Reflection Attacks

Page 70: Session 1   Framework

TCP DDOS Reflection Attacks

Page 71: Session 1   Framework

Other Attacks

Page 72: Session 1   Framework

Incident Response Team A Computer Security Incident Response Team (CSIR

T) is a team that performs, coordinates, and supports the response to security incidents that involve sites within a defined constituency.

Page 73: Session 1   Framework

ISP Security

ISP need to:

• Protect themselves• Help protect their customers from the Internet• Protect the Internet from their customers• At any given time there are between 20 to 40 DOS/DDOS attacks on the Net

Page 74: Session 1   Framework

Role of Service Providers

Page 75: Session 1   Framework

Role of Service Providers

Page 76: Session 1   Framework

Role of Service Providers

Page 77: Session 1   Framework

ISP Security Actions

Page 78: Session 1   Framework

Policy

Page 79: Session 1   Framework

Policy• Avoid extensive damage to data, systems and networks

due to not taking timely action to contain an intrusion

• Minimize the possibility of an intrusion affecting multiple systems both inside and outside an organization because staff did not know who to notify and what actions to take.

• Avoid negative exposure in the news media that can damage an organization’s public image and reputation.

• Avoid possible legal liability and prosecution for failure to exercise due care when systems are inadvertently or intentionally used to attack others.

Page 80: Session 1   Framework

Preparing to Respond

• Create an archive of original media, configuration files, and security-related patches for all router and host operating systems and application software versions

• Ensure that backup tools and procedures are working

• Create a database of contact information

• Select and install tools to use when responding to intrusions

Page 81: Session 1   Framework

Preparing to Respond (Cont.)

• Develop a plan and process to configure

isolated test systems and networks when

required

• Keep response plans, procedures and tools up

to date

• Consider performing a practice drill to test tools

and procedures

Page 82: Session 1   Framework

CERT Infrastructure

• Information Platform ( Website )• Tel, Mail• Event Processing System• Traffic Monitoring System• Intrusion Detection System

Page 83: Session 1   Framework

Security System Security System Architecture

Infra

structu

re

Identity Authen

Clock Synchronization

Security Monitoring System

Traffic Collection

Traffic Analyse and Account

emergency response service system

information issue system

Event

CooperationLeak Scan

Distributing IDS

IP info

Page 84: Session 1   Framework

CCERT Framework

CERNET Committee of Experts

Center CCERT

Regional CCERT

CCERT Expert Team

Campus CCERT

R&D Secretariat

Interprovincial CCERT

Page 85: Session 1   Framework

CCERT

R&

D

Liaison

Training

Analysis

Monitoring

Service

Committee of Experts

CCERT Framework

Page 86: Session 1   Framework

Response Flow

① Preparation② Detection③ Analysis④ Decision⑤ Control⑥ Announcement⑦ Statistic

Page 87: Session 1   Framework

Response Flow

0

10

20

30

40

50

60

70

80

90

1st Qtr 2nd Qtr 3rd Qtr 4th Qtr

helpdesk

Investigation

NOC

Traffic analyzing and monitoring

Signature based IDS

CERNETmanagement CNCERT/CC

OtherIRTs

UsersAdministrators

toolspatches

Attacksignature

Incident database

Whois info advisories

Common Event

Important Event

Page 88: Session 1   Framework

What Do ISPs Need to Do?

Page 89: Session 1   Framework

Components of Response

Analyze the event

Contain the incident

Eliminate intruder access

Restore operations

Update procedures based on lessons learned

Page 90: Session 1   Framework

Analyze Event

• What systems were used to gain access

• What systems were accessed by the intruder

• What information assets were available to those systems?

• What an intruder did after obtaining access

• What an intruder is currently doing

Page 91: Session 1   Framework

Contain the Intrusion

• Gain control of the systems involved

• Attempt to deny an intruder access to prevent

further damage

• Monitor systems and networks for subsequent

intruder access attempts

Page 92: Session 1   Framework

Eliminate Intruder Access

• Change all passwords on all systems accessed

• Restore system and application software and data, as needed

• What other systems might be vulnerable?

Page 93: Session 1   Framework

Restore Operations

• Validate the restored system

• Monitor systems and networks

• Notify users and management that systems are

again operational

Page 94: Session 1   Framework

Other• Build the Communications Channels to your Peers

and Customers• Build the Communications Channels to your Vendor

s

Page 95: Session 1   Framework

Preparation

• Securing the Router and the Management Plane

• Securing the Network and Data Plane

• Securing the Routing Protocol and Control Plane

• Anycast as a Security Tool

• Using IP Routing as a Security Tool

Page 96: Session 1   Framework

Terminology

Page 97: Session 1   Framework

Securing the Router and theManagement Plane

Page 98: Session 1   Framework

Routers do get Directly Attacked

Page 99: Session 1   Framework

Routers do get Directly Attacked

Page 100: Session 1   Framework

Router Security

Page 101: Session 1   Framework

Global Services You Turn OFF

Page 102: Session 1   Framework

Global Services You Turn OFF

Page 103: Session 1   Framework

Interface Services You Turn Off

Page 104: Session 1   Framework

Interface Services You Turn Off

Page 105: Session 1   Framework

Cisco Discovery Protocol

Page 106: Session 1   Framework

Cisco Discovery Protocol

Page 107: Session 1   Framework

Cisco Discovery Protocol

Page 108: Session 1   Framework

Use Enable Secret

Page 109: Session 1   Framework

Securing Access to the Router

Page 110: Session 1   Framework

RISK Assessment

Page 111: Session 1   Framework

Lock Down the VTY and Console Ports

Page 112: Session 1   Framework

VTY and Console Port Timeouts

Page 113: Session 1   Framework

VTY Security

Page 114: Session 1   Framework

VTY Security

Page 115: Session 1   Framework

Encrypt the Traffic from Staff to Device

Page 116: Session 1   Framework

SSH Support in ISP Code

Page 117: Session 1   Framework

Cisco IOS SSH Configuration

Page 118: Session 1   Framework

SSH Server Implementation

Page 119: Session 1   Framework

SSH Server Configuration Prerequisites

Page 120: Session 1   Framework

SSH Server Configuration

Page 121: Session 1   Framework

SSH Server Configuration (cont.)

Page 122: Session 1   Framework

SSH Server Configuration Summary

Page 123: Session 1   Framework

SSH Client Access

Page 124: Session 1   Framework

SSH Terminal-Line Access

Page 125: Session 1   Framework

Secure Copy (SCP)

Page 126: Session 1   Framework

Secure Copy (SCP)

Page 127: Session 1   Framework

Staff AAA to get into the Device

Page 128: Session 1   Framework

What is ISP AAA and ISP AA?

Page 129: Session 1   Framework

Separate Security Domains!