Securing your Magento sitePradip Shah
Owning a Magento website means you have a resource you own and control on the internet. Keeping it secure in all aspects is a responsibility. You need to ensure
- your business data is secure.
- your customer data and privacy is secured.
- your customer’s computers are protected when accessing your website.
It is not required to be a famous to be in the eyes of the attacker – most attackers today prowl the internet looking for vulnerable sites and automatically get to work. New types of attacks are being designed and hence keeping a site protected is a continuous battle.
As a person ultimately responsible for your website, you need to periodically review your security processes and see they are enhanced for new vulnerabilities.
This article has an overview of the aspects of security you need to worry about. In addition it goes in depth as well to make it actionable.
Aspects of security infrastructure for a Magento Website
- Protection of the web edge infrastructure. Ensure you keep the bad guys out and the good guys in. Using a Web Application Firewall (WAF) with appropriate configuration will help.
- Server protection. Ensure access to the server restricted, preferrably without a password, limit port access and protect files and folders with permissions that are just needed. Also ensure the server has the latest security patches installed. Need to know access should enforced. Code updates should be automated. A staging site should be used for updates from vendors. Plugins should be acquired from known and reputable vendors.
- Code protection. Ensure your code is patched with the latest Magento (or any platform and plugins). In addition train developers to use safe practices to not leave holes.
- User data protection in transit. Ensure https access to the entire site so all access is secured against in transit hacking as users use your website. Ensure all admin access is restricted either with dual password or two factor authentication or IP restricted.
- Review all access periodically Change passwords and admin URLs regularly.
- Run vulnerability scanners Vulnerability scanners are available for testing many aspects of security. Blackbox scanners such as Trustwave, Secure Works, help in checking if they can find external vulnerabilities. Static analyzers such as Fortify scan the code to find code level vulnerabilities.
Protecting Web Edge Infrastructure
The key role of this protection is to keep the bad guys out and allow the traffic you want in.
As with any protection of this nature, detecting bad is a key. OWASP is an online community which has come up with a core rule set (CRS). A Magento site needs a WAF protection either on the nginx server level or with an external service such as Webscale Networks.
The OWASP ModSecurity Core Rule Set (CRS) provide protections against the following category of attacks.
- SQL Injection (SQLi)
- Cross Site Scripting (XSS)
- Local File Inclusion (LFI)
- Remote File Inclusion (RFI)
- Remote Code Execution (RCE)
- PHP Code Injection
- HTTP Protocol Violations
- Session Fixation
- Scanner Detection
- Metadata/Error Leakages
- Project Honey Pot Blacklist
- GeoIP Country Blocking
A hacked or broken in server – popularly shown in movies – gives access to your server to the hacker. Web prowlers are continuously trying to see what ports are open in the server and what access they can get. Being a very traditional form of hacking, it is highly automated. By the very same count, protecting a linux server is not very difficult either. Follow some guidelines and review process.
- Keep only known ports open and limit which IPs can access these ports
- Disable any form of password access
- Keep server patched with latest security patches
- Run only services that you need. For example never run ftp as it gives password based access to the server.
- Follow very strict rules on file / folder permissions as well as linux groups and users
- Periodically scan servers for viruses signatures
- Periodically review access keys
- Automate routine processes and restrict with keys including code update
- If a db server is a separate server further restrict access to this server . If using a autoscale architecture, further restrict access to app servers as well.
- Allow no exceptions – even for a critical fix
The following system admin note has technical details for linux system administrators to execute the strategies above
Protect your code
- Ensure Magento code is patched to the latest. Subscribe to Magento updates and setup process to check for patch releases on a monthly basis.
- When the plugin vendor. Many simple looking community plugins can be weak on security and leave the site prone to attacks.
- Train developers to use safe practices.
- Keep the code repository (svn / git) access secure and passwordless for developer access.
- Ensure external respository provider web access is secure and with 2-factor authentication.
- Ensure backup servers are protected with access to write only given to automatic backup process
User Data Protection in Transit
Customer data in transit is the protection of data sent and received from your website to their browser. Internet connections to websites are not direct – the data hops from server to server in between. A server compromised on the way can tap into your data without anyone knowing it.
- Using https for the complete site is an obvious requirement. Using higher security options in https is even better.
- Emails sent should not contain sensitive data. A recent Magento patch fixed such an issue – passwords were earlier sent in emails.
Review all access periodically
Setup a security task force that reviews and reports on security once a month.
The charter of the task force would be evaluate the following
- Who has access the the server and do they yet require this access. The access may be via keys and when a employee or contractor leaves, the key should be removed
- Who has access to development environment. Have required access been withdrawn appropriately.
- Who has access to version control systems. Have required access been withdrawn appropriately.
- Admin access Are all admin users yet needing access?
- Were admin passwords reset at agreed frequency?
- Magento Patch status
- OS patch and update status
- External security scan (if arranged) status
- Action taken report for the last period on any security issues
- Backup and restore process review to ensure data and code is appropriately backed up