Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Deny SSMS Update Expand / Collapse
Author
Message
Posted Thursday, March 6, 2014 9:46 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:00 AM
Points: 179, Visits: 682
Hello,
Our setup uses Windows integrated security.

I would like someone to be able to update using the front end (.NET), but not if they use SSMS.

Is this possible without using "Execute As" for the front end? "Execute As" would be a massive undertaking.

Thank you,
djj55
Post #1548362
Posted Thursday, March 6, 2014 10:05 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Today @ 12:53 AM
Points: 785, Visits: 687
What is the architecture of the application? Web app? Three-tier with a separate application server? Or does the user run the application from his desktop and the application connects directly to SQL Server?

In the latter case, there is only one option: Terminal Server/Citrix + network segmenting.

If you have a two-tier app, and use EXECUTE AS or an application role, you cannot achieve security, because anythijg the app can do, the user can do from SSMS. So the only option is to keep the user out from SQL Server.

If you have three tiers there a few more options.


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1548369
Posted Thursday, March 6, 2014 10:13 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:00 AM
Points: 179, Visits: 682
Erland Sommarskog (3/6/2014)
What is the architecture of the application? Web app? Three-tier with a separate application server? Or does the user run the application from his desktop and the application connects directly to SQL Server?

In the latter case, there is only one option: Terminal Server/Citrix + network segmenting.

If you have a two-tier app, and use EXECUTE AS or an application role, you cannot achieve security, because anythijg the app can do, the user can do from SSMS. So the only option is to keep the user out from SQL Server.

If you have three tiers there a few more options.

Thank you. That was what I was afraid of as we use the desktop application connecting to SQL.
Post #1548374
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse