On convention that I developed at a former employer for mashine names 
consists of coding the diferent positions in the name with diferent 
meanings.

* Letters 1: Geographical location (city or main datacenter)
* Letters 2-4: Department or building
* Letters 5-6: OS
* Letters 7-8: Counter to ID individual mashines at the location.

You could probably invent something similar for your use.


On 2 Feb 00, at 15:18, Michael E. Cummins wrote:

> Security through obscurity may not be advisable as a primary defense, but it
> is an excellent philosophy to compliment your existing infrastructure.
> 
> Personally, I would try avoiding any practice that drew attention to my
> architecture to the casual observer.
> 
> I'm sure that you can come up with a naming scheme that seems a bit more
> arcane to those outside your company, and still have it make logical sense
> to you and your staff.  It will not obfuscate those who are more intimately
> familiar with your company's structure, but then again - if they are - you
> already have something to worry about anyway.
> 
> >     I am going through many network blocks this week, cleaning out PTR
> > entries for outdated systems and assigned blocks. I would like to update
> > most of the reverse records for the routers and gateway systems at the
> > same time. Do any of you have thoughts on proper naming conventions of
> > reverse records for gateways ? Could you see potential risks associated
> > with having the geographical location or organization name in the record
> > ? For instance, core-1.atm155.newark.example.com would give me information
> > regarding the importance of the router, the company name, the location,
> > and the type of link. Of course security through obscurity is NO SECURITY
> > at all, but ... any thoughts ?
> >
> > .truman.boyes.
> >
> >   /"\
> >   \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
> >    X  ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
> >   / \

I whole-heartedly favor this campaign. HTML mail is a waste of bandwith.
**********************************************************************
Mario L. Epp
E-Mail: [EMAIL PROTECTED]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]

Reply via email to