I am using DO Droplets for use in my thesis experiments. I was wondering if DO implements DNS blacklists (either opensource or other) to stop outgoing HTTP requests to known malicious web servers. Additionally, does DO use any IDS to stop incoming traffic from known malicious websites? Or are these responsibilities on the user to implement to protect from malicious traffic?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These 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.
Click below to sign up and get $200 of credit to try our products over 60 days!
DigitalOcean will not generally stop any outgoing requests from your droplet. If there is a violation or malicious activity our support team will get in touch with you.
As for incoming traffic there are Firewalls which can block severe malicious traffic, but you also use the Cloud Firewalls product to stop traffic on network level.
The DigitalOcean Cloud Firewalls, are network-based and stop traffic at the network layer before it reaches the server.
This means that you could close specific ports like the SSH port or your MySQL port, or you could block specific IP addresses or ranges.
That way the network traffic is filtered on the firewall before it even reaches your Droplet.
However, you can not block specific HTTP requests, and for that, you need an application-level firewall that is able to filter the incoming packets based on specific rules.
Hope that this helps!
I don’t think DigitalOcean has any such blocks on your Droplet. They might block some heavy traffic coming from IPs for a period but I don’t know of a Firewall or firewall rules that block any resources, especially on customer’s Droplets.