Defining and Understanding Campus Policies
associated with Integrating a Science DMZ into
the Campus Environment
Moderator:
Wendy Huntoon, KINBER
Panelists:
Scott Baily, Colorado State University
Wallace Chase, Washington State University
Tony Brock, Oregon State University
Slide 1
Slide 1
Oregon State University
•
Slide 2
Oregon State University – Current Design
Slide 3
Oregon State University –Data Flows
Slide 4
Oregon State University – Technical Design
Slide 5
Oregon State University
Technology Portfolio Lifecycle:
1.
2.
3.
4.
5.
6.
7.
Market Portfolio Analysis
Due Diligence/Internal Testing
Executive Decision
External Pilot
Deployment
Support/Efficacy
Metrics/Sunset
- Why do we want to do this?
- Is this a good idea?
- Will this be part of the portfolio?
- What does it take to do this well?
- Do customers know about this?
- Is our value optimized?
- Is the value worth the service?
Slide 6
Oregon State University – Proposed
Policies/Standards by Lifecycle Stage
5.
Deployment
1.
2.
3.
6.
Technical Requirements for connecting
Use requirements (AUP? and/or eligibility to connect?)
User training, education and communication of expectations
Support/Efficacy
1.
Maintenance
1.
2.
3.
Security/Monitoring (CISO’s Office)
2.
1.
2.
3.
4.
5.
7.
Appropriate tools for monitoring and archival of data
Hardware refresh/renewal (applies to both user and IT equipment)
User issues – who do the users call? Who are the first, second and third tiers of support?
Data classification
Integration of compliance with NIST policies (if applicable)
Incident response and remediation procedures (compromised hosts, user notification, etc.)
Application of the 20 Critical Controls (require advanced, written agreement for auditing?)
User notification – communication of contact information and expectations
Metrics/Sunset
1.
Metrics and Review
1.
2.
Service Review – Is this still the appropriate design?
Annual Metrics – long-term documentation of performance
Sunset – Criteria for discontinuing service
2.
1.
2.
3.
4.
Termination of grant?
Minimum performance/age requirements
Change is type of use or purpose (i.e., is this still research or is it now “production”?)
User notification and consulting for potential alternative solutions
Slide 7
Washington State University
•
Slide 8
PAN-EDU-205
High Speed Scalable Research Core
Building the backbone to support big data and unique research at WSU Pullman…
Slide 9
Slide 9
Washington State University – Located in Pullman, WA (not Seattle…)
• Land-grant institution founded in 1890
• Around 30k students
• Several strong research programs that are data intensive
• Genomics
• Atmospheric
• Geologic
• Shock Physics
• National Smart Grid
• TRIGA reactor
•
•
•
•
History of very distributed infrastructure
Multiple HPC environments
Research spread across many locations
Solution needed to take these realities into account
Slide 10
Slide 10
Slide 11
Slide 11
Slide 12
Slide 12
Slide 13
Slide 13
Colorado State University
Slide 14
CSU is located in Fort Collins, CO
• Land Grant University founded in 1870
• Approximately 30K Students
• Research focus areas include
Engineering, Atmospheric and
Environmental Sci., Bioinformatics
• Very decentralized IT environment
• Moving toward the “condo model” for HPC
on campus
• Partnering with CU to implement a shared
HPC system to be located in Boulder, CO
Slide 15
CSU’s Implementation of the Science DMZ
Slide 16
Science DMZ represents new service, challenges
•
•
•
•
•
Unprecedented file transfer speeds are now possible
Many researchers are comfortable with the status quo
Lots of devils in the details
Exercising our governance process
No one said this would be easy!
Slide 17
Panel Discussion Questions
• Who gets to connect to the research network? Who makes
the call who gets access?
• All resources are limited, how do you deal with prioritization
of those resources?
• Do you allow for “commodity” internet access on your
research network or just connections to “pure” research
networks? What are the operational and security questions
this brings up?
• There seems to be a paradox between what may be
perceived as "lighter weight" security afforded by the
Science DMZ and tighter controls being required from
funding agencies, for example FISMA and NIH's Genomic
Data Sharing (GDS) Policy. How are you dealing with this?
Slide 18