1. KSC and NIS2 – new obligations of essential and important entities
NIS2 and the amended KSC define who falls within the new regulatory framework and what follows from that status. The section explains essential and important entities, rules for determining status, register-related duties, data updates and loss of status, implementation deadlines, and the role of authorities and CSIRTs.
- the most important assumptions of the NIS2 Directive and the amended Act on the National Cybersecurity System,
- essential entity and important entity – who the new requirements apply to,
- principles for identifying the organization's status,
- obligations related to entry and updating data in the register of essential and important entities,
- change of data and loss of the status of an essential or important entity,
- deadlines for fulfilling obligations arising from the KSC,
- the role of competent authorities for cybersecurity and CSIRT.
2. Responsibility of the manager of a key or important entity
Under Art. 8d KSC, managerial accountability extends beyond delegation of day-to-day cybersecurity tasks. This part clarifies the responsibility of the manager and collective bodies, the scope of decision-making and supervision duties, compliance with internal and statutory requirements, and consequences of non-performance.
- the manager's responsibility for the implementation of cybersecurity obligations,
- the scope of responsibility of members of collective bodies,
- the possibility of entrusting part of the obligations to other persons and the manager's responsibility,
- the most important obligations of the manager resulting from Art. 8d KSC,
- making decisions regarding cybersecurity,
- supervision over the organization's implementation of obligations,
- ensuring the organization's compliance with KSC and internal regulations,
- the consequences of failure to perform obligations.
3. Information security management system – obligations of the organization and the manager
An information security management system defines how the organization governs cybersecurity on an ongoing basis. The section explains duties related to identifying critical systems and processes, assigning responsibility, selecting technical, operational and organizational measures, documenting rules, and monitoring and improving control effectiveness.
- obligation to implement an information security management system,
- identification of systems, processes and resources essential for the provision of services,
- defining responsibility for cybersecurity,
- cybersecurity risk management,
- selection of adequate technical, operational and organizational measures,
- documenting security principles and procedures,
- monitoring the effectiveness of the applied safeguards,
- periodic review and improvement of the security system.
4. Cybersecurity risk management
Risk management connects managerial decisions with concrete safeguards for systems and data. Participants examine threat and vulnerability identification, assessment of likelihood and impact, risk acceptance, treatment decisions, and key protection areas such as access control, identity management, MFA, patching, and encryption.
- identification of threats and vulnerabilities,
- assessment of the probability and effects of threats occurring,
- determining the level of acceptable risk,
- making decisions regarding the method of dealing with risk,
- security of infrastructure, networks and information systems,
- vulnerability and update management,
- access security and identity management,
- multifactor authentication and permission control,
- encryption and protection of data and information.
5. Supply chain security and cooperation with suppliers
Supplier relationships can transfer significant cyber risk into the organization if they are not governed properly. This section addresses secure procurement, supplier and service provider assessment, contractual security requirements, oversight of third parties, ICT service security, and incident response on the supplier side.
- risks resulting from cooperation with technology and service suppliers,
- cybersecurity in the procurement process,
- assessment of suppliers and service providers,
- security requirements in contracts,
- supervision of external entities,
- security of ICT services and services provided by third parties,
- responding to incidents occurring on the suppliers' side.
6. Organization of cybersecurity and staff responsibility
Clear assignment of roles is essential when cybersecurity obligations are distributed across the organization. The section covers task allocation, responsibilities, authorities and supervision, requirements for personnel involved in information systems security, staff verification, competence development, internal rules, and security culture.
- assignment of tasks in the field of cybersecurity,
- defining roles, responsibilities and authorizations,
- supervising the implementation of assigned tasks,
- requirements for persons carrying out tasks in the field of information systems security,
- verification of persons allowed to perform specific tasks,
- ensuring staff competence and awareness,
- internal cybersecurity regulations,
- building a security culture in the organization.
7. Resource planning and cybersecurity financing
Limited budgets force management to align cybersecurity spending with actual risk exposure. This part addresses responsibility for securing adequate resources, planning funding for KSC obligations, setting investment priorities, making trade-offs under constraints, and documenting management decisions on resource allocation.
- the manager's responsibility for ensuring adequate resources,
- planning adequate financial resources for the implementation of KSC obligations,
- determining priorities for security investments,
- making decisions in a situation of a limited budget,
- the relationship between the level of risk and expenditure on cybersecurity,
- documenting management decisions.
8. Contemporary threats and real attack scenarios
Current attack patterns show how technical weaknesses and user manipulation combine in practice. The section maps the contemporary threat landscape, including phishing, spear phishing, ransomware, account takeover, supply chain compromise and social engineering, together with the business impact of cybersecurity incidents.
- current cybersecurity threat landscape,
- phishing and spear phishing,
- ransomware,
- user account takeover,
- supply chain attacks,
- social engineering and user manipulation,
- the most common organizational and technical errors,
- the impact of a cybersecurity incident on the organization's operations.
9. Workshop – analysis of a real cyberattack scenario
Through a realistic attack scenario, participants examine how a cyber incident develops in operational and business terms. The workshop analyzes phishing, account takeover and ransomware escalation, identifies attack symptoms and vectors, and focuses on management decisions and first-hour response activities.
- analysis of a phishing message,
- identification of attack symptoms,
- user account takeover scenario,
- course of a sample ransomware attack,
- analysis of the attack vector and its escalation,
- determining potential business consequences,
- decisions that the organization's manager should make,
- actions of the organization in the first hours after detecting the incident.
10. Handling and reporting incidents in accordance with the KSC
Handling an incident under KSC requires a defined process from detection to closure. Participants work through classification, division of responsibilities, reporting duties, deadlines and report content, cooperation with the competent CSIRT, incident updates, final reporting, and documentation of the entire course of events.
- organization of the incident handling process,
- identification and classification of the incident,
- division of responsibilities during incident handling,
- obligations related to incident reporting,
- deadlines and stages of reporting,
- scope of information provided in reports,
- cooperation with the competent CSIRT,
- updating information concerning the incident,
- final report and post-incident actions,
- documenting the course of the incident.
11. Crisis management and business continuity
To maintain operations during disruption, organizations need more than incident response alone. This section focuses on business continuity and disaster recovery plans, backups and data restoration, crisis communication, management roles during major incidents, time-critical decision-making, and post-incident corrective measures.
- ensuring the continuity of the organization's operations,
- business continuity and disaster recovery plans,
- backups and data recovery,
- response to failures and large-scale incidents,
- internal and external communication in a crisis situation,
- management roles in a major incident situation,
- decision-making under time pressure,
- conclusions and corrective actions after the incident.
12. Information obligations and cooperation with users and authorities
Effective compliance depends not only on internal measures, but also on timely external communication. The section covers information duties under KSC, communication with service recipients, cooperation with competent authorities and CSIRTs, and organizational readiness to provide required records during an inspection or summons.
- information obligations resulting from the KSC,
- informing about cyber threats and incidents,
- communication with service recipients,
- cooperation with the authority competent for cybersecurity,
- cooperation with the competent CSIRTs,
- preparing the organization for an inspection or summons from the authority,
- ensuring the availability of the required documentation and information.
13. Audits, control and documentation of compliance
When compliance must be demonstrated, documentation and control mechanisms become central. This part explains preparation for KSC inspections and security audits, reviews of safeguard effectiveness, identification of non-conformities, planning corrective actions, supervision of recommendations, and reporting to management.
- preparation of the organization for control of the implementation of KSC obligations,
- the role of documentation in demonstrating compliance,
- reviews and assessment of the effectiveness of the safeguards applied,
- obligations related to the security audit,
- identification of non-conformities and planning of corrective actions,
- supervision of the implementation of recommendations,
- reporting the state of cybersecurity to the management.
14. ISO 27001 and the system approach to security
ISO 27001 provides a structured model for organizing cybersecurity beyond isolated controls. The training links the standard with KSC requirements, explains roles, policies and security controls within an ISMS, and shows how risk-based management supports continuous improvement.
- basic assumptions of ISO 27001,
- the relationship between the information security management system and the requirements of the KSC,
- risk management based on the system approach,
- roles, procedures, policies and security controls,
- continuous improvement of the cybersecurity system.
15. Cybersecurity and the use of AI
AI and LLM adoption introduces specific security and governance challenges that managers must control. The section addresses data leakage, prompt injection, deepfake-driven social engineering, criminal use of AI, internal rules for safe use, and the basic assumptions of ISO 42001.
- main risks related to the use of AI and LLMs,
- protection of data provided to AI tools,
- information leaks and uncontrolled use of data,
- prompt injection and other AI-related threats,
- use of AI by cybercriminals,
- deepfake and new forms of social engineering,
- rules for the safe use of AI tools by employees,
- AI governance in the organization,
- basic assumptions of ISO 42001.
16. Workshop for the manager – assessment of the organization's readiness to meet KSC requirements
Using a sample organization, the workshop evaluates how far current practice meets KSC requirements. Participants identify organizational and technical gaps, define managerial and operational responsibilities, assess key risks, and build a prioritized list of corrective actions with clear ownership.
- analysis of a sample organization in terms of KSC obligations,
- identification of the most important organizational and technical gaps,
- definition of the responsibility of the manager and persons carrying out tasks,
- identification of key risks,
- definition of actions requiring priority implementation,
- creation of a list of corrective actions,
- determination of priorities and responsibilities.
17. Checklist of the manager of a key or important entity
A practical management checklist translates KSC duties into concrete governance actions. It covers decisions to be made, formal task allocation, required procedures, management reporting, incident-related duties, and regular supervision, while also showing how to document compliance and prepare for audit or inspection.
- what decisions the manager should make,
- what tasks should be formally assigned,
- what procedures and documents should function in the organization,
- what information should reach the management,
- what activities should be regularly supervised,
- what obligations concern incident reporting,
- how to document the fulfillment of obligations,
- how to prepare the organization for an audit or inspection,
- the most important actions to implement after the training.