SANE: A Protection Architecture for Enterprise Networks

By Martín Casado, Tal Garfinkel, Aditya Akella, Michael J. Freedman, Dan Boneh, Nick McKeown. USENIX Security Symposium, 2006

296 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/5a3a095371ce86a9d4125201352e48131ebd2cdb

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

A Survey and a Layered Taxonomy of Software-Defined Networking (2014, methodology): “SANE [8] is a single protection layer consisting of a logically centralized server that enforces several security policies (access control, firewall, network address translation, etc.) within the enterprise network.”
Onix: A Distributed Control Platform for Large-scale Production Networks (2010, background): “Second, Onix allows for aggregation in which the network managed by a cluster of Onix nodes appears as a single node in a separate cluster’s NIB.”
Software-defined networking (SDN): a survey (2016, background): “[157] SANE system provides a single protection layer where controller includes access control rules instead of having them in firewalls as in traditional networks Logically centralizing routing and access control decisions to allow or deny access.”
Design and Implementation of a Consolidated Middlebox Architecture (2012, methodology): “, [14, 33, 24, 23]), and software consolidation is commonly used in data centers.”
NOX: towards an operating system for networks (2008, unknown): “The SANE/Ethane systems were designed around a single application: identity-based access control.”
Security in Software Defined Networks: A Survey (2015, unknown): “Secure Architecture for the Networked Enterprise (SANE) [13] is a clean-slate protection architecture for enterprise networks.”
Revisiting Traffic Anomaly Detection Using Software Defined Networking (2011, background): “While there has been significant previous work in this domain [14,16,17], recently Openflow [7,28] has become the standard bearer for the SDN paradigm.”
Sdn Security: A Survey (2013, background): “Without a signi ﬁ cant increase in focus on security, it will not be possible for SDN to support the evolving capability associated with, for example, Network Functions Virtualization (NFV) [3].”
A security enforcement kernel for OpenFlow networks (2012, background): “Ethane [5] is a more practical and backwards-compatible instantiation of SANE that requires no modi.cation to end hosts.”