Service

Implementation of cybersecurity requirements

We implement security in modules, in the order that follows from the readiness review, whether or not NIS2 and KSC apply to your organisation. You pay for what you really need, and the documents describe the actual state.

  • 6 modules

    to choose from based on the list of gaps

  • 24 and 72 hours

    incident reporting deadlines built into the procedure

  • 3 April 2027

    deadline for essential and important entities to meet their obligations

Modules

We set the scope and order of modules based on the list of gaps from the readiness review.

  • Security policy and roles

    Who is responsible for what, from the board to IT suppliers.

  • Risk analysis

    Risks to your services and systems, with decisions on how to treat them.

  • Business continuity with a tabletop exercise

    Continuity and recovery plans, tested in an exercise with your team.

  • Incidents and reporting

    An incident handling procedure, reporting within 24 and 72 hours, and the final report.

  • Supplier security

    Requirements for suppliers and how to verify them.

  • Board training

    Management obligations and accountability, in practice.

Who it is for

  • Organisations that have completed a readiness review and have a list of gaps and a 90-day plan.
  • Companies whose clients require evidence of security.
  • Organisations that are not covered by the regulations but want to build security in proportion to their scale.
  • Essential and important entities, which have until 3 April 2027 to meet their obligations.

How implementation works

  1. Starting point

    We start from the list of gaps and priorities from the readiness review.

  2. Choice of modules

    We agree which modules are needed and in what order.

  3. Work with your team

    Documents and procedures are based on how the organisation works day to day, not on a template.

  4. Tested in practice

    We test continuity and recovery plans in a tabletop exercise with your team.

  5. Keeping it running

    After implementation we offer ongoing support, so the system keeps working after the project ends.

The modules up close

Each module has its own scope, workshops and a concrete result. Expand a module to see the details.

    • We agree who decides on security, who coordinates it and what belongs to the IT provider.
    • We write down the rules the organisation really follows or will start to follow, instead of copying a ready-made template.
    • We prepare a board decision that approves the policy and assigns roles.

    What we need from you: management for about an hour and the person who will coordinate security.

    What you get: a concise security policy, a split of roles and responsibilities and a draft board decision.

What a risk register looks like

The register shows what could harm the organisation, how badly, what we do about it and who is responsible. Here are three rows from the register of a fictional company.

  • Scenario
    Ransomware encrypts the server running the sales system
    Impact
    No sales for 3 to 5 days and contractual penalties
    Likelihood
    Medium
    Risk level
    High
    Decision
    Reduce
    Action and deadline
    Separated backup and a restore test, by the end of the quarter
  • Scenario
    Accounting mailbox takeover and a changed bank account number
    Impact
    A lost transfer and a dispute with a client
    Likelihood
    High
    Risk level
    High
    Decision
    Reduce
    Action and deadline
    Multi-factor authentication and a rule for verifying account changes, 2 weeks
  • Scenario
    Outage at a cloud service provider
    Impact
    A few hours of downtime
    Likelihood
    Low
    Risk level
    Medium
    Decision
    Accept
    Action and deadline
    Board decision recorded in the register, review in a year

An example from a fictional company. In the register for your organisation, each risk also has an owner.

A sample schedule

  1. Month 1

    What we do

    Policy and roles, an inventory of services, systems and suppliers, the first risk workshop.

    What is ready

    Approved roles and policy.

  2. Month 2

    What we do

    Risk analysis and impact analysis, assessment of critical suppliers.

    What is ready

    A risk register with board decisions.

  3. Month 3

    What we do

    Continuity and recovery plan, incident handling procedure, board training.

    What is ready

    Procedures ready to use.

  4. Month 4

    What we do

    Tabletop exercise, improvements after the exercise and handover of documentation.

    What is ready

    A system tested in practice.

This is what implementing all six modules usually looks like. A smaller scope takes less time, and the pace depends mainly on the availability of your people.

Three terms from implementation

  • Business impact analysis

    Establishing how long each key process can be down and how much data can be lost before the consequences become unacceptable. It tells you what to restore first.

  • Tabletop exercise

    An exercise around a table, without switching any systems off: the team gets an incident scenario and decides step by step what to do. It reveals gaps in the plans before a real incident does.

  • Critical supplier

    A supplier without which the organisation stops, or which has access to its systems or data. Such suppliers are assessed more closely and given requirements in the contract.

How we work

  • Documents describe the actual state, not a template for the drawer.
  • We match safeguards to scale and risk.
  • We advise independently of vendors. We do not sell licences or hardware.
  • If you prefer to do part of the work yourself, we offer a package of consulting hours.
  • We do not later carry out a statutory audit of an organisation where we implemented the requirements. This protects the independence of the audit.

Frequently asked questions

Let us talk about the security of your organisation

You do not need to be ready for a large project. A conversation about where you are and what the law requires of you is enough. We will help you plan realistic, workable steps.

Email
contact@isconsulting.pl
Address
ul. Żelazna 51/53, 00-841 Warszawa, Poland