Online Services

Category: Security

  • WordPress Backups Are Critical to Your Security Strategy

    On this blog, we often talk about employing a “defense in depth” approach to WordPress security. The majority of our focus is on the prevention and detection features offered by the Wordfence plugin. Today we turn our attention to WordPress backups, an incredibly important remediation topic.

    Why Are WordPress Backups Important?

    WordPress BackupsIf your site is compromised, having access to backups can make your life considerably easier. The fastest way to recover from a hacked website is to restore the latest version of the site that existed prior to the hack. You will still need to close the security hole the attacker used to compromise your site after your site is back up and running, but at least you’ll have your site back to working order in hours or even minutes.

    Without a good backup on hand, you’ll need to either manually clean your hacked website or pay an expert to do it for you. Many companies provide site cleaning services, including Wordfence. Many of them are quite reasonably priced, but with the right backup service you should be able to avoid this expense altogether.

    In some cases, your site may become compromised due to issues that your hosting company is experiencing. In those cases, there is likely nothing you can do to protect your site, short of moving your website to a new hosting company. Having a good backup and the right backup service can make that transition much easier.

    In our post last year on the SEO impact of a hacked website, we showed that recovering slowly from a hacked website can have an adverse impact on your search engine rankings, organic search traffic and, ultimately, your sales. We determined that the average cost of a hacked website is $2,518. Recovering quickly can have a significant impact on minimizing the damage to your business, and backups can play a big role in that.

    Implementing a Security-focused WordPress Backup Strategy

    Before you implement a security-focused WordPress backup strategy, you’ll need to answer a few questions. Your approach will depend on the type of website(s) you manage, the technology platforms you are already using (including your hosting company) and how much effort and money you are willing to invest in your backup strategy.

    What Is Your Hosting Provider Already Doing?

    The first place to start with your backup strategy is to find out what your hosting provider already does automatically. You may find that your hosting provider doesn’t back up your site at all: many entry-level hosting plans only offer WordPress backups for an additional monthly fee. If they do offer backups, they may not back up all of your data, or they may not do so frequently enough, or keep it long enough or store it securely. In the large majority of cases, you are going to want to augment what your hosting provider is doing.

    What Should You Back Up?

    It is incredibly important to understand all of the files that you will need backed up to properly restore your website. At a minimum, you need to back up the files in your wp-content folder (themes, plugins and media uploads), WordPress config files, and your WordPress database. You may also want to back up WordPress core files, though you should be able to get fresh copies of those from the WordPress website when needed.

    How Often Should You Back Up Your Site?

    The frequency with which you should back up your WordPress site should be determined primarily by how often your content changes. Sites that change infrequently may be able to get by with weekly WordPress backups. Sites with constant updates, like new users, blog posts and comments may need to be backed up hourly. Many websites will be somewhere in between. The key question to ask yourself is: how much would it hurt to lose an hour of data? A day’s worth? A week’s worth?

    How Long Should You Retain WordPress Backups?

    To answer this question, you need two data points: how quickly do you think you will discover that your site has been hacked and how far back could you go back in time with a site restore and still have it be useful. Our site cleaning team unfortunately sees sites on a regular basis that had been hacked for as long as 6 months before the site owner noticed. The best way to answer this question for yourself is to think through the realities of each scenario. Would a 60-day-old backup of your site be useful, or does your site change often enough to need more frequent backups?

    However long you decide to retain your WordPress backups, it likely makes sense to keep more of the most recent files and fewer of the older ones. For example, for a mission-critical site, you might decide to keep 24 hours of hourly backups, 30 days of dailies, and six months of weekly files. A site owner with a relatively static website might decide to keep one week of daily backup files and six months of weekly files.

    In the case of a hacked website, the most recent backup created before your site was compromised is the one you want. Your backup strategy should seek to reduce the risk that you won’t have that backup available when you need it.

    Where Should You Store WordPress Backups?

    The key concepts to consider when deciding where to store your WordPress backup files are: access control, redundancy and independence. In addition, you probably have technology services such as AWS, Google and Dropbox that you are already using for other kinds of data storage. The ideal approach achieves your independence, access control and redundancy objectives while taking advantage of technology services and platforms you already have in place.

    Independence

    With regard to WordPress backups, the concept of independence simply means that you don’t want to rely on the same hardware, network or provider to store your backups that you use to host your website. With a compromised website, you don’t want the hackers to be able to simply delete your backups. In the case of a hosting company level issue, you don’t want your backups to be lost alongside your site.

    Access Control

    Getting access control right is critical when recovering from a hacked website. Faithfully backing up your site every hour won’t matter at all if a hacker is able to delete everything once they’ve taken control of your website. To avoid this, you need to configure the permissions for your WordPress backup storage so that new files can be saved, but saved files cannot be deleted using the credentials you use for ongoing backups. By using this approach you protect your backups from hackers even if they take full control of your website. Check out this great tutorial from UpdraftPlus on how to securely save backups to AWS S3.

    Redundancy

    In technology, the concept of redundancy means having extra components around in case of failure in other system components. In the context of backups, we want to make extra copies in case the others are either not available or compromised in some way. The number of copies of your WordPress backups you should store depends on how important your website is to you and how much you are willing to invest to reduce risk.

    There are three aspects of redundancy to consider: hardware, geography and service / company.

    Hardware redundancy is the most basic, and the easiest to solve. Simply put, you do not want hardware failure to keep you from accessing your backups. If you’re storing your backups in your own data center, or in a folder on your laptop (gasp!), make sure that something as simple as hard drive failure won’t take you out. If you’re using an online storage solution such as Dropbox, make sure that they have adequate hardware redundancy built into their systems.

    Geographic redundancy can be incredibly important. Things like natural disasters and power outages can render your backup files unreachable for hours, days or even weeks. And it doesn’t take a hurricane to take out a data center: many a data center has lost network or power access due to something as mundane as an overzealous backhoe at a construction project next door. By storing your WordPress backups in geographically diverse locations you significantly reduce the risk that your files will be unavailable when you need them.

    Service redundancy in this context means not relying on any one company to keep your backups safe and available. Internet services have outages all the time. And in some cases like the DynDNS outage last fall, a single event can impact a large number of services simultaneously. By storing copies of your backups with multiple, independent services you significantly reduce the risk of an outage impacting your access.

    How Should I Manage My WordPress Backups?

    The easiest way to manage your WordPress backups is via a plugin that meets your needs. There are a wide variety of options available, and as you can see from this feature comparison table, their features vary dramatically. The following are the features we think you should consider when evaluating your options.

    Author Reputation

    As with all WordPress plugins, the first thing you should consider is whether the plugin author is reputable. What rating has the plugin received on WordPress.org? How many times has it been downloaded, and how many sites have it actively installed? How long has it been since the plugin was updated?

    By answering those questions, you should be able to quickly narrow your choices down to plugins you can rely on.

    Automatic Restore

    When your site has been compromised, time is of the essence. You want to reduce the impact on your customers, search engine rankings, your reputation and even revenue. The ability to automatically restore your site can significantly speed up the time it takes to restore your site to working order.

    Support for Database Encryption

    If your site database is encrypted, it is essential that your backup solution can both back it up and restore it. Make sure that you understand how and where your encryption keys are being stored and whether they will be available when you need them.

    Backup File Encryption

    It is very likely that your backup files contain sensitive information. Your backup solution should ideally allow you to encrypt your backup files before storing them remotely. As we suggested with database encryption, make sure that you understand how your encryption keys will be stored and that they will be available when you need them.

    Secure File Transfer

    Make sure that your files are being transferred securely. Communication between your website and storage locations should always leverage secure protocols such as SFTP, TLS or SCP.

    Secure Administration

    The account you set up to manage your backup service becomes a new target for attackers. Make sure that you can properly secure access to your backup administration functions. All administrative communication should happen via TLS (or other encryption protocol). Also, you should exercise the same level of password security you employ for your website by using unique, strong passwords and ideally enabling two factor authentication.

    Multisite Support

    If you are leveraging WordPress Multisite functionality, or plan to do so in the future, make sure that your backup solution supports it. Transitioning to a new solution can be a lot of work, so make sure that you aren’t forced to switch down the road.

    Support for Hosting Company Migration

    As we mentioned earlier in the post, we often find that security issues that occur are the responsibility of the hosting company. In many cases, the site owner is forced to change hosting providers to solve the problem. Not all backup solutions support seamlessly restoring your site to a new hosting account.

    Conclusion

    Implementing a well-thought-out backup strategy is a crucial component of a “defense in depth” security approach. Make sure you consider the following when determining your strategy:

    • Take WordPress backups frequently enough to ensure that you can restore your site without significant data loss.
    • The more important your website is, the more redundancy should be built into your backup storage approach.
    • Make sure that your backup is kept secure during transfer and storage.
    • Use a full-featured, reputable backup plugin to make implementing your strategy easy.

    The post WordPress Backups Are Critical to Your Security Strategy appeared first on Wordfence.

  • The May 2017 WordPress Attack Report

    Today’s post is a continuation of the WordPress Attack Report series we’ve been publishing since December 2016. Previous versions can be found here: April 2017, March 2017February 2017January 2017 and December 2016.

    This report contains the top 25 attacking IPs for the month of May and their details. It also includes charts of brute force and complex attack activity for the same period. We also include the top themes and plugins that were attacked, and which countries generated the most attacks for this period.

    The Top 25 Attacking IPs

    The next section is our standard explanation of how the table below works. If you are familiar with our attack reports, you can skip down to the table below which contains the data for May along with my commentary.

    Brief Introduction (If You Are New to Viewing These Reports)

    In the table below, we’ve listed the most active attack IPs for May 2017. Note that the “Attacks” column is in millions, and is the total of all attacks that originated from each IP. Farther right in the table (you may have to scroll right) we break down the attacks into “brute force” attacks and “complex” attacks.

    Brute force attacks are login-guessing attacks. What we refer to as “complex attacks” are attacks that were blocked by a rule in the Wordfence firewall.

    We have also included the netblock owner, which is the organization (usually a company) that owns the block of IP addresses that the attack IP belongs to. You can Google the name of each owner for more information. A Google search for any of these IP addresses frequently shows reports of attacks.

    The hostname included is the PTR record (reverse DNS record) that the IP address owner created for the IP, so this is not reliable data, but we still include it for interest. For example, we have seen PTR records that claim an IP is a Tor exit node, when, based on traffic, it is clearly not.

    We also include the city and country, if available. To the far right of the report, we show the date in April when we started logging attacks and the date the attacks stopped.

    The Top Attacking IPs

    The total attacks from the top 25 attacking IPs increased from 137 million in April to 144 million in May.

    Brute force attacks made up 72% of total attacks for May, up from 68% in April. Complex attacks accounted for 28%.

    Turkey and Ukraine continued to dominate the top 25 list, accounting for 16 of the IPs on the list.

    Brute Force Attacks on WordPress in May 2017

    In the chart below, we show the number of daily brute force attacks on the sites we monitor for the month of May.

     

    The average number of daily brute force attacks dropped by almost 39% this month – a massive drop in volume after two months of much higher volume. As we wrote about on May 2nd, a home router botnet shut down which had previously been performing brute force password-guessing attacks on WordPress sites. The peak day for the month was also much lower, at just over 30 million versus over 46 million the previous month.

    Complex Attacks on WordPress in May 2017

    In the graph below, we show the daily complex attacks (attacks that attempt to exploit a security vulnerability) for May.

    Average daily attack volume for May was down was down just 6% from April for the sites that Wordfence protects at 5.4 million.

    Similar to April, we saw an uptick in volume toward the end of the month, peaking at over 9 million attacks in a single day.

    Attacks on Themes in May 2017

    The table below shows the total number of attacks on WordPress themes. We identify each theme using its slug, which is the directory where it is installed in WordPress.

    There was quite a bit of change in the rankings from last month. Most notably, ypo-theme jumped 30 places in the rankings, going from number 34 to 4.

    Based on a quick Google search, that theme doesn’t appear to be available for download anymore. There was quite a bit of content published in 2016 about an Arbitrary File Download vulnerability, so we took a closer look at the attacks to try to figure out what’s behind the spike in attack volume and to see if the two were related.

    The first thing we noticed is that the attacks do appear to be attempting to exploit the Arbitrary File Download vulnerability we referenced above. Attackers attempt to download the wp-config.php file from the targeted sites. Secondly, the vast majority of attacks are originating from a small list of IP addresses. Almost 57% of the attacks are coming from 31.184.194.90, an IP from Saint Petersburg, Russia. Over 92% of all attacks are originating from just 10 IPs. We think it’s likely that the surge in attacks on this particular plugin vulnerability can be attributed to a single attacker.

    Attacks on Plugins in May 2017

    The table below shows the total number of attacks on WordPress plugins. As with themes, we identify each plugin by its unique slug, which is the unique installation directory where the plugin is installed.

    Similar to what we saw with themes, the top 25 list for plugins had quite a lot of change. Ten plugins in the top 25 this month weren’t on the list last month. Most of those 10 jumped dramatically in the rankings this month. We took a look at the highest ranked plugin of the 10 newbies, sell-downloads, to see if we could figure out what is behind the increase in “popularity.”

    According to WordPress.org, the Sell Downloads plugin has roughly 900 active users. There was a security vulnerability published in December of 2015  that impacts versions 1.0.16, but the current version of the plugin is 1.0.42, so we assume that vulnerability has been fixed for a long time.

    We then looked at where the attacks were originating and discovered quite a coincidence: the same IP that was responsible for the surge in attacks on ypo-theme –  31.184.194.90 – was responsible for over 71% of the attacks on this plugin in the month of May. The top 10 IPs were responsible for over 95% of attacks on the plugin.

    Attacks by Country for May 2017

    The table below shows the top 25 countries from which attacks originated in the month of May on WordPress sites that we monitor.

    Country rankings were very stable at the top of the list this year, as is frequently the case. There was quite a bit of movement toward the bottom of the list, but at relatively low volumes.

    Conclusion

    That concludes our May 2017 WordPress attack report. It was really nice to see the volume of brute force attacks down for the month. We hope that trend continues.

    The post The May 2017 WordPress Attack Report appeared first on Wordfence.

  • Spotlight: How a Digital Marketing Agency Secures Client Sites

    Spotlight: How a Digital Marketing Agency Secures Client Sites

    Spotlight: How a Digital Marketing Agency Secures Client Sites

    Based in Melbourne, Australia for over 17 years, 24Digital knows what it takes to succeed in the ever-evolving digital marketing space which is no longer a world resting on desktop alone. The goal is to be an extension to every client’s marketing department, a true partnership to launch or rebuild effective websites – from WordPress to Magento ecommerce sites, and everything in between.

    We’re creative technologists. Hybrids of the digital world.

    Owner Jess Knollmeyer understands how to communicate with the hundreds of clients her company manages.

    Continue reading Spotlight: How a Digital Marketing Agency Secures Client Sites at Sucuri Blog.

  • PSA: OneLogin Breached. Here’s What You Need to Do.

    This is a public service announcement from Wordfence. We are sending this notice to the WordPress community due to the widespread nature and potential severity of this security issue. It has a high likelihood of impacting some of our readers and requires immediate action on their part.

    Single sign-on provider OneLogin has experienced a breach. If you or your company uses OneLogin to sign in to applications, or if you use any of their other services, you need to be aware of this and may need to take several actions immediately.

    In the past 24 hours, OneLogin sent out the following notice about a security incident:

    On Wednesday, May 31, 2017, we detected that there was unauthorized access to OneLogin data in our US data region. All customers served by our US data center are affected; customer data was compromised, including the ability to decrypt encrypted data. We have since blocked this unauthorized access, reported the matter to law enforcement, and are working with an independent security firm to assess how the unauthorized access happened and to verify the extent of the impact. We want our customers to know that the trust they have placed in us is paramount, and we have therefore created a set of required actions.

    Emphasis ours; we have bolded the section that says attackers managed to decrypt encrypted data because this could be particularly damaging to OneLogin customers. You can view the full notice in this screenshot, including the necessary actions that OneLogin suggests.

    This is not the first time OneLogin has experienced a breach. Their ‘secure notes’ feature was breached in August of last year.

    The long list of actions OneLogin suggests users take are as follows:

    • If you replicate your directory password to provisioned applications, force a OneLogin directory password reset for your users.
    • Generate new certificates for your apps that use SAML SSO.
    • Generate new API credentials and OAuth tokens.
    • Generate and apply new directory tokens for Active Directory Connectors and LDAP Directory Connectors.
    • Update the API or OAuth credentials you use to authenticate to third-party directories like G Suite, Workday, Namely and UltiPro.
    • Generate and apply new Desktop SSO tokens.
    • Recycle any secrets stored in Secure Notes.
    • Update the credentials you use to authenticate to third party apps for provisioning.
    • Update the admin-configured login credentials for apps that use form-based authentication.
    • Have your end users update their passwords for the form-based authentication apps that they can edit, including personal apps.
    • Replace your RADIUS shared secrets.

    If you use OneLogin, you should have received an email from them with a link to an article that contains the above guidance with additional detail. The article unfortunately requires you to sign in using OneLogin to access it. Screenshot here.

    OneLogin has also published a brief blog post about the incident without any additional detail.

    This story is also being covered by the BBC,  The Register, Motherboard and by Brian Krebs.

    Please share this with the community so that any users of OneLogin are made aware and can take immediate action to mitigate any damage.

    The post PSA: OneLogin Breached. Here’s What You Need to Do. appeared first on Wordfence.