Larry G. Wlosinski is a senior associate at Veris Group.
WordPress is a free and open source content management system used by more than 23.3 percent of the top 10 million websites, according to Wikipedia, and itâ€™s also the most popular blogging system in use, with more than 60 million websites.
WordPress has been around since May 2003Â and has over 37,000 plugins. Its applications are accessible online and via mobile devices, allowing for many paths to compromise. Securing WordPress should be a top priority because of the large number of applications, the number of organizations that use it, the lack of security awareness of some users and developers, and weak security practices. Â
Weak or nonexistent security practices include outdated sites and software components, unsupported systems (i.e., patching of operating system, application softwareÂ and its components), poor database and server configurations, and abandoned sites.
The compromised sites can and have been used as launching points for virus and drive-by attacks, a window into your network systems and the data, and a place for misuse. Depending on the template, pluginÂ and system architecture, a WordPress website can not only be the source of a Denial of Service attack, but also a means to obtain sensitive, private, proprietary and personal information on your organization and staff.
As of April 2015, WordPress has 194 unique vulnerabilities and 21 known exploits, according to theÂ Common Vulnerabilities and Exposure database. Weaknesses in the programs, supporting templatesÂ and plugins can increase the business risk at the organization, mission/businessÂ and information system levels. Â
Recovery from an attack could affect your network, your systems and the data. If the data is sensitive or personal, there would be additional ramifications because of government regulations regarding health and personally identifiable information. Reporting and responding to data breaches and information spillage can be costly and have severe repercussions.
The mitigations needed to secure a WordPress system (application and/or blog) and fortify it from attacks are many. They address technical, policy and procedural changes. Administrators will need to continue due diligence on a continual basis to update WordPress based on new vulnerabilities posted by the National Vulnerability Database and other sources. Recommended mitigations include:
- Backups.Â Make regular backups of site files and databases.
- Working environment.Â Secure the admin folder by limiting the IP addresses that can access it, change the name of the admin account, and track number of attempts to use it.
- Sensitive Files.Â Lock down access to the wp-config.php file as it contains sensitive data, and encrypt cookies to protect against cookie hijacking.
- Access.Â Use strong passwords, implement least privilege to WordPress files and folders, and use encrypted SSL connections on admin related pages and functions.
- Configuration.Â Change default database table prefix from default settings, and hide the version information to reduce the information hackers use.
- Need to know. Limit search engine indexing spiders to only relevant files and folders on the domain.
- Testing.Â Perform IVV in a separate development environment prior to production implementation.
- Continuous monitoring.Â Keep the software upÂ toÂ date, patch regularlyÂ and monitor for problems daily by running scans and subscribing to security alerting organizations.
- Checklists. UseÂ a security checklist to aid in fortifying the system design, access controls, configuration, maintenanceÂ and operation.
- Tools. Use tools that harden the hosting, working environment, access, configuration management, maintenanceÂ and operations areas.
All of these actions are critical in reducing the likelihood of system and network compromises.
WordPress developers need to use the many websites that provide security guidance to prevent compromise and data spillage as well as resolve problems. A simple search on the Internet can yield information on WordPress issues with workarounds. Common errors, vulnerabilities, exploits with troubleshooting tips and solutions, â€œhow toâ€ instructions and guidance can also be found to aid programmers in system coding and development as well as resolving operational issues. For more in-depth information, you can also order books on these subjects. Â
Donâ€™t be caught in a net of malicious activity.Â WordPress developers and users need to implement best practices in development and preventative controlsÂ and be ever vigilant to prevent problems that affect their system and, ultimately, their organization.
(Image via GongTo/ Shutterstock.com)
Article source: http://www.nextgov.com/technology-news/tech-insider/2015/06/how-secure-wordpress-10-steps/114226/