Upload
lamdat
View
222
Download
1
Embed Size (px)
Citation preview
March, 2007 Stanford Security Forum
A Network Architecture forSecurity Management
Martin CasadoJustin PettitJianying LuoMichael FreedmanTal GarfinkleDan BonehNick McKeownScott Shenker
Presented By: Martin CasadoPhD Student in Computer Science, Stanford [email protected]://www.stanford.edu/~casado
March, 2007 Stanford Security Forum
What we’d likePrinciple 1: Manage network using policy over real names
“Nancy can access Payroll”“Laptops can’t accept incoming connections”
“VoIP phones mustn’t move”
Nancy
PayrollPrinciple 2: Policy should dictate the path packets follow
“CEO traffic should not pass through engineering”“Guest flows must pass through http proxy”
“Laptop flows must pass through IDS”
Principle 3: The origin of packets should be known
Principle 4: Network should log all connectivityFor diagnostics and auditing
March, 2007 Stanford Security Forum
Enforcement Hurdles (Today)Bindings between names and addresses keep changing, are not authenticated.Route is generally unknown to the manager (and security system). And changes.No standard for source routingHow to keep security policy consistent in dynamic network?
NancyHost: b
IP: j
MAC: n
dns
Dhcp/ARP
Dynamic bindingsNot authenticatedEasily spoofed
March, 2007 Stanford Security Forum
Security and Policy Today(?)
Payroll
dns
dhcp
1. Network Access Control/Policy/Management2. Proxies (Web, Email, …)3. Monitoring/Mapping
March, 2007 Stanford Security Forum
Security and Policy TodayThrow silicon at the problem
Special purposes processorsTCAMs (the universal hardware hammer)
Layer security on top of networkingOften at the cost of redundancyOften at odds with routingOften at the cost of diagnostics
Bottom Line: Desired service model requirements not provided by yesterday’s architecture
March, 2007 Stanford Security Forum
EthaneManage network from centralized controller
Standard Desktop PCRoutingName-address bindingsPolicy declarationPermission Checks
Perform security check per flow
Enforce security decisions using very simple switches
Carefully manage all name to address bindings
March, 2007 Stanford Security Forum
dhcp
Ethane 10K View
Nancy
Payroll
Host: bIP: jMAC: n
Host: aIP: iMAC: m
dns
“Nancy can access Payroll”“Laptops can’t accept
incoming connections”“VoIP phones mustn’t move”“CEO traffic should not pass
through engineering”“Guest flows must pass
through http proxy”“Laptop flows must pass
through IDS”
learningspanning tree
ospf
controller
March, 2007 Stanford Security Forum
Ethane in six steps
PayrollHost: aIP: iMAC: m
“Nancy can access Payroll”“Laptops can’t accept
incoming connections”“VoIP phones mustn’t move”“CEO traffic should not pass
through engineering”“Guest flows must pass
through http proxy”“Laptop flows must pass
through IDS”
controller
NancyHost: bIP: jMAC: n
login?
OK: Nancy → payroll. Port 4
OK: Nancy → payroll. Port 3
OK: Nancy → payroll. Port 4
OK: Nancy → payroll. Port 2
OK: Nancy → payroll. Port 4
Register Authenticate Send Check Setup flow Communicate
Payroll → credentialsNancy → credentials
March, 2007 Stanford Security Forum
in port, ether hdr, src ip, dst ip, src port, dst port
Forwarding
Out portOutput queue (isolation)Overwrite IP header (NAT)Overwrite MAC header (MAC hiding)
End-to-end L2 isolationNAT by overwriting IP headerMAC hiding by overriding the MAC header
March, 2007 Stanford Security Forum
PropertiesBackwards compatible
No modifications to end-hostsCooperates with existing switches
Extremely simple switchesno need for TCAMSLine speeds are easyMore is good!
Sophisticated service modelIsolation, NAT, MAC filtering, waypoints
Fine-grain control of each flowCan require different forms of authentication for different access points (e.g. stronger for wireless than wired)
March, 2007 Stanford Security Forum
Supporting Policy Namespace
• Namespace covers(users, hosts, access points, protocols)
• Controller manages all name bindings– Require authentication for each binding– Do not update bindings without re-authentication– Revoke bindings on user movement
User NameIP Mac Switch Port
Host Name
March, 2007 Stanford Security Forum
From Policy to Fast Lookup
PolicyFile
NameBindings
Fast Lookup(packet classification)
Compiler
Journal
Journal
User authentication
Address allocation
Host authentication
RouteComputation
IncomingPacket
March, 2007 Stanford Security Forum
Namespace Properties
• DNS-like interface to all bindings• Namespace binding can match packet to ..
– Sending user, host– Sending location(regardless of when it was sent)
• Journalling of global policy allows – Full policy roll-back– ‘What-if’ testing
March, 2007 Stanford Security Forum
Design Summary
• Rather than rely on custom hardware for per-packet computation, centralize and use commodity processors for per-flow computation
• Reduce switches to cheap, simple flow tables• Policy runtime supports secure namespace
– Policy allows complex service model– Interface to the namespace, rich and with “memory” to
aid in diagnostics
• So … does it work?
March, 2007 Stanford Security Forum
Many Questions
• Central controller– Performance & Scalability– Robustness to failure
• Appropriate policy language• Simple/intuitive management interface…• …and transparent to user.
March, 2007 Stanford Security Forum
Our Deployment
• 300+ hosts at Stanford: Servers, laptops, desktops, phones.
• 19 switches– Hardware 4x1GE switch (FPGA)– Wireless access point (openWRT)– Software 4x100MbE switch (Linux)
• Controller cheap-o Fry’s PC• Policy: 132 rules to replicate policy
March, 2007 Stanford Security Forum
Deployment
March, 2007 Stanford Security Forum
Lessons so far…
• Controller handles >10,000 flows/second• Enough for 22k active IPs?• Multiple ways to handle redundancy
– Cold-standby, hot-standby, stateless, stateful• Transparent to users
(even remotely at home!)
March, 2007 Stanford Security Forum
Lessons so far…
• Service discovery is a pain– Makes up the majority of flows– Inherently sends to broadcast
• Undocumented protocols exist (and are used!)
March, 2007 Stanford Security Forum
Future Plans1. Grow deployment in department
– 1GE switches and access points– Use traditional switch with VLANs as a mux.
2. Increase deployment at Stanford?3. Other schools…?
EthaneGig HW Switch
V1 V3 V5V4V2
March, 2007 Stanford Security Forum
Questions?
March, 2007 Stanford Security Forum
dhcp
TodayPrinciple 1: Manage network using policy over real names
“Nancy can access Payroll”“Laptops can’t accept incoming connections”
“VoIP phones mustn’t move”
Nancy
Payroll
Host: bIP: jMAC: n
Host: aIP: iMAC: m
dns
learningspanning tree
ospf
“Everyone who is not Nancy cannot access payroll”
Q: How to identify them?Q: Where do their packets flow?
Today
ACL: Jim’s IP, payrollACL: Jen’s IP, payroll
ACL: Jen’s IP, payroll
Jen
March, 2007 Stanford Security Forum
Waypoints
Payroll
“Nancy can access Payroll”“Laptops can’t accept
incoming connections”“VoIP phones mustn’t move”“CEO traffic should not pass
through engineering”“Guest flows must pass
through http proxy”“Flows to Payroll must pass
through IDS”
controller
Nancy