Back to services

Security architecture

A design that shows what stays, what goes and what to buy before you spend the next tools budget.

Security tools were bought separately, in different years and from different budgets. The firewall sees traffic, the EDR sees a process, the cloud logs to itself, and nobody sees the whole picture. Add duplicate licences, features paid for twice and gaps that no tool covers. Another purchase without a design usually just adds one more tool.

Public bodies also have to describe the tender so that they buy a setup they can run, not just one that passes the acceptance protocol. A security architecture design ends with a document that sets out the changes and their order. Deployment is a separate stage.

01

Current-state inventory

We list what is deployed, what is paid for and what actually works.

  • Tools, licences and actual coverage: endpoints, servers, cloud, identity, email
  • Log flows and the points where blocking decisions are made
  • Features that overlap and areas nothing covers
02

Target architecture design

What stays, what goes, what gets added, and why.

  • Data flows and decision points
  • Integrations between tools
  • The reasoning behind every decision in the design
03

Polish KSC Act and NIS2

Logging, retention and the decision path are designed from the start so that they produce evidence that your controls work.

  • A map: requirement, mechanism, where the evidence is produced
  • Rules for collecting and keeping logs
  • The incident decision path: who blocks what, and when
04

Rollout plan

Stages you can base a tender specification or your own rollout on.

  • Rollout stages with their order and dependencies
  • Licences to retire or consolidate
  • Acceptance criteria you can check after deployment

Out of scope: deploying the design → Security systems integration; a hands-on test of whether your defences can be bypassed → Security audits and penetration testing.

How we prepare the design at ZeroLayer

Inventory

We collect data on tools, licences, logs and coverage.

Workshop with your IT team

We agree how the environment runs day to day and what must not change.

Design

We prepare the target architecture, the gap map and the rollout plan.

Review and sign-off

We go through the design with your team and hand over the final version.

What you get

  • Inventory report: tools, licences, coverage, gaps and overlaps
  • Target architecture design with the reasoning behind every decision
  • Staged rollout plan with order and dependencies
  • KSC Act and NIS2 requirements map: requirement, mechanism, where the evidence is produced
  • List of licences to retire or consolidate

Who it is for

  • Companies and institutions with many tools from different vendors where nobody sees the whole picture
  • Organisations preparing a security purchase or tender that want to know what they actually need
  • Organisations getting their environment in line with regulations and standards such as NIS2, the KSC Act, the DORA regulation or ISO 27001

When it is not the right choice: when you already know exactly what to deploy and need someone to do it. Then choose Security systems integration.

Frequently asked questions

How is an architecture design different from a security audit?

A design answers which tools and connections you need and in what order to switch them on. An audit, meaning a penetration test, checks with a hands-on attack whether your current defences can be bypassed. Audit results often feed into the design, and after deployment an audit confirms the result.

Does the design include deployment?

No. Security architecture ends with a document: the design, the gap map and the rollout plan. You can deploy it with your own team or hire someone to do it. With us that is a separate service: Security systems integration. In the public sector, design and deployment are often procured separately, so this split makes the tender easier to prepare.

How does the design help with the KSC Act and NIS2?

Logging, retention and the decision path are designed from the start so that they produce evidence that your controls work. You get a map of requirement, mechanism and where the evidence is produced, so there is no documentation to write up before an inspection.

Let's look at what you already have before you buy another tool.

We reply to sales enquiries within 24 hours.

Customer support +48 662 588 820

Related services

Security systems integration: when the design is ready and needs deploying.

Security audits and penetration testing: when you want to test your current setup with a hands-on attack.