Windows SQL Server Authentication Security

We have an application that uses Windows authentication to authenticate users with a database, and SQL Server user accounts must have some read / write access to the database tables.

The problem is that users can then install SQL Server Management Studio and potentially use the database so that it is not used, but that’s not what I want.

All that I read suggests that using integrated authentication is more secure, but at the moment, any user can use Management Studio or Access / Excel only to connect to the database.

I read the question SQL Server Authentication or Integrated Security? which offers some workarounds, but I don’t have the ability to change the application as dramatically as refactoring all stored procedures, etc., so I was hoping there might be another option?

Thank,

Nico

+3
source share
2 answers

All I read says using integrated authentication is more secure

-> This is more secure because it is more difficult to get a password.

SQL Server, . , ( ), .
, Windows, "Integrated Security = True", Windows, , - Windows .

, Windows , , , .

, :

, . ,

, , , , :

  • SQL Windows
    ( - , , ... , Windows !)
  • ( ) , . .
    - > SP ( ... SP ), , .
+2

, , .

, , - ( - -), , ..

0

Source: https://habr.com/ru/post/1783666/


All Articles