A secure network starts with the question of who may talk to whom.
We divide your network into zones, set a rule for every access and test both automatically. You receive the vulnerabilities we find sorted by urgency.
Our approach
A firewall protects the outer boundary of your network. The greatest damage happens behind it. That is where an incident spreads from computer to computer. This is why we give every area its own boundary.
Services
Four building blocks for a secure network
Every project starts with a survey of all paths that are open today. The survey determines the order of the building blocks.
-
01
Segmentation
We separate administration, production, guests and servers into zones of their own. Every connection between two zones has its own rule. This keeps an incident confined to its zone.
- Zones
- VLAN
- Firewall rules
- Guest Wi-Fi
-
02
Access and authentication
We define who accesses which systems from where. Administrator accounts and remote maintenance get a second factor. We review permissions with you at fixed intervals.
- Second factor
- VPN
- Permissions
- Remote maintenance
-
03
Testing and hardening
Automated test runs look for vulnerabilities in your network architecture. You receive the findings sorted by urgency. We fix the urgent points with you first.
- Test runs
- Updates
- Hardening
- Report
-
04
Incident response and recovery
We assign the tasks for an emergency in advance. A plan sets the order of recovery. We rehearse restoring data from the backup with you beforehand.
- Incident response plan
- Recovery
- Backup
- Drill
Zoning plan
This is what a zoning plan looks like.
Each row is a zone and each column is a destination. Every cell stands for a rule in your firewall. Three to five zones are enough for most businesses.
Administration reaches its business applications. It reaches the internet through a filter and machines only through the control room.
| From / to | Administration | Production | Servers | Guests | Internet |
|---|---|---|---|---|---|
| Administration | open | control room only | business applications only | blocked | through filter |
| Production | blocked | open | database only | blocked | blocked |
| Servers | blocked | blocked | open | blocked | updates only |
| Guests | blocked | blocked | blocked | isolated from each other | open |
| Internet | blocked | blocked | published services only | blocked | not applicable |
openonly with a dedicated ruleblocked
Process
How a security project runs
- 01Survey
We check every open path and every access right.
- 02Zoning plan
You receive a plan for the connections between your zones. It follows your processes.
- 03Implementation
We switch over one zone at a time. The way back for every step is fixed in advance.
- 04Verification
A test run checks every permission and every block individually.
Step 04 in detail
At the top is what an attacker could exploit today.
A test run quickly turns up dozens of issues. We sort them by urgency and name the affected system for each one. On Monday morning your team knows its first task.
- urgentRemote maintenance without a second factorFirewall, head office
- urgentFirmware with a known vulnerabilitySwitch, production
- soonGuest Wi-Fi reaches network printerGuest zone
- soonAdministrator account without expiry dateDirectory service
- plannedOutdated encryption methodMail server
Plus 37 issues of low urgency.
Self-assessment
Five questions for your network
You can answer each of them without a service provider. Your answers stay in this browser window.
Do all administrator accounts have a second factor?
Is the guest Wi-Fi separated from the company network?
Have your firewall and switches received a firmware update in the last six months?
Have you restored anything from your backup this year?
Do you know which services are reachable from outside?
In practice
From our projects
Our projects range from internet service providers to advertising agencies.
-
Regional internet service provider, Germany
- Result
- Customer networks and the provider’s own infrastructure sit in clearly separated security zones.
- Task
- Design of the firewall architecture and consulting.
-
Agency of an international advertising network
- Result
- Security updates reach every workstation from one central point in a traceable way.
- Task
- Introduction of Patchlink for all Mac workstations at the sites across Germany.
Questions
Frequently asked questions
Is your question missing? Call us or write to us.
Does this replace our existing firewall?
Will our staff notice the segmentation?
Does this help us with NIS2?
How often do you test?
What happens if an incident occurs at the weekend?
Other areas
Talk to us about your IT security.
Typical reasons are a questionnaire from your insurer, a new site or a near miss.