Computer host names - recommendations
From: Mike Thomas (r53804@email.sps.mot.com)Date: 03/09/02
- Previous message: Security Alert: "Sec. Vulnerability in SNMP (rev. 5)"
- Next in thread: Ole Michaelsen: "Re: Computer host names - recommendations"
- Reply: Ole Michaelsen: "Re: Computer host names - recommendations"
- Reply: trbakker@xs4all.nl: "Re: Computer host names - recommendations - trinityos-c.tar.gz (0/1)"
- Reply: R. DuFresne: "Re: Computer host names - recommendations"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Mike Thomas" <r53804@email.sps.mot.com> Date: Fri, 8 Mar 2002 17:12:13 -0700
I've been searching for some guidelines/recommendations on hostnames. One
of my peers is suggesting that all systems be identified with a hostname
which would include whether the system is a server and the function of the
system, along with the physical location. Does anyone know of any white
papers or security guidelines on this topic? My first thought was that I
didn't know if it was a good idea to identify all of your critical systems
via their names. The counter-argument was that these are all internal and
won't be seen on the internet. Then, of course, there is the infinite joy
in entering "snisaz34-0012" whenever one wishes to telnet to a particular
system, in this case a NIS server at an Arizona location. I guess this is a
common practice in really large enterprise IT environments?
Thoughts? Opinions? Links to well-reasoned papers?
Thanx,
Mike Thomas
- Previous message: Security Alert: "Sec. Vulnerability in SNMP (rev. 5)"
- Next in thread: Ole Michaelsen: "Re: Computer host names - recommendations"
- Reply: Ole Michaelsen: "Re: Computer host names - recommendations"
- Reply: trbakker@xs4all.nl: "Re: Computer host names - recommendations - trinityos-c.tar.gz (0/1)"
- Reply: R. DuFresne: "Re: Computer host names - recommendations"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|