Security-Driven Architecture: Network Architecture Session

1
Security-Driven ArchitectureNetwork
Architecture Session

• Participants
• David Clark
• Nick Feamster
• George Kesidis
• Vic Thomas
• Z. Morley Mao

2
End hosts insecurity demand security support from
networks

• Considerations
• Information assurance protect the information
• Availability is a key topic theory of
  availability
• Social and regulatory considerations, e.g.,
  logging IM for stock traders
• Networks responsibility
• identify nodes worthy of trust, block malicious
  traffic at sources
• Flow-based/usage-based pricing helpful to improve
  security
• require authentication framework identify
  authentication, service authentication
• Enforce traffic behavior from end hosts.
• Secure, verifiable host-network coordination to
  enforce correct behavior, bi-lateral verification.

3
Other key ideas discussed

• Use the contract or SLA to construct traffic
  policers for identifying malicious application
  behavior
• Community-based anomaly detection for popular
  applications
• Accountability for ISPs
• Fast, privacy preserving performance comparison,
  line-rate crypto
• Attribution determine and trace the perpetrator
• crypto-bound addressing, packets carrying
  manifest, cross-layer provenance
• Containment provide assurances
• Partition networks into regions, just-in-time
  instantiation
• Management and configuration verifiable configs
• Protocol correctness e.g., correct routing
  behavior
• Device trust is a challenge
• Use of GENI for evaluation