Secure WordPress Hosting

Prevention, Mitigation, and Restoration.

Introducing PressARMOR™

A comprehensive security architecture developed by Pagely® that hardens and protects our network, hardware, and WordPress applications. The primary focus is on prevention and the mitigation of risk to clients.

Secure WordPress Hosting is just how we do business. For base level security, we utilize a dynamic web application firewall (WAF) that blocks code injection attacks, known exploits and rate limits access attempts. This greatly reduces the chance of a DDoS attack or Brute force attack succeeding.

On top of the above, we also practice chroot user separation and real-time system malware scanning. Scanning for malware means we’re constantly looking for things like trojan horses, viruses, worms, keyloggers, spyware, and adware. Additional rulesets at our network edge filter out much of the nefarious traffic long before it even has a chance to pass into our network.

Furthermore, Pagely has always considered it our task to assist you in cleaning and restoring a site should it become compromised, free of charge.

Prevention

A cornerstone of our secure WordPress Hosting strategy is prevention. We have crafted custom rules for our network edge, web nodes, and file system. All primary Pagely services used by our team is behind 2-factor authentication, and key based access.

Mitigation

Proactively patching plugins system wide as well as real time malware scanning is just the beginning. Our security team executes our 5 step protocol in the rare case of successful infection of client site that informs and leads the client through the process of mitigating the attack and restoration.

Restoration

Unfortunately nothing is 100% hack-proof. When it does happen our team works closely within our security protocol to clean and restore the client's site to pristine condition, free of charge.

Additional Details

  • Managed Web Application FireWalls
  • Brute force mitigation and Rate Limiting
  • Custom WordPress specific firewall rules
  • Chroot'ing of all shared systems
  • Administrator 2-factor authentication for core services
  • Multi-level Intrusion Prevention and Detection
  • Malware prevention and remediation
  • Comment spam prevention, system wide

View Pricing or Request Proposal

The Shared Security Model

In this model responsibility for the the overall security of the platform, and a customer's specific site is shared between vendors and customer.

Shared Security Model

The Other Guys

  • "WPEngine Security Breach: Customer Credentials Exposed" 
  • "It seems that this attack is limited to only Bluehost and Dreamhost..." 
  • "...a number of sites hosted by Bluehost had been hacked (including their CEO’s blog)" 
  • "...the security issue allowed users admin access to blogs on the [WPEngine] network..." 
  • "...The attackers were able to get access to Rackspace databases and infect the sites..." 
  • "...GoDaddy servers were hacked again..." 
  • "...many sites hosted at Network Solutions got blacklisted by Google..." 
  • "...thousands of sites at different providers (GoDaddy, Dreamhost, HostGator, etc) got hacked..."