May 2, 2008 at 7:06 am
Lets assume SQL Server 2005 running on Windows 2003 Server, connected to the network but not part of the domain. One application accesses it over the network with one login. Either SQL Server or a local windows login is used for authentication. This would protect SQL Server if the domain was compromised. I can see in normal circumstances domain level logins should be used, but in certain scenerios where the security of the SQL Server box is top would this be a good solution?
Thanks
Danny
May 2, 2008 at 8:14 am
So the machine is not part of the domain. I'm not sure it's more or less secure than being on the domain. The same type of security is used to authenticate in either case and can be broken.
Why do you not want it on the domain? Is there some reason your password is more secure? Do you now trust the domain admins?
May 2, 2008 at 9:09 am
I am only talking hypothetically. Lets assume a domain controller has been compromised. A domain admin could then access the SQL box. If the SQL box was not part of the domain then it would not be compromised in this situation.
Danny
May 2, 2008 at 9:17 am
Danny (5/2/2008)
I am only talking hypothetically. Lets assume a domain controller has been compromised. A domain admin could then access the SQL box. If the SQL box was not part of the domain then it would not be compromised in this situation.Danny
Sure a domain admin could get to the box and stop services, but, if you have removed/downgraded the Builtin\Administrators group the Domain Admin would not have elevated privileges within SQL Server which should protect your data.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 2, 2008 at 9:42 am
Unless he knows enough about SQL to start it in single user mode.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 2, 2008 at 9:52 am
True, but if your domain is compromised you have problems in every area not just SQL Server and while SQL Server holds your data at least you should have backups off-site than can somewhat help you recover the SQL Server(s) AFTER you have recovered all your servers from the damage done to them.
Also you'd know pretty quickly that someone had changed that when users complain that the "system is down" and you could pull the network cable from the SQL Server. Granted damage might already be done, but as I said above, you and\or your network admins will be busy recovering from other issues I think.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply