Security Requirements for Software Defined Networks Internet Area WG IETF 85: Atlanta November 4, 2012 Margaret Wasserman

Slides:



Advertisements
Similar presentations
SDN Abstractions. In an SDN Ideal World, we want… multiple applications (Composition): – So, need to worry about sharing. – About isolation. Network policies.
Advertisements

Firewalls By Tahaei Fall What is a firewall? a choke point of control and monitoring interconnects networks with differing trust imposes restrictions.
1 Firewalls. 2 References 1.Mark Stamp, Information Security: Principles and Practice, Wiley Interscience, Robert Zalenski, Firewall Technologies,
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
K. Salah 1 Chapter 31 Security in the Internet. K. Salah 2 Figure 31.5 Position of TLS Transport Layer Security (TLS) was designed to provide security.
FIREWALLS & NETWORK SECURITY with Intrusion Detection and VPNs, 2 nd ed. 6 Packet Filtering By Whitman, Mattord, & Austin© 2008 Course Technology.
Jaehoon (Paul) Jeong, Hyoungshick Kim, and Jung-Soo Park
(part 3).  Switches, also known as switching hubs, have become an increasingly important part of our networking today, because when working with hubs,
Session-ID Requirements for IETF84 draft-ietf-insipid-session-id-reqts-00 1 August 2012 Paul Jones, Gonzalo Salgueiro, James Polk, Laura Liess, Hadriel.
Network Security (Firewall) Instructor: Professor Morteza Anvari Student: Xiuxian Chen ID: Term: Spring 2001.
Additional SugarCRM details for complete, functional, and portable deployment.
A Brief Taxonomy of Firewalls
Network Architecture and Protocol Concepts. Network Architectures (1) The network provides one or more communication services to applications –A service.
Mobile IP Traversal Of NAT Devices By, Vivek Nemarugommula.
Kostas Giotis, Yiannos Kryftis, Vasilis Maglaris
Service Function Chaining Use Cases draft-liu-service-chaining-use-cases IETF 89 London, March 3, 2014 Will Liu, Hongyu Li, Oliver Huang, Huawei Technologies.
Chapter 13 – Network Security
Version 4.0. Objectives Describe how networks impact our daily lives. Describe the role of data networking in the human network. Identify the key components.
1 Chapter 6: Proxy Server in Internet and Intranet Designs Designs That Include Proxy Server Essential Proxy Server Design Concepts Data Protection in.
SDN Abstractions Lecture 20 Aditya Akella. Going beyond defining a virtual network, configuring specific network functions Application interface – PANE:
SOS EGEE ‘06 GGF Security Auditing Service: Draft Architecture Brian Tierney Dan Gunter Lawrence Berkeley National Laboratory Marty Humphrey University.
Windows 7 Firewall.
Network Security Lecture 9 Presented by: Dr. Munam Ali Shah.
OV Copyright © 2011 Element K Content LLC. All rights reserved. Network Security  Network Perimeter Security  Intrusion Detection and Prevention.
Firewall Technologies Prepared by: Dalia Al Dabbagh Manar Abd Al- Rhman University of Palestine
Authentication Mechanism for Port Control Protocol (PCP) draft-wasserman-pcp-authentication-01.txt Margaret Wasserman Sam Hartman Painless Security Dacheng.
Dynamic Virtual Networks (DVNE) Margaret Wasserman & Paddy Nallur November 11, 2010 IETF Beijing, China.
1 Topic 2: Lesson 3 Intro to Firewalls Summary. 2 Basic questions What is a firewall? What is a firewall? What can a firewall do? What can a firewall.
1 Chapter Overview Password Protection Security Models Firewalls Security Protocols.
Firewalls  Firewall sits between the corporate network and the Internet Prevents unauthorized access from the InternetPrevents unauthorized access from.
Network Security. 2 SECURITY REQUIREMENTS Privacy (Confidentiality) Data only be accessible by authorized parties Authenticity A host or service be able.
© 2006 Cisco Systems, Inc. All rights reserved. Cisco IOS Threat Defense Features.
SOA-39: Securing Your SOA Francois Martel Principal Solution Engineer Mitigating Security Risks of a De-coupled Infrastructure.
Security Requirements of NVO3 draft-hartman-nvo3-security-requirements-01 S. Hartman M. Wasserman D. Zhang 1.
Integrating and Troubleshooting Citrix Access Gateway.
Security, Accounting, and Assurance Mahdi N. Bojnordi 2004
Switch Features Most enterprise-capable switches have a number of features that make the switch attractive for large organizations. The following is a.
Introduction to Grids By: Fetahi Z. Wuhib [CSD2004-Team19]
A Network Security -Firewall Bruce Turin.
1 VLANs Relates to Lab 6. Short module on basics of VLAN switching.
Chapter 40 Network Security (Access Control, Encryption, Firewalls)
Office of Science U.S. Department of Energy Grid Security at NERSC/LBL Presented by Steve Chan Network, Security and Servers
Intro to Web Services Dr. John P. Abraham UTPA. What are Web Services? Applications execute across multiple computers on a network.  The machine on which.
Trust Router Overview IETF 86, Orlando, FL Routing Area Meeting Margaret Wasserman
IP packet filtering Breno de Medeiros. Florida State University Fall 2005 Packet filtering Packet filtering is a network security mechanism that works.
DOTS Requirements Andrew Mortensen November 2015 IETF 94 1.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 Security Requirements of NVO3 draft-hartman-nvo3-security-requirements-00.
Draft-fm-bess-service-chaining-01 Prague, July 2015 Rex Fernando Stuart Mackie Dhananjaya Rao Bruno Rijsman Maria Napierala.
Virtual Local Area Networks In Security By Mark Reed.
Software Defined Networking BY RAVI NAMBOORI. Overview  Origins of SDN.  What is SDN ?  Original Definition of SDN.  What = Why We need SDN ?  Conclusion.
25/09/ Firewall, IDS & IPS basics. Summary Firewalls Intrusion detection system Intrusion prevention system.
Dr. Ir. Yeffry Handoko Putra
CompTIA Security+ Study Guide (SY0-401)
Examples based on draft-cheng-supa-applicability-00.txt
OGF PGI – EDGI Security Use Case and Requirements
VIRTUALIZATION & CLOUD COMPUTING
IEEE 802 OmniRAN Study Group: SDN Use Case
Module 4 Remote Login.
Firewalls.
CompTIA Security+ Study Guide (SY0-401)
Firewalls.
Firewalls and GMPLS Networks: A token based approach
Software Defined Networking (SDN)
ISMS Information Security Management System
PLUG-N-HARVEST ID: H2020-EU
Firewalls Routers, Switches, Hubs VPNs
Requirements for Client-facing Interface to Security controller draft-ietf-i2nsf-client-facing-interface-req-02 Rakesh Kumar Juniper networks.
Firewalls Jiang Long Spring 2002.
Introduction to Network Security
FIREWALL.
Presentation transcript:

Security Requirements for Software Defined Networks Internet Area WG IETF 85: Atlanta November 4, 2012 Margaret Wasserman

SDN Security Requirements Draft  Security Requirements in the SDN Model  requirements-00 requirements-00  Currently individual work, not tied to any WG  Feedback to authors, discussion on 2

Security Requirements for SDN  Discusses requirements for an SDN protocol running between “applications” and an SDN controller  Describes security requirements for three classes of applications  Apps may not be run by the same organization as the Managed Service Provider (MSP) 3 App SDN Controller (run by MSP) Switch

Three Classes of Applications (1)  Class 1: Network Sensitive Applications  Applications that require particular network characteristics  Needs access to ports in particular VLAN  Requires specific path characteristics  Traffic stays within a specific jurisdiction  Traffic travels only over certain equipment  Wants to monitor costs of traffic/flows  May want to reject or accept certain flows 4

Three Classes of Applications (2)  Class 2: Services for the Network  Application provides a service for the network  e.g. Firewall, content inspection or intrusion detection 5

Three Classes of Applications (3)  Class 3: Packaged Network Services  Combines previous two classes  e.g. Application of Class 1 that wishes for all traffic to be sent through a border firewall service  Application is requesting instantiation of another application as a virtual element in the network  Permits abstraction and re-use of network applications 6

Authentication & Authorization  Need for authentication and authorization across multiple organizations 7

Security Requirements (1)  REQ1: Authentication is REQUIRED to the controller. Authentication SHOULD support existing credentials that are likely to be used in the datacenter.  REQ2: The interface to the SDN controller MUST support authorizing specific network resources to applications and manipulating the authorizations of applications.  REQ3: The SDN controller MUST provide facilities to isolate one application from another. 8

Security Requirements (2)  REQ 4: The SDN controller interface MUST support a controller acting as a proxy on behalf of applications.  REQ 4a: The SDN interface SHOULD support a way of associating an audit ID or other tracking ID so that requests can be correlated with an original application when a proxy acts on behalf of an application.  REQ 5: The SDN controller interface MUST provide mechanisms for operators and applications to enforce privacy. 9

Security Requirements (3)  REQ 6: The SDN controller interface MUST support delegating access to a subset of resources; as part of delegation new authorization and privacy constraints MAY be supplied. This supports the security needs of the debugging use case, aspects of the nested application use case, and facilitates other inter-organization uses. 10

Nested Application Security (1)  REQ N1: The SDN controller interface MUST support controlling authorization for what nested applications an outer application can nest.  REQ N2: The controller MUST separate authorizations held by one instance of a nested application from authorizations help by other instances of the same nested application. 11

Nested Application Security (2)  REQ N3: The SDN controller interface SHOULD provide outer applications a way to learn a nested application's policy for sharing information between instances.  REQ N4: Nested applications MUST be able to authenticate on behalf of a specific outer application. This facilitates authorization, accounting and auditing. 12

Nested Application Security (3)  REQ N5: Nested applications MUST be able to specify privacy policy for what resources are visible to the outer application.  REQ N6: Outer applications MUST be able to specify privacy policy and authorizations with regard to what outer resources the nested application can interact with. 13

Questions? Feedback?  Send questions of feedback to the draft authors  Sam Hartman  Margaret Wasserman  Dacheng Zhang  Or, discuss these drafts on 14