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
Starting point
We start from the list of gaps and priorities from the readiness review.
Choice of modules
We agree which modules are needed and in what order.
Work with your team
Documents and procedures are based on how the organisation works day to day, not on a template.
Tested in practice
We test continuity and recovery plans in a tabletop exercise with your team.
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.
- We list the services and systems the organisation depends on, and their suppliers.
- In a workshop with process owners we assess scenarios, such as ransomware, mailbox takeover or a supplier outage, by impact and likelihood.
- For each significant risk, management decides whether to reduce, transfer, avoid or consciously accept it.
What we need from you: owners of key processes and the person responsible for IT, 2 to 3 hours per workshop.
What you get: a risk register with assessments and decisions, and a risk treatment plan with owners and deadlines.
- Business impact analysis: how long each key process can be down and how much data the organisation can lose.
- Continuity and recovery plan: who does what, in what order and how to work when a system is down.
- Tabletop exercise: the team works through an incident scenario step by step, and we check whether the plan works in practice.
What we need from you: process owners, the person responsible for IT and the IT provider. The exercise takes 2 to 3 hours.
What you get: an impact analysis, a continuity and recovery plan and an exercise report with a list of improvements.
- We agree who assesses an event and who decides on reporting, and for entities on the KSC register also who has an account in the S46 system and who stands in for them.
- We tailor the criteria for a serious incident to the organisation, based on the regulations and the impact analysis.
- We prepare templates for the early warning, the notification and communications, so no one has to write them from scratch at night.
What we need from you: the person responsible for IT, the IT provider and the person responsible for communication.
What you get: an incident handling procedure, criteria, reporting templates and an incident register.
- We list suppliers and identify the critical ones: those without which the organisation stops, or which have access to its systems or data.
- We assess them based on a questionnaire and the documents they already have, such as certificates or audit reports, and point out what those documents do not prove.
- We prepare security requirements for contracts: incident reporting, remote access rules, backups and the right to verify.
What we need from you: the person who knows the supplier contracts and the person responsible for IT.
What you get: a register of critical suppliers with assessments, contract requirements and a reassessment schedule.
- Management obligations, and for entities covered by KSC also personal liability, discussed through examples rather than legal provisions.
- A short exercise: the board decides in an incident scenario whether it is a serious incident and who reports it.
- A list of decisions the board should take in the next quarter.
What we need from you: the whole board at one time.
What you get: materials, an attendance list and named certificates that document the training.
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
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.
Month 2
What we do
Risk analysis and impact analysis, assessment of critical suppliers.
What is ready
A risk register with board decisions.
Month 3
What we do
Continuity and recovery plan, incident handling procedure, board training.
What is ready
Procedures ready to use.
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
We implement in the order that follows from the readiness review, so that is where we usually start. The review fee is credited towards implementation.
No. You pay for what your organisation really needs. The scope follows from the list of gaps.
Yes. If you prefer to do part of the work yourself, we offer a package of consulting hours.
No. We advise independently of vendors and do not sell licences or hardware. We also do not provide operational services such as SOC, SIEM or 24/7 monitoring.
The documents describe the actual state of your organisation, not a template for the drawer.
No. We do not later carry out a statutory audit of an organisation where we implemented the requirements. This protects the independence of the audit.
The cost depends on the number and scope of modules. We give you a quote once the scope is agreed, based on the list of gaps.
We offer ongoing support in one of three tiers, so the system keeps working after the project ends.
All six modules usually take 3 to 4 months. Individual modules take from a few weeks, and the pace depends mainly on the availability of your people.
Each module usually means 1 to 3 workshops of 2 to 3 hours and a review of documents between meetings. For each module we say whom we need.
As editable files that stay with you and that you can keep changing without us.
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.
- contact@isconsulting.pl
- Address
- ul. Żelazna 51/53, 00-841 Warszawa, Poland

