A Guide to Cyber Security for SMEs

There’s a continual stream of blogs and posts about cyber security and the sometimes catastrophic effects of getting it wrong, but there is very little that tells SMEs what they should be doing, and it’s generally left to local IT management companies and VARs (Value Added Resellers – i.e. those who sell various products and add value by configuring and managing them). I’m not knocking those companies; they have a very valid business model. But what they aren’t are cyber security professionals and generally their security expertise is focused on the products that they sell. For instance, they will have good skills in installing and configuring security products such as anti-virus and firewalls but there is generally no knowledge of cyber risk management and assessment, thereby ensuring that you have the right defences in the right place, providing the best value for your limited spend, and ignoring the non-technical solutions that are often a better bet than a piece of technology.
SMEs generally have very little budget to allocate to this and that means that what budget they have needs to be effectively targeted at what is important. They need to be aiming for a situation whereby when a potential attacker targets them, they appear to be a more difficult nut to crack than other organisations in their space and their size. Attackers want things to be easy, not difficult, and they will often move on if things get difficult. A criminal is in the game of getting easy money.
Let’s take a look at what cyber security is all about, and more importantly, why you need it? Let’s tackle the first question – what is cyber security? One definition is as follows:
Cybersecurity is the practice of protecting computer systems, networks, software, and data from digital attacks, unauthorised access, damage, or theft. It involves a range of technologies, processes, and practices designed to:
- Prevent cyberattacks
- Detect breaches or suspicious activity
- Respond to security incidents
- Recover from damage or loss caused by attacks
The problem is of course that each bullet point there covers a multitude of issues that need to be addressed. The question is understanding what those issues are, how they affect you and what is the priority i.e. what are the most important things that you need to protect, and what comes next, all managed within whatever budget you can allocate to it. It’s not easy and you might feel that you don’t need to do everything but that you need to cover off the most important issues. That means of course that you need to know what those issues are.
The first thing you need to do is to identify your cyber assets. Assets are not confined to hardware and software, far from it. A cybersecurity asset is anything of value that requires protection in a digital context. Identifying and classifying these assets is a foundational step in building a strong cybersecurity posture. Assets will change from company to company, depending upon how you’re organised and what business you are in, but generally:
Hardware Assets
- Servers, routers, laptops, mobile devices, firewalls
- Why it matters: Physical devices are entry points for attackers and must be secured.
Software Assets
- Operating systems, applications, databases etc
- Why it matters: Vulnerabilities in software can be exploited to gain unauthorised access.
Data Assets
- Customer records, financial data, intellectual property, source code
- Why it matters: Data breaches can lead to regulatory fines, reputational damage, and financial loss.
Network Assets
- VPNs, switches, IP addresses, subnets
- Why it matters: Networks facilitate communication and, if not protected, can be avenues for lateral movement by attackers.
People Assets
- Employees, contractors, system administrators
- Why it matters: Human error is a leading cause of breaches, so training and access control are crucial.
Cloud and Virtual Assets
- Virtual machines, containers, cloud storage (e.g., AWS S3, Azure Blob Storage)
- Why it matters: Cloud environments introduce new attack surfaces that must be monitored and managed.
An example could be a customer database, maybe on the cloud or via an app, or even an onsite server. You class this as high value because it contains personally identifiable information (PII) and of course all your interactions with those customers and the value they have to you. Lose that and you might be out of business. You decide to encrypt it and use multi factor authentication and have daily backups, not kept online.
Identifying the assets is the first step in defining what protections you need. You then have to categorise those assets and decide how important they are to the business before you can decide what levels of protection they need.

Having categorised your assets, you then need to assign a risk score to them. Now, this can be done formally via a formal risk assessment, but I accept that many SMEs can’t afford to have that done, and, given the size of the company and the amount/types of information held, it might be relatively easy, when compared to a corporate body, to assign a risk score to each asset.

The next step then is to apply a risk score to the assets in accordance with how you have assessed them, this in turn informs you of the importance of each asset and how you will need to protect them. In other words, you are now targeting your spend to where you know it will be most effective.
We then need to identify the vulnerabilities and the threats and that is where most organisations require help.
Here at H2 we use our considerable experience in doing this for corporate level organisations, and translating that into doable chunks for SMEs, carving up what is needed into priorities and working with clients to decide what those priorities are. We do this keeping in mind the principle of People, Process and then Technology, keeping in mind that many protections, or controls as we term them, are actually not technical but are procedural, based on sound policy and process, and therefore costing very little.
We take a phased approach:

The first phase works with the client to decide where they are now, on a scale which we take from the Carnegie Melon cyber maturity model. Most SMEs come out at around 1 to 2 on the scale and aim to get to 3 to 3.5. The scale goes up to 5 but, as you can see from the phased approach above, this tends to be not necessary for an SME and is often too expensive anyway.
Once we know our starting point, we identify quick wins to tighten up security. As a rule, that will include things like cyber awareness training for staff, ensuring that all access is controlled using MFA of some sort and making sure that Admin rights are strictly controlled. Depending on the company and what it does, it might mean instituting some form of identity management.
As part of the Quick win phase, we also look at policies and processes. Is there a process for allocating and removing rights? Is there a policy and process about on and off boarding staff etc. Other policies we might need to look at include:
- Top-level policy issued by the board
- Starters and Leavers Policy
- Access Control Policy
- Magnetic Media Policy
- Mobile Working Policy
- Password Policy
- Email Policy
- Acceptable Use Policy
- Data Protection
That done we move on to Phase 2 which is where we might recommend encryption both at rest and in transit, for critical data assets. We will discuss back up procedures and processes which will ensure that backups are securely stored and that restoring from backups is practiced and works. We will discuss incident handling procedures and business continuity planning. Finally, we will discuss monitoring and audit, two things that until quite recently tended to be out of the price range of SMEs. However, there are now systems and services on the market which are affordable.
This all seems a bit daunting, but if taken in chunks and phased over perhaps several budgetary periods it is doable, and you really need to consider it.




Recent Comments