16 November 2026

6 min read

How to Prepare an Information Security Management System for KSC Compliance?

Bartosz Pyrczak

Head of Growth

Linkedin

An Information Security Management System (ISMS) is not simply a collection of policies and procedures. It is a way to manage risk, put security controls in place, and check how well they work. The amended Act on the National Cybersecurity System (KSC) places obligations in this area on essential and important entities. Organizations must therefore not only establish security rules but also demonstrate that they follow them in practice.

Where Should You Start When Building an ISMS for KSC Compliance?

The first step in building an ISMS is to define its scope, assign responsibilities, and establish the rules for managing information security.

Start with a formally approved ISMS scope that identifies the business processes, systems, assets, and organizational units it covers. Management then approves the overarching information security policy, appoints an ISMS owner, and assigns responsibility for risk management and implementing security controls.

A dedicated budget and a register of legal and regulatory requirements are also needed.

These documents provide the foundation for the work ahead. They should make it clear who makes security decisions, who is responsible for carrying them out, and how the organization monitors compliance with its rules.

How Do You Conduct a Risk Assessment Within an ISMS?

Risk assessment should cover business processes, the assets that support them, and threats to the confidentiality, integrity, and availability of information.

Start by mapping business processes, including their criticality, dependencies, and owners. The organization then uses this map to create an information asset register with data classifications and an inventory of technical resources, personnel, and suppliers.

The next step is to establish a risk assessment methodology that defines the criteria, likelihood and impact scales, and risk acceptance thresholds. The findings are recorded in a risk register, while decisions to reduce, avoid, transfer, or accept risks are documented in a risk treatment plan.

Documented acceptance of residual risk by authorized risk owners is particularly important. Rules for escalating risks to management should follow the organization’s established governance model. These records make it possible to identify who decided to tolerate a particular risk.

What Security Controls Must an ISMS Include?

An ISMS should include organizational and technical security controls suited to the results of the risk assessment and the obligations imposed by KSC. Each area should follow a cycle of threat assessment, implementation of protective measures, and verification of their effectiveness.

Identity, People, and Physical Security

Access management includes the principle of least privilege, control over privileged accounts, and the use of multi-factor authentication (MFA) where appropriate. Access rights must be reviewed regularly, and unnecessary permissions must be revoked.

Security measures should also cover physical access to infrastructure and personnel security, including appropriate employee screening, training, and security awareness programs.

Infrastructure, Vulnerabilities, and Monitoring

Organizations should regularly identify vulnerabilities, manage updates, and monitor system configurations. Software that is no longer supported by its vendor requires a risk assessment and appropriate compensating controls.

Network security includes segmentation, traffic control, and secure remote access. These measures are supported by data encryption, cryptographic key management, and appropriate communication standards, such as TLS.

Monitoring involves collecting and analyzing security events. SIEM, EDR, and NDR tools help detect threats, while 24/7 alert handling enables faster responses to suspicious activity.

Business Continuity and IT Process Security

Business continuity planning begins with a Business Impact Analysis (BIA), which identifies critical services and the consequences of their unavailability. This analysis is used to set Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) and prepare Business Continuity Plans (BCP) and Disaster Recovery Plans (DRP).

The effectiveness of these plans should be checked regularly through recovery tests, with the results and any problems identified properly documented.

An ISMS also covers secure software development, security testing, and dependency management. Changes to systems require a risk assessment, appropriate approval, and a rollback plan.

Incident and Supply Chain Management

The system also covers incident handling and documentation, as well as assessing risks associated with suppliers and cloud services.

Both areas require clearly assigned responsibilities, established procedures, and monitoring methods. We discuss their implementation in more detail in separate materials dedicated to KSC.

our service

You Have ISMS Documentation. But Can You Prove the System Works?

Tenesys can help you assess the current state of your ISMS and identify which KSC requirements call for further action.
KSC Gap Analysis and Compliance Audit will help identify gaps in processes, security controls, and documentation, and develop a prioritized remediation plan. This allows your organization to focus its resources on the areas that need improvement.

What Documents and Evidence Demonstrate That an ISMS Is Working?

An ISMS is supported by documents that define security rules and records that demonstrate how those rules are followed.

The first category includes policies, risk assessment methodologies, and operational procedures. The second includes registers, system logs, test reports, and review records.

For example, an auditor may compare the access management policy with the history of changes in the IAM system, the results of access reviews, and records confirming that permissions have been revoked.

Similarly, a disaster recovery plan should be supported by recovery test reports. A vulnerability management procedure should be backed by records of identified vulnerabilities, assigned remediation tasks, and evidence that the issues have been resolved.

Audit evidence should make it possible to determine what action was taken, when it happened, who performed it, and what the outcome was.

How Do You Maintain and Improve an ISMS After Implementation?

Maintaining an ISMS requires regular assessments of security control effectiveness, internal audits, management reviews, and corrective actions.

Organizations should track measurable performance indicators, such as vulnerability remediation times, timely revocation of access rights, and recovery test results. This data helps identify gaps and measure progress.

An internal audit program is used to check whether processes comply with established rules and regulatory requirements. Audit findings should lead to corrective actions, followed by further checks to confirm that the issues have been addressed.

Management reviews must result in documented decisions about risks, resources, and priorities. The ISMS should also include procedures for reporting to the relevant authorities in accordance with applicable regulations.

How Can You Align KSC Requirements With ISO 27001?

An ISMS designed to meet KSC requirements can be based on ISO/IEC 27001:2022. Both frameworks cover risk management, the selection of security controls, internal audits, and management reviews.

Organizations that already have an ISO 27001-compliant ISMS can build on their existing processes, but they should check whether those processes meet the additional obligations imposed by KSC.

The standard requires, among other things, a Statement of Applicability (SoA) identifying the necessary security controls, the reasons for selecting them, their implementation status, and the reasons for excluding any controls listed in Annex A. Certification also requires successfully passing an audit conducted by a certification body.

An ISO 27001 certificate does not automatically demonstrate compliance with KSC. Designing an ISMS to meet both sets of requirements from the outset can therefore reduce the need for later changes to processes and documentation.

How Can You Check Whether Your ISMS Is Ready for KSC Requirements?

The best way to assess ISMS readiness is to start with a gap analysis that compares existing processes, security controls, and audit evidence against KSC requirements.

The result should be a list of gaps and nonconformities, ranked by risk and priority, with responsibilities assigned. This analysis helps distinguish missing documentation from issues that require technical or organizational changes.

Author

Bartosz Pyrczak

Head of Growth

Head of Growth at Tenesys. Connects people, builds relationships, and ensures the company grows in the right direction. Convinced that in IT sales, the one who listens better than they speak wins. Privately a traveler and cyclist.

Linkedin