Auditing changes...By developers
- From: "Joseph" <josephsheppard@xxxxxxxxx>
- Date: 19 Mar 2007 16:25:28 -0700
What is the best way to go to track changes by developers that are
privy to db usernames and passwords?
Not all application users have domain accounts, so we can't use
trusted connections. Instead, we have a single username that the
application (we only have one) uses to perform its work.
We have auditing at the internal application level...Now we need a way
to determine if any of the four developers are possibly manipulating
data.
I briefly looked at application roles, but considering that you can
run sp_setapprole from the QA, that doesn't seem worthwhile.
How is everyone else doing it? Our auditors assure us it is being
done...
Don't you love SOX?
Thanks!
Joseph
.
- Follow-Ups:
- Re: Auditing changes...By developers
- From: K . Brian Kelley
- Re: Auditing changes...By developers
- From: Sue Hoegemeier
- Re: Auditing changes...By developers
- Prev by Date: Re: ALTER MASTER KEY REGENERATE Command
- Next by Date: Re: SQL2005 Linked server authentication problem
- Previous by thread: Re: ALTER MASTER KEY REGENERATE Command
- Next by thread: Re: Auditing changes...By developers
- Index(es):
Relevant Pages
|
|