Re: RC separation of duty

From: ao@morpork.shnet.org (A. Ott)
Subject: Re: RC separation of duty
Date: 30 Oct 1999 14:10:00 +0200

Next Article (by Date): Re: RC separation of duty ao@morpork.shnet.org (A. Ott)
Previous Article (by Date): Re: RC separation of duty "Paul D. Robertson"
Top of Thread: RC separation of duty ao@morpork.shnet.org (A. Ott)
Next in Thread: Re: RC separation of duty ao@morpork.shnet.org (A. Ott)
Articles sorted by: [Date] [Author] [Subject]

********* ***************** ********** ****  *****   ***** ************
  To subject Re: RC separation of duty
  proberts@clark.net (Paul D. Robertson)  wrote:
********** ******************** ******  ********  ******* *************

> I'm in the process of building some HTTP proxy servers for WAN access.
> Being the paranoid type, I don't want unfettered WAN access to my main
> corporate site from distant locations.  Our infrastructure is such that
> the people who should manage the machines don't have a great deal of
> experience outside of Win*.  Rather than taking calls and doing routine
> things like adding new support admins I'll be able to delegate the
> administration tasks, and now even delegation itself as time goes on and the
> lower layers of support gain more clue.  Phase II of this project just
> instantly gained "add RSBAC" to its feature list.  Actually for the
> corporate side proxies it may squeak into Phase I.

So you will probably be the first one to use the separation of duty  
features. I'd like to get lots of ideas for improvement, practical  
experiences, etc.

The whole concept just evolved in my head to be something that might work,  
but I am not yet sure about all the consequences.

Amon.

--
Please remove second ao for E-Mail reply - no spam please!
## CrossPoint v3.11 ##
-
To unsubscribe from the rsbac list, send a mail to
majordomo@morpork.shnet.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.