.net - Recognize application connected to SQL Server 2005 -
I should know which application is connected to DB and execution of SP.
(I want to limit the execution of SP only my app - all others - for example MS SSMS will be ignored)
So, is there a way to detect associated client names?
If you do not have other suggestions to make sure that only dedicated app is used (the app is using Windows' integrated security)
Edit: Which problem I'm trying to solve:
I'm working on the app made in the user's right & amp; Roles module Therefore, the app receives all areas from DB (SP) and it is decided by commercial logic to show which user (or not)
I am afraid of a more experienced user: He can run his own app, connect to DB and leave all security restrictions.
This is the reason why I want to ensure only DB conversations with this app.
The only thing that can be authenticated on Windows is the user is not a secure method to establish an identity for application As a result, any effort to restrict access to a specific application is sufficiently inspired by the attacker. May be defeated by.
You can keep an accidental login honestly by adding in the trigger you can see the "Name of the app" declared by the connection string and can not close the connection. This could prevent someone accidentally connecting to your server. However, it can not prevent an inspired administrator from accessing the data, because the name of the app can be tricked. In addition, if you have administrative and maintenance tasks of any type, administrators and maintenance tasks will require access to your database.
A little better way to control access through data. One approach enables you to apply for this app, you still have to compute your content management restrictions ('column' restrictions and others you quote). Will use your custom application logic for. This will progress a bit so that only you can modify and access your application data. This will stop the non-administrator from accessing your data, but will be a privileged administrator ( always ), he can do whatever he wants.
And finally the higher bar than the deployment of an encryption. To get this done, a fixed administrator actually takes it and it takes an administrator who needs to take specific steps to find your key password, they can not accidentally search as I said, a dedicated administrator will always Will be able to access the data.
No alternative is to deploy any obstacle, rather it is to use auditing to monitor the data. Clear auditing can be done in the compromised SQL Server and audit can usually do a strong enough deterrent advertisement.
Comments
Post a Comment