Whether you’re inexperienced with WordPress, or you’ve been using the platform since its existence, this article has 10 practical and supper effective ways to secure your WordPress blog that anybody can implement.
Hackers are nothing if not persistent. Where others see obstacles and quit, hackers brute-force their way through barriers or find ways to game or bypass them. And they’ll patiently invest weeks and months devising new methods to do so.
We live in a world online, in which exists threats that aim to steal your money, your private data or information, and even worst, your identity entirely.
A hole in a widely used encryption technology has given hackers a way to infiltrate many of the world’s largest websites and download sensitive information from servers without leaving a trace. The problem, dubbed Heartbleed, has existed for two years but was recently discovered by researchers at Google setting off a scramble to fix it. Curious if a website that you use has patched the Heartbleed exploit? Visit Qualys SSL Labs page test any SSL site and ensure that your private data is safe and secure. The Heartbleed Bug The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs). The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users. What leaks in practice? We have tested some of our own services from attacker’s perspective. We attacked ourselves from outside, without leaving a trace. Without using any privileged information or credentials we were able steal from ourselves the secret keys used for our X.509 certificates, user names and passwords, instant messages, emails and business critical documents and communication. How to stop the leak? As long as the vulnerable version of OpenSSL is in use it can be abused. Fixed OpenSSL has been released and now it has to be deployed. Operating system vendors and distribution, appliance vendors, independent software vendors have to adopt the fix and notify their users. Service providers...