Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.
-
Upload
darrell-tucker -
Category
Documents
-
view
213 -
download
0
Transcript of Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.
![Page 1: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/1.jpg)
Preliminary Conclusions
VO Box Task Force
GDB Meeting
5 april 2006
![Page 2: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/2.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
VO boxes, services, software, & securityJeff Templon 2015.01.14
![Page 3: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/3.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
We made a big fuss about this in 2006
Good example of whySome implications for vo sw
securityAs well as VO traceability
(cf current discussion)
Why this talk
VO sw security, GDB 2015.01.1414 January 2015
![Page 4: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/4.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
VO Box
Priorities, C.
Loomis, 7 June
20066
Classification of VO Services
Class 1: ◦ Can access site's services (and work
correctly) from a private network. (I.e. does not need to live within the trusted subnet of a farm.) Uses only service APIs/interfaces which are exposed to the external world past their firewall.
Class 2: ◦ Uses 'private' interfaces to access
information/services at the site (i.e. not exposed to those beyond the site's firewall). Essentially this is anything which is not a Class 1 service.
![Page 5: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/5.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
VO service authors write, install, maintain services. No site control or overview
If box can live in separate network, no problem. Hacked?◦Wipe the box◦Reinstall from scratch◦Say “here ya go” to the VO
If box has to live inside trusted subnet, huge forensic task to see whether a breach has occurred
Heart of the problem
VO sw security, GDB 2015.01.1414 January 2015
![Page 6: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/6.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
Used to have a class 2 serviceNot anymore .. Moved to vobox
networkPort scan revealed vulnerable
service listeningBecause we had it in class 1
network:◦Limit exposure through firewalling,
but leave functional and running for a while
◦Once fixed: wipe box & return to VO
VO Box
VO sw security, GDB 2015.01.1414 January 2015
![Page 7: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/7.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
Is class 2 by design … has to see SE namespace
Vulnerability found: service immediately shut down
Restarted only when fix was provided
Counterexample:ATLAS N2N service
VO sw security, GDB 2015.01.1414 January 2015
![Page 8: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/8.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
How many people potentially can add software to CVMFS repos?
What security measures are there (also in checking / patching sw in CVMFS)?
If VO deploys software for which trust is relevant beyond “VO boundaries”, some rigor is needed. Should be well-defined what is, and is not, covered or assured.
Who checks VO sw?
VO sw security, GDB 2015.01.1414 January 2015
![Page 9: Preliminary Conclusions VO Box Task Force GDB Meeting 5 april 2006.](https://reader036.fdocuments.in/reader036/viewer/2022083008/56649ed25503460f94be1b72/html5/thumbnails/9.jpg)
J. TemplonNikhefAmsterdamPhysics Data Processing Group
Discussion about dropping glexec et al and mapping all VO activities at site to a single “VO user” since “the VO knows who the real users are”
If VOs distribute vulnerable software providing network services, can we really trust them to handle all user traceability?
Suggest any new services requiring substantial trust at site level be audited.
Moving Traceability to VO
VO sw security, GDB 2015.01.1414 January 2015