Re: Column Level Permissions Security Issue
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 8 Nov 2007 22:15:39 +0000 (UTC)
Ross Nornes (RossNornes@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
A standard SQL user is placed inside this role allowing them full read,
write, and execute rights on everything in the DB which is fine. BUT,
now we want those same rights except for the sensitive data files so I
updated the rule with the following script:
DENY SELECT ON [dbo].[TableNameHere] ([strCC]) TO [RWE]
Loggin in a developer and doing a SELECT * FROM TableNameHere throws a
permission error as expected, so far so good.
But, I did a SELECT * FROM ViewThatContainsField_strCC and shows them the
denied field. Oh, oh! I also did EXEC spProcThatShows_strCC and again it
shows the denied credit card field. Again, oh, oh.
Ownership chaining I suppose. That is, the procedure and the view are owned
by the same database user that owns the table. In such case the permissions
of the owner applies.
You could deny permission on the view column. You should probably deny
execution on procedures that disclose sensitive data as well.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: Column Level Permissions Security Issue
- From: Ross Nornes
- Re: Column Level Permissions Security Issue
- Prev by Date: Re: sa password
- Next by Date: guideline for service account user
- Previous by thread: Re: Error: 18488
- Next by thread: Re: Column Level Permissions Security Issue
- Index(es):
Relevant Pages
|
|