1 / 5

Security isn't a product you buy
Antivirus software isn't a security concept. Neither is a firewall. Both are building blocks that only work if they fit your environment and someone keeps an eye on them.
That's why we look at the whole chain: the workstation, the servers, the network and the cloud services you use. A perfectly configured firewall doesn't help much if there's a server behind it running a three-year-old patch level, or if every employee can access every folder.
So it always starts with an assessment: what's in place, where the risks are, and which of them are worth fixing first. We work with long-standing partners and choose the technology based on your requirements, not our sales targets.
How deep this assessment goes depends on how your environment is set up and what you want to know. Sometimes half a day is enough to find the three biggest gaps. Sometimes it's worth looking closer. What makes sense in your case, we clarify beforehand – not afterwards on the invoice.

Firewall and network security
The firewall decides what's allowed into your network and what's allowed out. Both matter: outbound traffic is often the first sign that a system has been compromised.
We plan and operate firewalls sized to your business, set up connections for your locations and remote staff, and separate areas that have nothing to do with each other. A point-of-sale system, a machine controller or the guest Wi-Fi don't belong on the same network as your accounting.
That separation is one of the most effective levers there is: it doesn't stop every attack, but it limits how far one gets.

Protection at the workstation
The most common way into a company is an employee who clicked on something. That's not a criticism – fake invoices and job applications are well made these days.
For us, endpoint protection means up-to-date antivirus, a clean permissions model and, above all, patch management. Most successful attacks don't exploit unknown gaps, but known ones that have had an update available for months.
We run these building blocks day to day – antivirus, monitoring clients, installing updates – as part of our Managed Services. This page is about how the whole thing needs to be built so it holds up.

A backup is only security once the restore actually works
Almost every company has a backup. Far fewer have ever checked whether it can be restored – and how long that takes.
Those two questions decide the extent of the damage in a real incident. That's why we clarify upfront:
- What needs to be restored to keep working? Not all data is equally important, and not everything needs to be back immediately.
- How much data loss is tolerable? That determines how often backups run.
- How long can the restore take? That determines how the backup needs to be built.
- Are the backups themselves protected? Ransomware specifically hunts for reachable backups and encrypts them too. A backup sitting freely writable on the same network is worthless in a real incident.
- When was the restore last tested? We ask this at the start of every engagement. For most companies, the honest answer is: never.
The answers turn into a concept that fits your business – not a tariff you're squeezed into. The actual backup then runs as online backup through our Managed Services.

If it happens anyway
Business continuity management sounds like something for large corporations. What it really means is a simple question: what do you do on Monday morning when nothing works any more?
Whoever works that out only once it's actually happening loses days. So we define in advance which systems come back in what order, who gets informed, who's allowed to decide, and how you stay able to act while IT still isn't.
For companies with special requirements – healthcare or logistics, for example, where outages directly affect people or supply chains – we build recovery concepts that go beyond plain data restoration.
Where your systems run plays a role here too: in our private cloud we have full control over the architecture and redundancy, and can design the recovery accordingly.