Re: Server naming conventions

[Andreas Paulisch <apaulisch () BROCKU CA>]

We use element names.. It was fun for a while.. but who want's to log into molybdenum?!  That was just way to much 
typing..  We actually ran out of "normal" element names.. So we went back to ad hoc.. For example, housing services has 
servers called "hut" and "hovel".... The DHCP server is called "gimme"....These days the emphasis is on short, 
memorable names.

------------------------------------------------------------
Andreas K. Paulisch
ITS Security Officer and Manager, Integrated System Support Group
Brock University
St. Catharines, ON L2S 3A1 Canada
E-Mail: andreas.paulisch () brocku ca<mailto:andreas.paulisch () brocku ca>
http://www.brocku.ca
Phone: 905-688-5550 x 5109
------------------------------------------------------------

From: The EDUCAUSE Security Constituent Group Listserv [mailto:SECURITY () LISTSERV EDUCAUSE EDU] On Behalf Of 
Woodruff, Daniel
Sent: Wednesday, February 10, 2010 2:17 PM
To: SECURITY () LISTSERV EDUCAUSE EDU
Subject: [SECURITY] Server naming conventions

What kinds of naming conventions do everyone follow when building new servers?

Currently, our Windows hosts are named following the pattern 'its-w2ks#' or similar, where the # is the next in the 
sequence, and the names are published in DNS. What are the potential drawbacks or using a scheme like this? Do you 
think it is any better or worse from a security perspective than using something like 'its-oracle-1' which has the 
service right in the name? We're concerned about disclosing the purpose of the machine via its name, and are trying to 
get an idea of what other schools do for their machines. Thanks in advance.

Dan Woodruff
University IT Security and Policy
University of Rochester

________________________________
Confidentiality Notice: This e-mail, including any attachments, may contain confidential or privileged information. If 
you are not the intended recipient, please notify the sender by e-mail and immediately delete this message and its 
contents. Thank you.