InfrastructureNew: our VPS servers are live in the United States

Our New York datacenter is live. Our Morocco datacenter is coming soon: your data stays on US servers until launch, and is then migrated. Clients who need data sovereignty in their own country can request the migration. Learn more

Learn more
Free webinars Cloud & Cyber Wednesdays · 30 min · Wednesday 5:00 pm Morocco (12:00 pm Montréal) · Zoom and Rabat office See the programme (32 dates) →
Affiliate program Refer Open Vista, earn 15% recurring commissions. Join free. Join the program →
News

Cybersecurity for Moroccan SMEs: 10 essential controls

Ten controls ranked by payoff rather than by fear: what a Moroccan SME can finish this week, what takes a month, and which three deserve a real project.

Ten controls ranked by payoff rather than by fear: what a Moroccan SME can finish this week, what takes a month, and which three deserve a real project.

Most Moroccan SMEs are not breached because someone picked them out. They are breached because they were reachable: a server nobody patched, a mailbox with no second factor, a backup nobody ever restored. The reassuring part is that most of the risk reduction sits in ten controls, and only three of them need a project. Here they are, in the order we would actually do them.

Why ten controls, not thirty

Security frameworks publish hundreds of measures, and an SME that tries to cover all of them ends up doing none of them properly. An opportunistic attacker does not follow a framework either; they follow the shortest path. Find an exposed door, get a credential, stay resident, take what resells. So each control earns its place through one test: does it break one of those paths, and can you verify it works? The ten below are ranked that way. Our page on cybersecurity in Morocco covers the wider trends behind them.

Three controls to finish this week

None of these need a budget or a consultant. They need two hours and a decision.

1. Know what you expose

Four columns will do: service name, address, who administers it, last update. Domains, forgotten subdomains, servers, SaaS accounts, admin panels, the former provider's access. Most incidents we see start on an asset the owner did not know was still online. That inventory then becomes the worklist for every other control.

2. Turn on two-factor authentication wherever it exists

Email first, because it receives the password resets for everything else. Then the hosting panel, the virtual desktop, the ERP, the domain registrar, the bank. An authenticator app beats SMS, and a single admin account without a second factor cancels the benefit of the other nine controls.

3. Back up, then actually restore

Three copies: one off the server, one beyond the reach of ransomware encryption. Above all, a timed restore every quarter, onto a machine that is not production. An untested backup is not a backup, it is an assumption. Write down the date of the last test, because it is the one line your insurer or your industrial customer will ask for.

Four hygiene controls to spread over the month

Patch on a fixed cadence

Operating system, CMS, plugins, ERP modules. One monthly maintenance window, one named owner, a short list of internet-facing services that go first. A patch applied within thirty days on anything reachable from the internet does more for your exposure than another antivirus licence.

Cut privileges down

A separate admin account from the everyday one, no shared accounts, an offboarding step that kills access the same day. Service accounts for backups, integrations and sync should be able to do their job and nothing else.

Read the logs you already have

Successful logins outside business hours, repeated failures, a new SSH key, a new user. Those four signals cover most scenarios. Twenty minutes a week, on a screen someone actually opens.

Rehearse three phishing scenarios

An urgent invoice from a known supplier, a message from the boss asking for a transfer, a parcel-tracking link. Three a year, unannounced, followed by a fifteen-minute debrief. The goal is not to trap people, it is to install one reflex: verify through another channel before you click or pay.

Three controls that deserve a project

Separate networks and services

The server publishing your website has no business talking to accounting. Simple segmentation, one network for workstations, one for servers, one for backups, with explicit rules between them, turns a breach into a contained breach. It is the strongest control against ransomware and the hardest one to improvise.

Write the incident plan before the incident

Who calls whom, at what hour, who decides to take a service down, who talks to customers, where the backups and keys live. Two pages will do, as long as four things are in them.

  • Who to call: provider, host, insurer, lawyer, with numbers kept outside email.
  • Who decides: the person allowed to take a service down, and their stand-in.
  • Who speaks: one spokesperson for customers and press.
  • Where to restart: where the backups, the keys and the restore procedure live.

A plan nobody has reread is worthless the night the phone rings at 3 a.m., so test it once a year on a deliberately simple scenario.

Monitor what matters, continuously

All of the above assumes somebody is watching. Log monitoring for logins, file integrity and vulnerabilities turns a late discovery into a dated alert. That is the job of a SIEM such as Wazuh, which we deploy and operate; the managed Wazuh page describes the exact scope and the resources it needs.

Prioritizing: the ten controls at a glance

The table gives a realistic sequence for an SME of ten to fifty people. The last column describes what you notice once the control is live, not a promise of total security.

ControlTimingEffortImmediate effect
Asset inventoryWeek 12 hA shared worklist
Two-factor authenticationWeek 12 hStolen passwords become useless
Tested backupsWeek 13 hA rollback that works
PatchingMonth 14 h per monthKnown flaws closed
Least privilegeMonth 13 hShared accounts removed
Access loggingMonth 12 hTraces you can read
Phishing awarenessMonth 22 hA verifying reflex
Network segmentationQuarter1 to 2 daysContained propagation
Incident planQuarter1 dayKnown roles and contacts
Continuous monitoringQuarter1 to 2 days plus subscriptionDated alerts

Two notes. The first three controls need no external budget, which makes them hard to postpone in good faith. And the last three are worthless if the first seven are neglected: monitoring an unpatched system is like filming an open door.

FAQ

Where do we start with only one day?

Two-factor authentication on email and on the hosting panel, then one tested backup restore. Those two moves cover the most common scenarios and need no outside help.

Do we need a CISO or a provider?

Neither, for the ten controls on this page: a part-time IT lead can carry them. Outside help pays off on segmentation, monitoring and the incident plan, where experience prevents expensive mistakes. Our consulting packages are billed by the hour, starting at $669.99 for 10 hours.

Are our host's backups enough?

They protect against a platform failure, not against a deletion, ransomware encryption, or a mistake inside your own application. You need at least one copy you control and can restore without waiting on someone else.

How long does the whole set take?

About a quarter, at a few hours a week, plus the continuous monitoring that becomes routine. The SME cybersecurity checklist restates every point as a checkbox.

Your next step

Take the three week-one controls and book them in the next ten days: inventory, second factor, tested restore. Then put a one-hour monthly review on the calendar for the four hygiene controls, and a quarter for the three projects. If you would rather frame this with someone who has done it before, the SME cybersecurity checklist works as the starting document, and our cybersecurity in Morocco page covers sector priorities. The metric that matters is not how many boxes are ticked, it is the date of your last successful restore.

Open Vista

An infrastructure, cloud or cybersecurity project?

VPS, domain names, software licences, Odoo, Microsoft 365 or managed IT: our teams answer you from Laval (Quebec) and Rabat.

2 min

Find the right solution for your business in 2 minutes

5 questions, a tailored recommendation and a projected budget — no commitment.