The Disciplines Plate IV Cybersecurity

Cybersecurity.

Security that doesn't get in the way of the work.

Posture reviews, hardening, secrets management and monitoring, scaled to the size of the business and what it has to protect.

Return to the workshop

Good security for a small business is mostly unglamorous: patched machines, MFA, proper backups and email that cannot easily be spoofed. These are the measures I concentrate on, and I choose them so that the people who use the systems every day hardly notice they are there.

I am not going to scare you into buying things you don't need, and I will not sell you Cyber Essentials as if it were a complete security programme, because it is not one. You get controls that fit your size, your industry and the risks you actually face, from someone who has spent two decades inside security organisations and holds an MSc in the discipline.

§ What I protect

  1. I.

    Infrastructure security

    Server hardening, firewall configuration, intrusion detection, automated patching and vulnerability scanning, aimed at the weaknesses that attackers go for most often.

  2. II.

    Application security

    Secure coding, input validation, protection against SQL injection and XSS, and careful handling of authentication and sessions. Security is part of the design from the start and not added at the end.

  3. III.

    Access control

    MFA, password policies that don't end with the passwords written on post-its, role-based access and least privilege, so that each person can reach what their job needs and nothing more.

  4. IV.

    Data protection

    Encryption at rest and in transit, secure backups, retention policies and GDPR compliance where it applies, both for your own data and for your customers' data.

  5. V.

    Email security

    SPF, DKIM and DMARC set up correctly, together with spam filtering, phishing protection and a secure gateway. Business email compromise is one of the most common ways in, so I make sure that one is closed.

  6. VI.

    Security monitoring

    Log analysis, intrusion and anomaly detection, and alerts tuned so that they fire when something actually matters. I watch for suspicious activity and respond to it before an incident turns into a breach.

§ The approach

  1. Step 1

    Security assessment

    I look at where you stand now, meaning what you are protecting, which threats are realistic and where the gaps are, and the plan is built from that.

  2. Step 2

    Risk-based priorities

    Not every risk is equal, so I rank them by how likely they are and how much damage they would do, and the budget is spent first on what is both valuable and exposed.

  3. Step 3

    Implementation

    The controls go in one at a time and in order: technical ones such as firewalls and encryption, written policies and procedures, and physical measures where they are relevant. The idea is that each layer covers for the others.

  4. Step 4

    Training & awareness

    Your staff are the first line of defence, so I train them to recognise phishing, to handle passwords safely and to report anything that looks suspicious.

  5. Step 5

    Ongoing monitoring

    The monitoring does not stop when the work is done, and there are regular updates and periodic reviews as new threats come up.

  6. Step 6

    Incident response

    If something does happen, there is a written plan: what to do, who to call and what to tell people.

§

Questions, answered

Before you
have to ask

We are small. Is this really necessary?

Yes. Most attacks are automated, and they don't check how big a company is before they try. What you don't need is enterprise tooling at enterprise prices, which is why I size the work to the business.

Can you help us get Cyber Essentials?

Yes, and Old Forge holds Cyber Essentials itself. Most of the work is getting your systems to the point where every answer on the questionnaire is actually true, and filling it in afterwards is the easy part.

What will it cost?

The prices on this page are starting points, so that you can tell in a minute whether you are in the right range. I then quote each job once we have talked it through, because the price depends on the shape of the job, and at this point nobody knows that yet. The first half hour is free, and usually it settles whether this is a small piece of work or a large one before any money is discussed.

Who owns the code when it is finished?

You do, outright, including the source. I hand it over with the runbooks you need to keep it running, and there is no licence to renew and no seat to pay for. Where this page quotes a monthly figure, that is for hosting or ongoing support, which is optional and can be stopped without taking anything away from you. When I say commissions, not subscriptions, I mean it literally.

What happens if you are unavailable?

I build everything so that somebody else could pick it up: common technologies, readable code, written runbooks and nothing proprietary. It is a fair question to ask of a one-person business, and the answer lies in how the work is built.

Do you work outside Suffolk and Cambridgeshire?

Yes. With local work you get the option of having me in the room, which is worth more than it sounds for the first conversation and for the handover, and for most clients everything after that is done remotely anyway.