Service

Cybersecurity readiness review

The first step for an organisation that wants to know where it stands and what to do first, whether or not the NIS2 and KSC rules apply to it. In 2.5 days we check the actual state and hand over a prioritised list of gaps and a 90-day action plan.

  • 2.5 days

    of work for the whole review

  • 90 days

    the action plan you receive at the end

  • 3 April 2027

    deadline for essential and important entities to meet their obligations

What you get

  • Clarity about obligations

    We check whether your organisation is subject to the Polish National Cybersecurity System (KSC) rules and whether its status on the KSC register is correct. If it is not covered, risk and good practice are the reference point.

  • A picture of the actual state

    Interviews with key people and a review of documents and day-to-day practice, not only of what the procedures say.

  • A prioritised list of gaps

    Each gap is prioritised by risk and requirements, so you know what is urgent and what can wait.

  • A 90-day action plan

    Concrete steps in order of execution, discussed with management.

Who it is for

  • Organisations that want to start without a large project.
  • Companies whose clients require evidence of security.
  • Organisations that are not covered by the regulations but want to put their security in order.
  • Entities on the KSC register before or during implementation.

How the review works

  1. Initial conversation

    What we do

    We agree the scope, the people to interview and the list of documents. We give you a fixed price before any work starts.

    What we need from you

    About 30 minutes of the person who decides on the engagement.

  2. Interviews

    What we do

    We talk to management, to the person responsible for IT or your IT provider, to finance and to the owners of key processes. We ask what has to work for the organisation to work and who is responsible for what.

    What we need from you

    Usually 4 to 6 conversations of 45 to 90 minutes, on site or remotely.

  3. Review of documents and practice

    What we do

    We compare what is written down with how things really are. For example, we check whether administrator accounts use a second authentication factor, when a backup was last restored and whether the account of someone who left was disabled.

    What we need from you

    Documents from the list and short on-screen demonstrations. We do not need passwords or administrator accounts.

  4. Discussion with management

    What we do

    We present the list of gaps and the 90-day plan, answer questions and agree who on your side is responsible for the next steps.

    What we need from you

    60 to 90 minutes of management's time.

The review is 2.5 days of our work, usually spread over 2 to 3 calendar weeks. The pace depends mainly on the availability of your people.

What we check

We base the scope on the areas of measures that the KSC Act and the NIS2 directive require of essential and important entities, but we describe them in business terms. That is why the review makes sense even when your organisation is not covered by the regulations.

  • Governance and roles

    Who decides on security, who is responsible for it and whether management has a budget for it.

  • Risk

    Whether you know what could bring the organisation to a halt or rob it, and which systems are critical.

  • Access and accounts

    Permissions, a second authentication factor, administrator accounts and disabling accounts when employees leave.

  • Systems and updates

    An inventory of hardware and software, updates, and protection of email and workstations.

  • Backups and business continuity

    Whether backups are separated, whether anyone has restored them and how long the organisation can withstand downtime.

  • Incidents and reporting

    Who responds, whom they notify and whether the organisation can meet reporting deadlines.

  • Suppliers and cloud

    Which suppliers have access to your systems, what the contracts say and what the cloud provider is responsible for.

  • People and fraud

    Training, rules for verifying a changed bank account number and whether staff know how to report a suspicious event.

  • Data and encryption

    Where the most important data is, who has access to it and whether laptops and storage media are encrypted.

What the list of gaps looks like

Each gap has a description of the current state, its possible impact in business terms, a priority, a recommendation and a deadline. Here are three rows from a list prepared for a fictional company.

  • Area
    Access and accounts
    What we found
    Microsoft 365 administrator accounts without a second authentication factor.
    Possible impact
    One phished password gives access to the email and data of the whole company.
    Priority
    Urgent
    Recommendation
    Enable multi-factor authentication for administrators, then for all accounts.
    Deadline
    within 2 weeks
  • Area
    Backups and business continuity
    What we found
    Backups run daily, but no one has restored them for over a year.
    Possible impact
    After a ransomware attack it may turn out that the backup does not work or that restoring takes weeks.
    Priority
    High
    Recommendation
    Do a trial restore of a key system and record how long it took.
    Deadline
    within 30 days
  • Area
    Suppliers and cloud
    What we found
    No list of suppliers with remote access to systems.
    Possible impact
    An incident at a supplier spreads to the company, and no one knows whose access to cut off.
    Priority
    Medium
    Recommendation
    List suppliers with remote access and name a contact person at each.
    Deadline
    within 60 days

An example from a fictional company. In the report for your organisation, each gap also has an owner on your side.

The 90-day plan

The plan puts the gaps in order of execution, so that the biggest risks are closed first at the lowest cost.

  • Days 1 to 30

    Quick actions that need no purchases, such as a second authentication factor for administrators or a rule for verifying a changed bank account number.

  • Days 31 to 60

    Decisions and documents that need management: roles, budget, a list of critical suppliers and an incident handling procedure.

  • Days 61 to 90

    Checking that it works: a backup restore test, a short incident exercise and a plan for the next period.

What we need from you

Before the interviews we ask for the documents you already have. Not all of them have to exist, and a missing document is information too.

  • Security policies and procedures, even outdated ones.
  • A list of IT systems and services and of the companies that manage them.
  • Contracts with key IT and cloud suppliers.
  • Information about backups and the last restore test.
  • A description of incidents from the last two years, if there were any.
  • If your organisation may be covered by KSC: headcount, turnover and balance sheet total, and whether it belongs to a group of companies.

Three terms from the report

  • Gap

    The difference between how things are and how they should be according to risk, contracts or regulations. A gap is not an accusation, just an item on the to-do list.

  • Risk

    An event that could harm the organisation, assessed by two things: how much harm it would do and how likely it is. A hijacked board mailbox is a risk, and a missing procedure is a gap that increases it.

  • Priority

    The order of actions that follows from risk and deadlines, not from what is easiest to buy. Urgent means weeks, not quarters.

Fixed scope, independent assessment

The review has a fixed scope and a fixed price, which we give you in the first conversation. We advise independently of vendors and do not sell licences or hardware, so the list of gaps is not a sales offer for products.

What happens after the review

The 90-day plan stays with you. You can carry it out yourself or with us, as part of implementation. The review fee is credited towards implementation or ongoing support.

What the review is not

The review is not a statutory audit within the meaning of Article 15 of the Polish National Cybersecurity System Act. It is a diagnosis that shows where to start.

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