Hi, I'd like to suggest a new feature to server owner's security, to block other domains visibility from whois services. at the moment, anyone can go to any whois service (i.e. http://reverseip.domaintools.com) and by typing domain name, or the IP address can check what other domains are hosted on this server. i think, to privacy of users and server owners, this is a lack. it may be just an additional feature, but i'm sure people would love to see this as an option to disable this from public view.

DDoS issues are getting out of control. It would be a good idea to integrate mod_evasive apache module to mitigate them.

I was suggested by the support team to mitigate the attack using app level firewalls but that's far to be an optimal solution.

They confirmed that the current infrastructure of their servers is not ready for adding this apache module but they are open to evaluating it as an option.

I made contact via suppot chat and ask if it was possible to install GoAccess on my server for a visual and accurate log view.
Since it was not possible all i can do is suggest to make a section on server panel to analyse server logs and have a clear vision of traffic and load.

Gabriel G.

PCI Compliance now regards weak ssh key exchange algorithms as a liability. There should be a way to disable them. It's fairly easy to set up in open-ssh: https://infosec.mozilla.org/guidelines/openssh#Configuration

IP whitelisted via Server > Security should also whitelist IP for Bot Protection on all apps. I have had to have support reps manually whitelist my client's IP when they were blocked by Bot Protection. I couldn't find their IP to be able to whitelist it. I want to be able to manually and globally whitelist an IP and it would make sense to tie it into the Server > Security whitelist option or if that is not possible, just an easy way to do it via Bot Protection settings.

Users can turn on two-factor authentification in their account.
But there is currently no way to see if the team members you have in your team have enabled it. It makes it impossible to enforce two-factor auth and poses a security risk.

Suggestion: Show "2FA enabled" next to team members that have enabled it on the Team page.

It would be great If I could change the login url of my wordpress site from website.com/wp-admin to website.com/my-custom-login-url in order to prevent unwanted brute-force login attempts.

SSL has rate limit for SSL certificates which is reset in 12hrs. This limit should be displayed on SSL page so that user can be careful.

Provide a way to disable the server signature to improve security by not disclosing the server type and server software, along with other information, which could allow hackers to determine vulnerabilities by listing server and software specifications.

Thanks!

The shellinabox service that runs on port 4200 is not secure enough, for a number of reasons:
* it accepts non-TLS traffic
* no multifactor authentication
* no battle-tested frontend webserver like nginx before it

Instead of fixing all of these, perhaps just allow to disable this service like you allow for other services.

If we have a multisite, we need a wildcard SSL for the subdomains. However if we go further, and provide custom domain (domain mapping) the problem comes that the SSL certificate is only for our domain not the mapped. Would be great if we can (even manually) create more than one certificate. SAN certificates is not the good option, since:

• We are using the wildcard for the own subdomains.
• There is a hard limit with the 100 domains.
• All the custom domains would be listed as secondary domains in the certificate details.

Please advise about specific measures did you take regarding Spectre and Meltdowns recent announced threats in order to give a word of trust to our final customers

Please make your cloud server SOC2 compliant.

Need to the ability to save IP ranges to security rather than one at a time.

Applications on the same server currently have write access to each others' files by default, which is an unnecessary security risk. For example, if you have multiple Wordpress applications on the same server and one gets compromised, the hacker could also compromise any other applications on the same server. If possible, it would be worthwhile to at least have the option to lock down file write access on a per application basis. I believe you already have apache running under separate users for each application, so this might be as simple as disabling the www-data group permissions.

Please could you find a way to keep up-to-date with Drupal core security updates (eg. current 7.38 has a critical security flaw). It's a PITA to get a security email immediately on install and have to go in and update. Isn't there a way to pull the latest secure core as part of your install process?

Thanks, Neil

Hi !

It would be interesting to be able to create groups of IPs and name or tag these IPs in order to visually understand who has been given access to MySQL/SSH services.

Example :

External company 1: 127.0.0.1 127.0.0.2 127.0.0.3
External company 2: 172.0.0.1 172.0.0.2
Freelance dev: 120.0.0.1
My company: Ips list ....

Thx