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

Wazuh SIEM security supervision for Moroccan SMEs

A SIEM does not stop an attack: it makes one visible. What Wazuh actually watches on your servers, what it costs to run, and where your monitoring ends and your host's begins.

A SIEM does not stop an attack: it makes one visible. What Wazuh actually watches on your servers, what it costs to run, and where your monitoring ends and your host's begins.

Most small companies learn they were compromised weeks after the fact, when an unusual hosting invoice shows up or a customer complains. The logs were usually there. Nobody was reading them. That gap is what Wazuh, an open-source SIEM, is built to close: it collects events from your servers, correlates them, and surfaces the handful of alerts that deserve a human decision. Here is what it actually detects, what it costs to operate, and what you should and should not expect from your hosting provider.

What Wazuh actually watches

Wazuh is not antivirus software and it is not a firewall. It will not block an attack; it makes one visible. It ingests events from your systems, applies rule sets, and turns an unreadable stream into ranked alerts. Three detection families do most of the daily work.

Authentication and access

Repeated failed SSH logins, a successful login from an unexpected country, a new account, a privilege escalation, sudo use outside working hours. These are the highest-value signals a SIEM can offer, because they almost always come before the damage. An attacker who gains access has to log in, and that login leaves a trace.

File integrity

Wazuh fingerprints sensitive files and tells you when one changes: a modified homepage, an added SSH key, an nginx configuration rewritten at three in the morning. On a brochure site or a store, this is often the first visible sign of a compromise.

Vulnerabilities and configuration

The vulnerability module compares installed packages against public CVE feeds, while the security policy module checks a baseline of hardening rules. The value is not the score. It is the short, dated list of patches to apply this week on the machines that matter.

Agent or agentless: how logs get in

Both collection models coexist. An agent is a small service on the host: it reads logs locally, applies rules close to the source, and ships only what is useful. Agentless collection relies on SSH, Syslog, cloud APIs, or a forwarder for devices that cannot run software.

  • Linux servers: native agent, system and application logs.
  • Windows: native agent, event logs, PowerShell.
  • Firewalls and network gear: Syslog, usually the only option.
  • Business applications: log files or APIs, through an intermediate collector.
  • Cloud and containers: provider audit logs, container standard output.

Use the agent wherever you can. It means less traffic, more context, and a local queue that keeps events from disappearing when the link drops.

The alerts worth acting on

A badly tuned SIEM produces thousands of alerts a day and becomes background noise nobody reads. The real work is picking about twenty rules, tying each to a written procedure, and deliberately ignoring the rest.

  1. Access: successful logins outside business hours or from a new geography.
  2. Persistence: a new SSH key, a new scheduled task, a new service account.
  3. Exfiltration: an outbound traffic spike, an archive created and compressed on a web server.
  4. Integrity: a change to a file nobody should be touching.

Every alert you keep has to answer three questions: who receives it, how fast, and what they do next. Without that written answer, detection only documents the incident after the fact.

Sizing the host before you deploy

A full Wazuh stack runs three roles — manager, indexer, dashboard — and the indexer sets the size, because it stores and indexes events and its footprint follows log volume and retention. A lab setup fits on a small instance. A real fleet needs memory and NVMe disk.

PlanvCPURAMNVMeUSD/moDH excl. VATTypical use
VPS-1G Startup11 GB30 GB9.9994.48Learning the tool
VPS-2G Business12 GB40 GB19.99189.06Pilot, limited collection
VPS-3G Performance23 GB50 GB34.99330.93Small fleet, short retention
VPS-4G Advanced24 GB80 GB39.99378.22SME fleet, comfortable retention
VPS-5G Ultra35 GB100 GB49.99472.80Larger fleet, long retention

Every plan includes one dedicated IPv4, unlimited bandwidth, automatic backups, firewall and DDoS protection, 24/7 supervision, root access, and a 99.9% SLA on infrastructure. Two honest notes: a 1 GB server is for learning the tool, not for protecting a fleet; and retention costs disk, not CPU — plan for it before you add agents, never after.

Wazuh and your host's monitoring: who does what

A hosting provider and a SIEM do not work on the same floor. The provider watches infrastructure: host availability, network, storage saturation, reboots. Wazuh looks at what happens inside your system: accounts, files, applications, compliance. Confusing the two is the most common mistake.

  • Hosting provider: physical host, hypervisor, network, DDoS, platform backups, 99.9% SLA on infrastructure.
  • Wazuh: operating system events, file integrity, software vulnerabilities, application access.
  • You: business rules, the escalation procedure, the call to shut a service down.

The supervision bundled with our VPS plans does not replace a SIEM. It guarantees the machine is reachable and the platform meets its commitments, not that nobody added an SSH key to your server. To place this work in the wider priority order, our page on cybersecurity in Morocco covers the controls to handle before this one.

FAQ

Is Wazuh free?

The software is open source with no per-server license. What costs money is the infrastructure underneath and the human time on top: installation, rule tuning, on-call. A VPS to run it starts at $39.99/month (about 378.22 DH excl. VAT) for the machine; operating it is counted in hours.

Do I need an agent on every server?

No, but it is the mode to prefer whenever the machine allows it. Agentless collection stays essential for firewalls, network devices and locked-down systems, at the price of more traffic and less context.

How long does it take to set up?

A working stack with a few agents takes about a day. Rule tuning and writing the procedures take longer, and that is where the value is decided. Our consulting packages are sold in hours: $669.99 for 10 h, $2,382.99 for 40 h, $5,212.99 for 100 h.

Does it replace my hosting provider's monitoring?

No. The two layers are complementary: the host guarantees infrastructure availability, Wazuh detects what happens inside your systems. A 99.9% SLA says nothing about an SSH key added last night.

Where to start

If you already host something critical, the first step is not rolling Wazuh out everywhere. Pick three machines, turn on authentication and file integrity monitoring, and hold a twenty-minute weekly review. Two weeks tell you whether you are producing noise or signal. The second step is sizing: a stack short on memory drops events, which is the same as not monitoring at all. Our managed Wazuh service covers deployment and day-to-day operation if you would rather not spend internal hours on it, and the security supervision page details the scope.

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.