HTTPS and SSL: a practical guide

The gap between knowing this and actually doing it is where most teams lose ground. This guide covers what HTTPS and SSL actually involves, where it usually goes wrong, and how to tell whether yours is in reasonable shape.

The realistic threat for most small businesses is automated and opportunistic, not targeted. Nothing below assumes a large team or a large budget — most of it is a decision somebody has to make and then write down.

The reason this keeps coming up

Browsers now actively warn on unencrypted pages. The cost of getting this wrong is rarely visible on the day it happens. If it only works because one person remembers to do something, it does not work yet.

For most businesses the question is not whether this matters but how much of it is worth doing right now. That depends on what you are trying to achieve in the next few months, not on best practice in the abstract. None of that requires a large budget, only a decision and someone to own it.

What good looks like

Certificates can and should renew automatically. Small and consistent beats large and occasional here. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

The cheapest security work is the boring kind done on a schedule. The version that works in practice is usually less elaborate than the version described in the guides.

Mixed content quietly breaks the padlock. Where this goes wrong is almost never a lack of knowledge. Check it against what you would want a competitor's site to get wrong.

A working checklist

If you want a quick read on where you stand, work through this. Anything you cannot answer confidently is where to start.

• Browsers now actively warn on unencrypted pages
• Certificates can and should renew automatically
• Mixed content quietly breaks the padlock
• Someone is named as the owner, not just assumed to be
• There is a date in the calendar to review it again
• The decision and the reasoning behind it are written down somewhere findable
• You could explain the current setup to a new hire in five minutes

Common failure modes

The most common failure is not doing this badly. It is doing it once, during a launch, and never revisiting it. Circumstances move, the setup does not, and the gap widens quietly until something breaks or somebody notices the numbers.

• It was configured during a launch and has not been touched since
• Different people in the business believe different things are true about it
• There is no way to tell whether the last change helped or hurt
• The only person who understands it has left, or is about to

Security is a maintenance habit rather than a purchase, which is why it drifts. In practice this is a scheduling problem more than a technical one.

How we approach it

On our projects this gets handled during the build rather than added afterwards, because retrofitting it costs several times more than including it. We write down what was decided and why, so the next person to touch it is not guessing.

If you are working with someone else, the questions worth asking are simple: who owns this, how will we know it is working, and what happens when it needs to change?

Where to go from here

Pick the single item from the checklist above that would cause the most trouble if it turned out to be wrong. Fix that one, confirm it worked, then move on. The point is not perfection, it is knowing which of these you have consciously chosen to skip.