Question
Private Network Security Policy
- Posted September 10, 2013
I’m very excited about the new private networking option. I have a couple questions:
- How is the private traffic protected from sniffing by droplets not run by me?
- Is it OK if I use nmap over the private network to analyze my own droplets?
Thanks for the hard work launching private networking!
Subscribe
Share
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sign in to AnswerThese answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Try DigitalOcean for free
Click below to sign up and get $100 of credit to try our products over 60 days!
@Neil: You can only use the IP address that is assigned to your droplet.
Can I use different IP addresses on the private network interfaces of my droplets ?
@gilkudik: See <a href=“https://www.digitalocean.com/community/articles/how-to-enable-digitalocean-private-networking-on-existing-droplets”>https://www.digitalocean.com/community/articles/how-to-enable-digitalocean-private-networking-on-existing-droplets</a>
How can I enable Private Network option in a deployed CentOS 6 x64 droplet?
<strong>* How is the private traffic protected from sniffing by droplets not run by me? </strong> <br>We filter traffic to prevent networks from leaking to a different droplet’s interface. However, we recommend that the users protect both public and private interfaces with iptables filters and use encryption where the data stored or transferred is sensitive.
<strong>* Is it OK if I use nmap over the private network to analyze my own droplets? </strong> <br>It’s allowed as long as it is not against the ToS. However if you cause any system issues your droplets will be throttled.