Purpose Present Drivers and Context for Firewalls Define Firewall Technology Present examples of Firewall Technology Discuss Design Issues Discuss Service and Support Issues Exchange Ideas and Concerns about Risk, Security and Firewalls
NOT An unveiling of a firewall service at SU A definition of a firewall service A forum for final decisions An exhaustive technical presentation A specific review of SU implementations
Data
Category A
Client
Access
Security
S = 1/A
Remote
Wireless
Risk
Mitigation
Affiliation
Authentication
Authorization
Host
Firewall
Balance
Packet
Header
Source
Destination
Port
Firewall
Router
Classic
Rules
Permit
Deny
Established
Tiers
Layers
Zones
Vulnerabilities
Horizontal
Vertical
Development
Production
NOT An unveiling of a firewall service at SU A definition of a firewall service A forum for final decisions An exhaustive technical presentation A specific review of SU implementations
Service
SPOC
Inventory
Questions APPLICATION INVENTORY FOR FIREWALL What is the name of the application? What are the names, locations, OS types, and IP addresses of the computers that host the application? Include the TCP ports that the application uses. Are there unique development and/or testing environments? If yes to #3, will the application use http or https or both? What measures of usage do you have? Are there peak periods of usage? Is there a web server component to the application? If yes, on which computer will it be installed? Is there a database component to the application? If yes, on which computer(s) will it be installed? If yes to #7, is the data sensitive University data – data that is protected by one of the Federal Privacy Acts? If there a unique application layer that mediates between the web services and the database services? If yes, on which computer(s) will it be installed? Who will install, upgrade and maintain the application? These are the application supporters. Will the application supporters need direct access to the web, application and/or database server? Will Firewall Exceptions rules be needed to grant this access? Are the application supporters Stanford employees or outside vendors/contractors? How is change managed in the application? What are the maintenance windows? Will the servers need AFS access? Will the servers need NFS access? Will the servers need Kerberos access? How will the servers be backed up? Will the servers need NTP access? What Windows domain will the servers be using? What type of ongoing service monitoring will be in place? Who is the appropriate person to make Security decisions about the application? How many users do you expect to be using the application? What is the user authentication that will be used for the application?
Pictures
Rules
Risk
Escalation
Moves
Acceptance
Troubleshooting
VPN
Monitoring
Audit
Costs
Numerator
Denominator
Risk Costs