Re: Locking Down Enterprise Manager...

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mark Allison (marka_at_no.tinned.meat.mvps.org)
Date: 09/02/04


Date: Thu, 02 Sep 2004 10:10:48 +0100

rathael1,

You could create your own application built on top of SQL-DMO which
would only provide the functionality you want your users to see. EM is
built mostly on top of SQL-DMO. There's no way to lock down EM itself -
it has to be done at the database server.

--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
rathael1 wrote:
> Mark,
> 
> Thanks for your reply. I realize I can set perms on the db's to secure data. 
> However, I am looking for a way to secure the actual client (EM), so that 
> users cannot even browse the different areas of EM. Even though they may not 
> be able to access data, I don't even want them to have visibility to certain 
> parts of EM. For example, I can create a regular user, grant it permission 
> only to databaseXYZ....and if I register EM with the same user account, I 
> will be able to see a listing of all DB's on the server. 
> 
> Any ideas on this? I haven't found any way so far to do this within the 
> actual client, so I'm open to suggestions that involve 3rd party solutions, 
> etc.
> 
> JD, MCSE, MCDBA
> 
> "Mark Allison" wrote:
> 
> 
>>rathael1,
>>
>>Enterprise Manager is just a GUI onto the database server. Permissions 
>>are set at the database server, not at the GUI, which is a client. Grant 
>>permissions in your databases according to what the users need to do, 
>>and no more. In other words only grant access to the things that they need.
>>
>>Look at the section in Books Online entitled "Managing Security" - it is 
>>a fairly big topic and is worth studying.
>>
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602.html
>>
>>
>>rathael1 wrote:
>>
>>>I am looking for any information on locking down EM, such as not allowing 
>>>access to certain areas (Security Folder, Management, etc), as well as 
>>>securing it so that they cannot even see certain DB's in the Databases 
>>>Folder. The security would ideally be tied into their SQL acct info, but NT 
>>>perms would work as well. 
>>>
>>>Can anyone provide some good primer info on this topic? Any hints or advice 
>>>would be greatly appreciated.
>>


Relevant Pages

  • Re: SQL or Access DB
    ... As far as encryption goes though... ... with Sql Server you can use SQL DMO and encrypt your stored procedures ... installation - Security was absolutely critical and in most instances, ... > then we create a nice gui around this database and sell it to automotive ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Is there any way to prevent hacker trying to guess sa password?
    ... and port 1433 will not be open. ... If someone can crash SQL Server by connecting to port 1433, ... You don't need multiple security experts. ...
    (microsoft.public.sqlserver.security)
  • Re: Getting to the bottom of MSDE network connection problems ...
    ... Brilliant, Nick, especially the explanation for local network user being ... authenticated as GUEST in WinXP SP2. ... > on a desktop OS like XP (meaning that, you can not compare SQL Server ... > again and selected the security tab. ...
    (microsoft.public.sqlserver.msde)
  • [NT] SQL Extended Procedure Functions Contain Unchecked Buffers
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... SQL Server 7.0 and 2000 provide extended stored procedures, ... Several of the Microsoft-provided extended stored procedures have been ... Exploiting the flaw could enable an attacker to either cause the SQL ...
    (Securiteam)
  • RE: Login failed for user (null).
    ... used at signon to authenticate in SQL Server. ... connect the remote SQL Server database), is there any other data accessing ... What's the security identity used to access the remote SQL Server, ... the worker process identity. ...
    (microsoft.public.dotnet.framework.aspnet.security)