Enhanced password management
Magento has strengthened the hashing algorithms (SHA-256) used in password management.
Improved prevention of cross-site scripting (XSS) attacks by making escaped data the default
More flexible file system ownership and permissions
Starting in version 2.0.6, Magento no longer explicitly sets file system permissions. Instead, we recommend that certain files and directories be writable in a development environment and read-only in a production environment.
To provide you with a simple way to restrict access to the file system in production, we provide the flexibility for you to further restrict those permissions using a umask.
For an overview, see Overview of ownership and permissions.
For details about ownership and permissions in development and production, see Magento ownership and permissions in development and production.
Improved prevention of clickjacking exploits
Magento safeguards your store from clickjacking attacks by using an X-Frame-Options HTTP request header. For more information, see X-Frame-Options header.
Use of non-default Magento Admin URL
A simple Magento Admin
backend) makes it easy to target attacks on specific locations using automated password guessing. To prevent against this type of attack, Magento by default creates a random Admin URI when you install the product. The CLI command
bin/magento info:adminuri is provided so that you can see the URI if you forget it.
You can change this Admin URI in three ways:
bin/magento setup:config:set --backend-frontname=<value>command
- The Admin panel
Although the use of a non-default admin URL will not secure the site, its use will help prevent large-scale automated attacks. See Display or change the Admin URI in Configuration Guide for more information.