[AG-TECH] AG Security

[Nolan, Kevin [NCSUS]]

Just to give you some insight - this is one of our biggest concerns.  We
have two types of AG setup's -

1) the open setup to communicate with the AG audience
2) Secure encrypted communication between our location using J&J multicast
address over tunnels.  It has taken us about 6 months to make it work - but
we now have the ability to have secure connections for J&J and un-secure
connections with the AG community.  

-----Original Message-----
From: Allan Spale [mailto:aspale at evl.uic.edu] 
Sent: Thursday, July 18, 2002 2:24 PM
To: ag-tech at mcs.anl.gov
Subject: [AG-TECH] AG Security


Hello,

One of the questions today that I received during my presentation about the
Access Grid concerned security.  Specifically, how can one guarantee that no
one can eavesdrop (video and/or audio) on an AG session.  I am somewhat
aware about the Secure Room and its purpose, but what other options are
there?  When I described this process, my explanation made this process of
reserving this room seem cumbersome (i.e. having to specifically request use
of the Secure Room as opposed to reserving a non-secure venue).

The other idea I thought about was setting up an instituition-level venues
server (Virtual Venues server software).  If this was done, what assurances
would there be to keep people from eavesdroping on the internal session. 

Taking this one step further, if there were shared applications used during
a session (and I do not think exposing DPPT data streams would really
matter, but for the sake of argument), it is more of the writers of the
applications to provide their own security mechanism to assure that the data
streams are secured?

I would appreciate any people sharing their information with me.  In this
way, I can help address the security issue in a much better manner in any
future AG presentation.  Thanks.


Allan
EVL at UIC
node-op

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20020718/bfe39f6a/attachment-0001.htm>