Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Logon Triggers As A Security Mechanism

user2728448Aug 5 2013 — edited Aug 6 2013

I’d like to get people's opinions on an idea that's been proposed by my organization's architecture team.

I work in a rapid development environment with an extensive database code base.  A good amount of DDL, Code Complication, and adhoc DML occurs on a weekly basis. 

Currently, we do not share database passwords with anyone.  Our process is far from optimal and the passwords can, at times, land in the hands of developers; but, for the most part, we do our best to keep the passwords secure. We have 20+ databases with 100+ applications and 400+ developers.

The proposed approach from the architecture team involves the sharing of database passwords with development teams, and the use of logon triggers as our security mechanism.  The logon trigger would allow the logon when it’s coming from an approved program/module & host, and would throw an error and block the logon for unapproved.

What’s your opinion of this proposal?  Has anyone ever seen the approach before?  If so, was it successful?

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 3 2013
Added on Aug 5 2013
13 comments
1,218 views