Re: Security question ..
From: Bob Castleman (nomail_at_here)
Date: 12/10/04
- Next message: John Steen: "Re: Error 22029 on Maintenance Plan"
- Previous message: David Gugick: "Re: Failed to verify"
- In reply to: JXStern: "Re: Security question .."
- Next in thread: REMOVE_BEFORE_REPLYING_dportas_at_acm.org: "Re: Security question .."
- Reply: REMOVE_BEFORE_REPLYING_dportas_at_acm.org: "Re: Security question .."
- Reply: Maury Markowitz: "Re: Security question .."
- Reply: JXStern: "Re: Security question .."
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 10 Dec 2004 14:20:56 -0500
Using just roles is not sufficient. Part of this is related to Sarbanes
Oxley. For instance, if I give somebody read/write access to a table via a
role and they are able to create an ODBC connection to the database via
something other than our app, they will inherit the role and be able to make
modifcations outside of the audit trail provided by any business rules
imbedded in the application. This is precisely the type of thing a SOX audit
is going to red flag. As I stated above, all of this is partly answered by
the appropriate architecture. Unfortunately our app is a simple 2 tier with
the front end connecting directly to the database, lots of dynamic sql, no
stored procedures or views, etc.
So much work and so little time :(
"JXStern" <JXSternChangeX2R@gte.net> wrote in message
news:d0njr05vmnd72for6v2lon1hrb3ijitq8b@4ax.com...
> On Fri, 10 Dec 2004 10:33:14 -0500, "Bob Castleman" <nomail@here>
> wrote:
>>If you use NT authentication, a user's permissions to a database are
>>independant of an application that might act as the front end, correct?
>
> Correct.
>
> Now, you can still limit what those permissions are, but they will
> indeed be the same whether he logs in with the closed app or something
> like Access.
>
>>For
>>example, there is nothing to prevent a user from using MS Access to open a
>>connection and start "exploring". Is there any way to prevent this short
>>of
>>using SQL Authentication?
>
> What's wrong with SQL authentication?
>
> As someone suggested, maybe "application roles" are a good halfway
> point and will do what you need - one hard-coded password for the app.
> In fact, in general, maybe roles will be helpful for you.
>
> J.
>
- Next message: John Steen: "Re: Error 22029 on Maintenance Plan"
- Previous message: David Gugick: "Re: Failed to verify"
- In reply to: JXStern: "Re: Security question .."
- Next in thread: REMOVE_BEFORE_REPLYING_dportas_at_acm.org: "Re: Security question .."
- Reply: REMOVE_BEFORE_REPLYING_dportas_at_acm.org: "Re: Security question .."
- Reply: Maury Markowitz: "Re: Security question .."
- Reply: JXStern: "Re: Security question .."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|