Obligations not translated into work and budget
A company may have obligations under the KSC Act and the NIS2 Directive, and nobody says what this changes for its work and budget.

A conversation, an analysis, an offer
The conversation about the problem is free of charge. The analysis under a non-disclosure agreement (NDA) has a defined scope and deadline, and its cost is credited towards the implementation.
Let's talk about your projectAI models and agents in an energy company's processes, maintained after launch.
ERP, CRM, document recognition, automation of debt collection and of financial product distribution.
A digital insurance platform and online policy sales on a global scale.
Inter-operator systems built to the TM Forum industry standard, a wholesale operator's product catalogue and infrastructure monitoring.
An AI platform run as a medical device under FDA, CE and MDR rules, on the EU and US markets.
An ERP with risk analysis for container trade and an intranet with company knowledge management.
JIRA customisation and automation of HR, IT and legal processes in public administration.

Close to 30 projects in the team's experience, seven sectors
One collection, three filters: sector, topic and service.
See the work
We check which obligations under the Polish National Cybersecurity System Act (KSC) and the NIS2 Directive apply to your company, and put them into practice in documents, the system and contracts.
Scopes
A written answer on whether the Polish National Cybersecurity System Act (KSC) covers your company, what obligations and deadlines follow from it, what is missing and in what order to fill the gaps.
See the scopeThe documents required by the Polish National Cybersecurity System Act (KSC), written with the people who will use them, and an application for entry in the register of entities ready to sign.
See the scopeKSC and NIS2 requirements written into the scope and acceptance of the system you are building or ordering, with evidence for the audit gathered during the project.
See the scopeA list of the suppliers your company's operations depend on, an assessment of each of them, and requirements for contracts and requests for proposal that match the obligations under the Polish National Cybersecurity System Act (KSC).
See the scopeSituations
A company may have obligations under the KSC Act and the NIS2 Directive, and nobody says what this changes for its work and budget.
The rules are written down in internal regulations, while the process they cover runs in a system that knows nothing about them. During an inspection someone reconstructs by hand who made a decision and why.
You are building a system whose output affects decisions covered by legislation, for example on a patient's treatment. Requirements added after launch mean rebuilding a working system with another budget.
Scope
We check which KSC and NIS2 obligations apply to your company and which you do not meet today. The result is a gap report with a list of actions.
We write information security policies and procedures, including the incident reporting path, together with the people who will apply them. The result is a full set of documents for adoption by the management board.
We carry the requirements from the policies into the system we are building or modernising: access control, event log, backups. The result is a system whose event log serves as evidence during an inspection.
We review your supplier contracts and check whether they allow you to meet your KSC and NIS2 obligations. The result is a list of clauses to change, with the reasons.
Technologies and standards: The KSC Act, the NIS2 Directive, SZBI (ISMS); access control, event log, backups.
Outcome
Process
We compare your business profile, systems and suppliers with the KSC and NIS2 obligations. Result: a gap report with a list of actions.
Policies, procedures and the division of roles are drawn up together with the departments they concern. Result: a full set of documents with a division of roles.
We implement the safeguards in the system, hand you the contract changes to negotiate with your suppliers and collect the evidence of compliance in one place. Result: the system, contracts and evidence ready for audit.
Services
Book a meeting
You describe the process or system that no longer keeps up and what has to change. The conversation costs nothing.
Phone: +48 455 406 404
Regulations
Obligations under the KSC Act and the NIS2 Directive cover entity registration, policies and procedures, supplier contracts and incident handling. Whether and from when they apply to you depends on the sector and the state of the law. One team handles both the legal side and the system; legal opinions are issued by the law firm we work with. Your company's data can stay in the European Union.
Work
A client in the healthcare sector was building an AI platform to support treatment. Software that affects treatment is a medical device, and obligations towards the regulator continue after it enters the market.
Our team built the platform as a medical device under FDA, CE and MDR: regulators' requirements were part of the system's scope. We build KSC and NIS2 obligations into systems the same way.
FDA, CE and MDR requirements were met during the build, not added afterwards.
You describe the process or system that no longer keeps up and what has to change. The conversation costs nothing.
We examine the process and the systems and hand over a recommendation with a scope of work. You know the scope, deadline and price of the analysis before it starts.
You receive the scope, team, schedule and price of the implementation. You decide whether we go ahead.
The cost of the analysis is credited towards the implementation if you order it.
Phone: +48 455 406 404 E-mail: contact@aliaxit.com
This site uses cookies that are necessary for it to work and, with your consent, analytics cookies that help us count visits. The details are in the Privacy policy.
Choose the categories you consent to. You can change your decision at any time via the ‘Cookie settings’ link in the footer.