Hardening WordPress - Reducing the attack vector

[phenomlab]

@jac This sounds like quite the horror story, but sadly, all too common.

@jac said in Hardening WordPress - Reducing the attack vector:

rightly or wrongly proceeded to delete my files via FTP .

This part is where I would have (if you knew me then) have stepped in and claimed back access to the site. The database was probably injected with malicious SQL, so wouldn’t be fit for production use, but it’s perfectly possible (and relatively simple) to get access back via a reset of the admin MD5 hashed password in the database itself.

@jac said in Hardening WordPress - Reducing the attack vector:

I’d lost hundreds of news stories I’d written

This is exactly my justification for writing this

https://content.sudonix.com/how-often-do-you-test-your-backups/

@jac said in Hardening WordPress - Reducing the attack vector:

In my mind I’m thinking the best thing to do is to start again, and like a fool I didn’t have a recent backup of my wordpress installation.

This is why it’s of paramount importance to determine, design, configure, and set a backup and recovery strategy - and, as I mentioned in the article above, this needs to be tested periodically to ensure it is actually fit for purpose rather than simply relying on it being functional when you need it.

@jac said in Hardening WordPress - Reducing the attack vector:

I know Mark will go to town and have nightmares of all my rookie mistakes but after reading the blog I do feel a lot more confident if I was to use WordPress again that I’ve learnt a lot of what not to do and to not be too hasty next time.

No, I won’t - really, I’ve seen this so many times, and one of the reasons as to why this platform exists in the first place is to educate, and ideally, eradicate.

[JAC]

@phenomlab said in Hardening WordPress - Reducing the attack vector:

@jac This sounds like quite the horror story, but sadly, all too common.

@jac said in Hardening WordPress - Reducing the attack vector:

rightly or wrongly proceeded to delete my files via FTP .

This part is where I would have (if you knew me then) have stepped in and claimed back access to the site. The database was probably injected with malicious SQL, so wouldn’t be fit for production use, but it’s perfectly possible (and relatively simple) to get access back via a reset of the admin MD5 hashed password in the database itself.

@jac said in Hardening WordPress - Reducing the attack vector:

I’d lost hundreds of news stories I’d written

This is exactly my justification for writing this

https://content.sudonix.com/how-often-do-you-test-your-backups/

@jac said in Hardening WordPress - Reducing the attack vector:

In my mind I’m thinking the best thing to do is to start again, and like a fool I didn’t have a recent backup of my wordpress installation.

This is why it’s of paramount importance to determine, design, configure, and set a backup and recovery strategy - and, as I mentioned in the article above, this needs to be tested periodically to ensure it is actually fit for purpose rather than simply relying on it being functional when you need it.

@jac said in Hardening WordPress - Reducing the attack vector:

I know Mark will go to town and have nightmares of all my rookie mistakes but after reading the blog I do feel a lot more confident if I was to use WordPress again that I’ve learnt a lot of what not to do and to not be too hasty next time.

No, I won’t - really, I’ve seen this so many times, and one of the reasons as to why this platform exists in the first place is to educate, and ideally, eradicate.

Thanks for the reply mate.

It’s good to know that these problems can be fixed. I think at the time I just thought they’ll attack it again once I’ve launched something else so the best way was for me to get rid of if I’m afraid.

Now of course I’d do things differently .

[phenomlab]

@jac What you can (and 100% should) do if you run a WordPress site is strongly consider WP Shield - there is a free version, but PRO is obviously much better as it has greater capabilities and features

https://getshieldsecurity.com/pricing/

I’ve used this with huge success over the years, and it’s my preferred and recommended security solution for anyone with a WordPress site.

[JAC]

@phenomlab said in Hardening WordPress - Reducing the attack vector:

@jac What you can (and 100% should) do if you run a WordPress site is strongly consider WP Shield - there is a free version, but PRO is obviously much better as it has greater capabilities and features

https://getshieldsecurity.com/pricing/

I’ve used this with huge success over the years, and it’s my preferred and recommended security solution for anyone with a WordPress site.

Absolutely! I can’t remember what I used to use last time but it was free. Most likely the mist downloaded security solution.

Talking of security, somebody tried to access my emails before so I reset the password etc although I do feel I need to maybe use a password generator or something to be more secure.

[phenomlab]

@jac said in Hardening WordPress - Reducing the attack vector:

Talking of security, somebody tried to access my emails before so I reset the password etc although I do feel I need to maybe use a password generator or something to be more secure.

This is s slightly different topic, but it’s just as important. In most cases, the best advice is

• Use a password manager to generate a strong password. You don’t need to remember it - that’s the job of the password manager itself
• Enforce two factor authentication for your email accounts (most have this). In this case, should an attacker get access to your username and password, they still will not be able to login without the second factor which is typically a 6 digit code that changes every 30 seconds

It’s important to note that two factor via SMS is in fact inherently weak and should be avoided - it’s always best at minimum to use a TOTP mechanism with something like AUTHY or Google Authenticator.

[JAC]

@phenomlab said in Hardening WordPress - Reducing the attack vector:

@jac said in Hardening WordPress - Reducing the attack vector:

Talking of security, somebody tried to access my emails before so I reset the password etc although I do feel I need to maybe use a password generator or something to be more secure.

This is s slightly different topic, but it’s just as important. In most cases, the best advice is

• Use a password manager to generate a strong password. You don’t need to remember it - that’s the job of the password manager itself
• Enforce two factor authentication for your email accounts (most have this). In this case, should an attacker get access to your username and password, they still will not be able to login without the second factor which is typically a 6 digit code that changes every 30 seconds

It’s important to note that two factor via SMS is in fact inherently weak and should be avoided - it’s always best at minimum to use a TOTP mechanism with something like AUTHY or Google Authenticator.

Thanks for all the great advice mate appreciate it.

I’ll follow it all up when home .

[phenomlab]

@jac No problem. I’m happy to put together a blog post for this if you think there’s a benefit ?

[JAC]

@phenomlab said in Hardening WordPress - Reducing the attack vector:

@jac No problem. I’m happy to put together a blog post for this if you think there’s a benefit ?

Absolutely matey, that’s up to you pal I’ve just followed the advice and used Microsoft’s authentication app that’s enabled two factor authentication.

[JAC]

@jac said in Hardening WordPress - Reducing the attack vector:

Microsoft’s authentication app that’s enabled two factor authentication.

Or is Google’s better?

[phenomlab]

@jac Microsoft’s and Google’s Authenticator both support TOTP - essentially, a time based system that changes every 30 seconds. The main principle here is that the device itself carrying the One Time Passcode only needs to be in sync with the source server in terms of time, and can be completely offline with no internet access.

Provided the time matches on both devices, the One Time Passcode will be accepted. Applications such as Microsoft Authenticator and Authy also support push notification meaning you just choose either yes or no on your device when prompted, and then that response is sent back to the origin which then determines if access is granted or not.

One of the best looking password less authentication models was CLEF - sadly, this product died out due to a lack of funding (if I recall correctly) although some open source implementations of this have appeared quite recently.

Essentially, both products will achieve the same goal. TOTP is an industry standard, and widely accepted across the board. Not all services offer push confirmation.

[JAC]

@phenomlab said in Hardening WordPress - Reducing the attack vector:

@jac Microsoft’s and Google’s Authenticator both support TOTP - essentially, a time based system that changes every 30 seconds. The main principle here is that the device itself carrying the One Time Passcode only needs to be in sync with the source server in terms of time, and can be completely offline with no internet access.

Provided the time matches on both devices, the One Time Passcode will be accepted. Applications such as Microsoft Authenticator and Authy also support push notification meaning you just choose either yes or no on your device when prompted, and then that response is sent back to the origin which then determines if access is granted or not.

One of the best looking password less authentication models was CLEF - sadly, this product died out due to a lack of funding (if I recall correctly) although some open source implementations of this have appeared quite recently.

Essentially, both products will achieve the same goal. TOTP is an industry standard, and widely accepted across the board. Not all services offer push confirmation.

Many thanks for the detailed reply mate.

There’s some great advice in there that will help me secure my accounts.