DEV Community

Discussion on: Four Security Principles That Software Developers Should Follow

Collapse
 
robdwaller profile image
Rob Waller

Hi Thomas,

Thanks for the comment and feedback, sorry I haven't responded to this sooner, I've been a little busy with work and other things...

To answer your questions, I absolutely agree that it's sensible to follow the advice of experts. I just believe there is a difference between this and following dogma which can be counterproductive.

In terms of of HTTP vs HTTPS: A Jekyll / Static site served over HTTP is likely more secure than a WordPress / Drupal site served over HTTPS. My point was simply that HTTPS does not guarantee security, merely increases it. You shouldn't implement HTTPS and assume you're safe.

I hope that answers your questions.

Collapse
 
thomasvjames profile image
Thomas James

Hi Rob, No worries.

I think your statement about Site Security and HTTPS is conflating two very different aspects of security to the point of being harmful to a less-informed reader.

I'd argue that HTTPS in no way increases your site's security (for some definition of security). Any expectation that is does is misinformed. What is does do is well documented by others such as Troy Hunt, so I'll link to that rather than poorly attempting to make the same point. Overall HTTPS is about the security of your visitors, not how hackable your own platform is.

troyhunt.com/dont-take-security-ad...

troyhunt.com/the-6-step-happy-path...

It's certainly not dogma, but just good practice, and with the prevalence of services like CloudFlare and LetsEncrypt, the barrier to entry is pretty much zero now.

Cheers!