|
| 1 | +--- |
| 2 | +meta: |
| 3 | + title: Understanding security measures on a shared hosting |
| 4 | + description: This page helps you understand security measures on a shared hosting platform. |
| 5 | +content: |
| 6 | + h1: Understanding security measures on a shared hosting |
| 7 | + paragraph: This page helps you understand security measures on a shared hosting platform. |
| 8 | +tags: webhosting cpanel security-practices |
| 9 | +dates: |
| 10 | + validation: 2025-06-30 |
| 11 | + posted: 2025-06-30 |
| 12 | +categories: |
| 13 | + - webhosting |
| 14 | +--- |
| 15 | + |
| 16 | +Your Web Hosting plan is on a shared server, meaning multiple websites are hosted on the same physical machine. While we have strong protections in place to isolate client environments, you are still responsible for some configurations. |
| 17 | + |
| 18 | +This page teaches you about security best practices and how to secure your space properly. |
| 19 | + |
| 20 | +## General best practices |
| 21 | + |
| 22 | +- Choose a strong password for your account and update it regularly |
| 23 | +- Use unique usernames and passwords for each account and service |
| 24 | +- Back up your data manually or using the backup hosting option to prevent loss in case of technical issues |
| 25 | +- Use the security features provided by your control panel, such as SSL/TLS certificates |
| 26 | +- Keep your software and plugins up-to-date for the highest level of security |
| 27 | +- Enable the two-factor authentication feature provided by cPanel |
| 28 | +- Limit access to files and databases to prevent abuses |
| 29 | +- Contact our support team if you have any questions or issues |
| 30 | + |
| 31 | +## Dedicated IP addresses |
| 32 | + |
| 33 | +By default, your hosting plan uses a shared IP address, meaning that the same IP is used by multiple clients on the same server. In case of abuse (if another client sends spam, for example), the shared IP can be blacklisted by other providers, which can block all data coming from the server, thus preventing outgoing mail from being sent. |
| 34 | + |
| 35 | +To avoid this, Scaleway offers a dedicated IP option: |
| 36 | + |
| 37 | +- You get a unique IP address used only by your hosting |
| 38 | +- You control your own reputation (especially for email delivery) |
| 39 | + |
| 40 | +## File and folder permission settings |
| 41 | + |
| 42 | +You can also keep your website secure by correctly setting file and folder permissions. |
| 43 | + |
| 44 | +### Standard files |
| 45 | + |
| 46 | +File permissions for files such as HTML, CSS, JavaScript, images, etc. should all be set to `644`. A permission of `644` means that the owner of the file will read and write permissions, while other users will only have read permissions. |
| 47 | + |
| 48 | +### Folders |
| 49 | + |
| 50 | +Permissions for folders should be set at `755`, meaning that the owner of the file has every right on the folder, while other users can only read and execute the folder but not alter it. |
| 51 | + |
| 52 | +### Sensitive files |
| 53 | + |
| 54 | +Sensitive files such as configuration files (`.env` files, or `wp-config.php` files for WordPress) should only be accessible by the owner. As such, they should be set to permissions `600`. |
| 55 | + |
| 56 | +### PHP scripts |
| 57 | + |
| 58 | +It is recommended to set PHP scripts to the `755` permissions. In some cases, `744` can be used to restrict execution to the owner of the script only. |
| 59 | + |
| 60 | +<Message type="note"> |
| 61 | + It is essential to review these permissions regularly to make sure that your hosting is not accessible to other users, and has not been compromised. |
| 62 | +</Message> |
0 commit comments