An introduction to Plesk Security Course: Part 1 [Video]
Have you seen our brand-new Plesk Security Course? It’s fresh in our Plesk University catalogue since Sept. 25 – and free for all our users. We figured we’ll help spring you forward so you can make your Plesk server the most secure it can be.
So let’s cover the basics. Here’s the first in a series of 3 quick videos that will bring you up to speed and achieve top security status for you and your customers.
The 3 security settings you need to adjust
Video: 1:17 minutes
What’s Going On in this Video
After installing Plesk, you need to do 3 important things:
1. Increase password strength
2. Restrict creation of DNS subzones
3. Enable prohibited domains list.
Increasing password strength
We recommend strong and very strong passwords. In this speedy guide, Plesk will help you and your customers create safer passwords with the right strength.
Restricting DNS subzones
We really believe preventing fraud and phishing should be one of our users’ top priorities. Follow the video to enable the DNS sunbzones restrictions. And this way, your customers won’t be able to create domains that look like subdomains of other customers’ domains. For example, if CustomerA owns example.com, CustomerB won’t be able to create store.example.com.
Enabling prohibited domains list
No matter your business or website ambitions, you will need to protect yourself against mail interception. What is this? Well some unscrupulous customer may be able to create a domain like gmail.com, microsoft.com or even your own domain (your-hosting.com) on Plesk. This sucks because from that point on, mail addressed to these kinds of domains will be delivered to your local domain, and not the real one.
That sums up what you need to do right after installing Plesk. Changing these settings won’t affect objects that already exist on the server, like domains, passwords, and so on. Ready to get started? There’s more in our Plesk Security Course
How useful was this post?
Click on a heart to rate it!
Average rating / 5. Vote count:
Oh no, sorry about that!
Let us know how we can do better below
Thanks for your feedback!