Timeline for Computer name naming convention for security
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2019 at 10:39 | comment | added | dr_ | "The fact that there is no readily available information to support your conclusion, should give you some idea about its validity." This. +1 | |
| Jul 5, 2019 at 10:17 | comment | added | Tim | My scheme is to use names of birds, like heron, egret, swan, magpie etc. The category of bird defines what type of device it is. | |
| Jul 5, 2019 at 6:35 | comment | added | reirab | @HagenvonEitzen Agreed. But I am of the same opinion as the two answers that the concern isn't really a valid one in the first place. :) What I described isn't really for security, but rather for making IT's life easier (I just mentioned it since the answer mentioned having difficulty remembering which Pi did what.) | |
| Jul 5, 2019 at 6:30 | comment | added | Hagen von Eitzen | @reirab Such a scheme is fine - but no help in the threat model in question, I suppose. An attacker looking for a mail vulnerability could look for mail.<domain> and couldn't care less if the "real" name was ganymed or chtulhu | |
| Jul 5, 2019 at 6:26 | comment | added | Hagen von Eitzen |
More often than I am happy with, I observe that www.companyname.com has a lot more ports open (and often interesting ones) than just 80 and 443. So if you conclude that it is "probably not the back end database" - this is actually a case of a slightly confusing-the-attacker hostname :)
|
|
| Jul 5, 2019 at 6:01 | comment | added | reirab | You can also do both - use some kind of themed name as the host name and then CNAME roles to it. Most of the servers to my university were set up that way when I was in undergrad. It was quite convenient in an environment where roles sometimes moved around between different servers. So, when a role changed, all we had to do was change the CNAME to point to the new server in charge of that role rather than needing to tell all of the clients to start connecting to a different hostname. Also, users neither had to know or care whether or not, say, mail.<domain> was the same box as www.<domain>. | |
| Jul 5, 2019 at 3:45 | comment | added | jwenting | a good example of a scheme that was obvious to those in the know yet hard to guess for the uninitiated I found at a former employer. All our servers were named after Nobel prize laureates, with different categories of servers taking names from different prizes (say (and this is just an example, don't remember what was actually in use) web servers got literature, database servers physics, application servers medicine). Much easier to remember to connect to Einstein than srv-12422A43D4327B | |
| Jul 4, 2019 at 20:33 | history | answered | Ljm Dullaart | CC BY-SA 4.0 |