I was hoping a quick google search of MS's site would yield the answer from on high (as managers see it anyways) and instead I got this :
"Note The "Physical Security" item in the following graphic does not have a corresponding section in this chapter recommending resources on the topic; Microsoft has not yet published detailed guidance on this subject. "
from their Security Risk Management Guide.
But, for some ammo for you here is a quote from the exchange 2k3 planning guide:
"Security The physical security of servers in branch offices is a major consideration. In a branch office design, you must take precautions to ensure that servers are not located in open areas and that they are physically secured. "
http://www.microsoft.com/technet/prodtechnol/exchange/guides/PlanE2k3MsgSys/9c9e0367-4032-47be-b334-bf3fed9ea539.mspx?mfr=true
| Larry Wahlers <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 06/28/2006 10:29 AM
|
|
I am being asked to install a single server in a remote location (about
20 miles from here, 20 users) that will be a DC for our entire network,
running DHCP and DNS, acting as a file server and print server for this
remote location. And, this server will be in an unlocked rack in a
semi-public area where literally anyone could gain physical access to
the box. At the very least, the 20 employees will be walking past it
every day.
There are many red flags about this scenario. I can think of a few. But,
what I need is documentation from an *external* source that tells
management just how bad an idea this is. After all, they won't believe
me, but they might believe an "expert."
At the very least, I would want the rack in which this server is placed
to be locked 24/7. Better would be a locked room.
All help welcomed with many thanks.
--
Larry Wahlers
Concordia Technologies
The Lutheran Church - Missouri Synod
mailto:[EMAIL PROTECTED]
direct office line: (314) 996-1876
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx
