We all want or have that friend that will tell us when we have spinach in our teeth. You know, the type that pulls us to the side and says it… this isn’t to be confused for the type that says it at the least opportune time in front of your bosses’ boss but that story is for another time. We all have nightmares okay?

Back to the topic of this blog though… I have a friend who has my back in a way like no other – it tells me that some filthy entity has tampered with my beautiful code and saves my butt quite often.

Okay, backstory time:

Clients sometimes like to engage in what I like to call the event horizon guarantee.

That means, I ensure that everything is rotating around the black hole in a steady balance for x amount of time. If any variable in their environment changes, my guarantee either needs to account for this or will be void (should a third party /developer tamper with the code and ‘break’ the system). This of course, does not include security issues that result from a bug that I should have addressed.

It’s important to safeguard ourselves and clients by providing comprehensive agreements prior to project commencement so the stakes are clear.

This is where generating a checksum for your code comes in. I use this method in every project and you should too!(infact it should be one of multiple ways you check your code’s integrity).

$mychecksum = md5_file($codefilepath);

And that’s it, save this, automate your processes, and boom! one more way to be more secure.

Ok, I’ve been more concerned than usual recently. The era of technological advancements at breakneck speeds is upon us and with that comes a plethora of security holes and probably exploitation.

The growing need for advancement in our response and regular ‘housekeeping’ on our digital platforms (and even with digital assets) is abundantly clear.

Over the course of the next few weeks, I will post about general do’s and don’ts and how to safeguard against what’s to come.

Gear up- it’s going to be an awesome, bumpy ride.

In the interim, here are my top 10 security tips for site owners:

1. Keep software and web applications up-to-date: Ensure that all software, including content management systems (CMS) and plugins, are updated regularly to avoid vulnerabilities.
2. Implement strong passwords: Use strong passwords and encourage users to do the same. Passwords should be complex, unique, and changed regularly.
3. Enable two-factor authentication: Two-factor authentication adds an additional layer of security and requires users to provide a second factor of authentication in addition to a password.
4. Secure data transmissions: Use secure protocols (e.g. HTTPS) to encrypt data transmissions to and from the website, especially for sensitive information such as login credentials and payment details.
5. Regularly backup website data: Back up your website regularly and keep the backup in a secure location to avoid data loss in case of a security breach or website outage.
6. Protect against malware: Install antivirus software and firewalls to protect against malware and other malicious attacks. Regularly scan the website for malware and vulnerabilities.
7. Control access: Limit access to sensitive areas of the website, such as the admin panel, to authorized personnel only.
8. Monitor website activity: Regularly monitor website activity for signs of suspicious behavior, such as unusual login attempts or file modifications.
9. Implement website security policies: Establish clear website security policies and procedures for users, such as password policies, email security, and file upload guidelines.
10. Educate users: Educate users on website security best practices, such as avoiding phishing scams, securing their devices, and reporting suspicious activity.

If you need pointers, you know where to reach me, comment below or @ me on Twitter