Tag Info

New answers tagged

0

Even if the web server is compromised, the credentials used to connect to SQL Server would not be compromised, if you use what's called a Trusted Connection, and this is recommended. Basically that means you set up your Application Pool in IIS to run as a particular user, let's call it "IISUser". Then you give IISUser the minimum set of permissions to SQL ...


0

You could, if you want to do extra amounts of work, have an intermediate middleware layer that brokers requests from the dmz web server. It could be as simple as a rest based api ( it might not be simple :) ). Once again the amount of work is dependent on the monetary loss associated with the data. Also if you approach this from a programming perspective, ...


1

I will post an alternate solution to the one that is proposed in MSDN's "Granting Row Level permissions in SQL Server": https://msdn.microsoft.com/en-us/library/bb669076%28v=vs.110%29.aspx. In my solution, you have a meta table for each table where row level permissions are required. I like to call that meta table as an ACL (Access Control List) table. So ...


0

You need something called dynamic data masking. The company I work for, Axiomatics (disclaimer - I work for that company), has a policy-driven solution that achieves data filtering and masking. It means that based on policies and attributes, it is possible to define what a user can SELECT / INSERT / DELETE ... The way it works is that you define a policy ...



Top 50 recent answers are included