RE: DOD security
- From: "Mohan, Ross" <RMohan@xxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 6 Jul 2005 17:06:17 -0000
FGAC (fine-grained access control. same/better thing. you'll need to code a
bunch
of pl/sql packages to re-jigger WHERE clauses based on security.
it's definitely a full time job for a person for at least a week (for a
production
toy database) to months or seasons (for a real one) .
Good luck, and God Bless the Security Weasels for providing this work.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Tanel Põder
Sent: Wednesday, July 06, 2005 12:46 PM
To: ORACLE-L
Subject: Re: DOD security
Hi,
I think you can use Label Security now, instead of Trusted Oracle..
Tanel.
----- Original Message -----
From: Goulet, Dick <mailto:DGoulet@xxxxxxxx>
To: rgramolini@xxxxxxxxxxxxxxx ; oracle-l
<mailto:oracle-l@xxxxxxxxxxxxx>
Sent: Wednesday, July 06, 2005 5:35 PM
Subject: RE: DOD security
Ruth,
It has been a LONG time since I was involved with a project
like this and even then we were using a "special" version of Oracle called
Trusted Oracle. Don't know if it's available anymore. Anyhow it was a project
for Strategic Air Command, now Air Combat Command, that was very classified.
The Trusted Oracle had provisions in it to declare data at the row and column
levels as having a classification of Top Secret, Secret, Confidential,
Restricted, and Unclassified. People also had security attached to them. It
was kinda interesting as you'd select data from a table and rows and columns
would
Other related posts:
