-1-

Jaehoon (Paul) Jeong, Hyoungshick Kim, and Jung-Soo ParkSungkyunkwan University & ETRI

Requirements for Security Services based on Software-Defined

Networkingdraft-jeong-i2nsf-sdn-security-services-00

IETF 91, Honolulu, HI, November 13, 2014

-2-

Contents

I Introduction

V Use Cases

II

SDN-Based Security Services

III

Objectives

IV

Requirements

VI

Discussion

-3-

Standardization Status in ITU-T

Working Item in Study Group 17 (SG 17), Question 6 (Q.6) in ITU-T Our proposal for“Requirements for Security Services based on

Software-Defined Networking”was accepted as a working item in September Meeting in 2014.

Scope of the Draft in SG 17. Classify the network resources for SDN-based security services.

Define the requirements for SDN-based security services.

Define the enhanced framework to support SDN-based security ser-vices.

Define use cases for security services based on SDN.

3

-4-

MotivationLegacy Firewall

Firewall inspects packets that attempt to cross a network boundary.

Firewall rejects any illegal packets such as• Incoming requests to open illegal TCP connections,• Packets of other illegal types (e.g., UDP and ICMP), and• IP datagrams with illegal IP addresses (or ports).

Firewall provides security at the loss of flexibility and the cost of network administration. 4

-5-

Challenges in FirewallCost

The cost of adding firewalls to routers is substantial.

Performance Firewalls are often slower than the link speed of their network inter-

faces.

Management Managing access control dynamically across hundreds of network ele-

ments is a challenge.

Policy It is difficult to describe what are permitted and denied flows within the

specific organization.

Binding Packet-based access mechanism is not enough in practice since the

basic unit of access control is usually user or application.

• e.g., Skype connections for specific users are open.

5

-6-

Centralized Network Firewall based on Software-Defined Net-working (SDN)Centralized Network Firewall

Firewall rules can be managed flexibly by a centralized server.

SDN protocols can be used for a standard interface between firewall applications and switches.

6

Public network

Private network

Firewall

Switches

add or deleterules

1. <Match, Action>2. <Match, Action>3. …

-7-

Expectations for SDN-Based Firewall

Cost Ideally, one single firewall is enough.

Performance Firewalls can adaptively be deployed depending on network condi-

tions.

Management Firewall rules can dynamically be added with new attacks.

Policy Centralized view might be helpful to determine security policies.

Binding Application level rules can be defined by software.

7

-8-

SDN-Based Security Services

8

DDoS-Attack Mitigator

Firewall

SDN Controller

Switch2

Switch3

Switch1

Install new rules (e.g., drop packets with suspicious

patterns)

Incoming packets Incoming packets

-9-

High-Level Architecture for SDN-Based Security Services

9

Mu

lti-

Layer

Man

ag

em

en

t Fu

ncti

on

s

Security Application(e.g., Firewall, DDoS-Attack

Mitigation)

Application Support

Orchestration

Abstraction

Control Support

Data Transport and Processing

Application Layer

SDN Control Layer

Resource Layer

Resource-Control Interface

Application-Control Interface

-10-

ObjectivesPrompt reaction to new network attacks

SDN-based security services allow private networks to defend them-selves against new sophisticated network attacks.

Autonomous defense from network attacks SDN-based security services identify the category of network attack

(e.g., worms and DDoS attacks). They take counteraction for the defense without the intervention of

network administrators.

Network-load-aware resource allocation SDN-based security services measure the overhead of resources for

security services. They dynamically select resources considering load balance for the

maximum network performance.

10

-11-

Requirements

The support of the programmability of network resources to mit-igate network attacks.

The support of an application interface allowing the manage-ment of access control policies in an autonomous and prompt manner.

The support of a resource-control interface for control of net-work resources to mitigate network attacks.

The support of logically centralized control of network re-sources to mitigate network attacks.

11

-12-

Use CasesCentralized Firewall System

This is for malware packets.

Centralized DDoS-Attack Mitigator This is for DDoS-attack packets.

12

-13-

Centralized Firewall Sys-tem (1/2)

13

Firewall

SDN Controller

Switch2

Switch3

Switch1

Malware packet

1. Switch1 forwards an unknown flow’s packet to Firewall via SDN Controller.2. Firewall investigates the packet. 3. Firewall regards it as a malware packet with suspicious patterns.

-14-

Centralized Firewall Sys-tem (2/2)

14

Firewall

SDN Controller

Switch2

Switch3

Switch1

Install new rules (e.g., drop packets with suspicious

patterns)

Incoming packets Incoming packets

Report a malware’s packet to SDN

Controller

The malware’s packets are dropped

by switches

-15-

Centralized DDoS-Attack Miti-gator (1/2)

15

DDoS-Attack Mitigator

SDN Controller

Switch2

Switch3

Switch1

DDoS-attack packets

1. Switch1 suspects a flow’s packets with inter-arrival patterns.2. Switch1 reports this flow to DDoS-Attack Mitigator via SDN Controller.3. DDoS-Attack Mitigator computes a separate path for the suspicious flow.

-16- 16

DDoS-Attack Mitigator

SDN Controller

Switch2

Switch3

Switch1

Install new rules (e.g., forward packets with suspicious

inter-arrival patterns to a separate path with random drop)

Incoming packets Undropped Incoming packets

Report the suspicious flow to

SDN Controller

The suspicious flow’s packets are randomly dropped by Switch3 on

the separate path

Centralized DDoS-Attack Miti-gator (2/2)

-17-

Discussion

17

Direction of This Draft Develop SDN-based Security Services (e.g., Firewall and DDoS-

Attack Mitigator) including API. Include other Security Services, such as Preventing the leak-

age of internal traffic into the outside networks.

Direction of our ITU-T SG 17 Draft Develop Security Scenarios and Requirements for ITU-T

Y.3300 (Framework of Software-Defined Networking).

Thanks for your attention.

Any Comments or Questions?