2 ms·
Still, you're exposing your infrastructure. It's kind of nice to know that there is a mongo1.profiles.company.com somewhere.
by jbverschoor 5y ago
Still, you're exposing your infrastructure.
It's kind of nice to know that there is a mongo1.profiles.company.com somewhere.
- Hamuko 5y agoYou can just obfuscate your names if you really need to keep it hidden. profiles.company.com? coffee.company.com. mail.company.com? tomato.company.com. passwords.company.com? tincan.company.com. If you're really paranoid, you can just flood a bunch of misdirects in there as well. If you need 10 internal subdomains, add 100 subdomains with random CNAMEs.
- aaomidi 5y agoYou can use wildcard certificates so you're not exposing any infrastructure. Also, you should really consider all your subdomains to not be private information. It's risky to build security based around that assumption. Tons of DNS services actually sell their queries, and those can be used to reconstruct these "private" subdomains.
- pixl97 5y agoWith this said, wildcards are massive security risks in themselves when devices start getting compromised. You can then chain together things like DNS poisoning and arp attacks to MITM further devices on the network. And confirming what you said. DNS leaks everywhere, so don't consider its obscurity a form of security.