Concept list
skos:ConceptScheme
CyFun 2025 — Delta BASIC→IMPORTANT (new requirements)
- Dataset
- CyFun Requirements
Concepts in this list
-
Other concepts
skos:inScheme -
- Cybersecurity and information security events shall be reviewed and analysed to identify potential attack targets and methods, in accordance with applicable laws, regulations, standards, and policies.
- The organisation shall ensure that event data from critical systems is collected and correlated using information from multiple relevant sources.
- Information about adverse events shall be promptly delivered to authorised person- nel and systems to enable timely detection, investigation, and response.
- Incidents shall be reported when adverse events meet defined and documented incident criteria.
- The organisation shall monitor and identify unauthorised use of its business critical systems through the detection of unauthorised local connections, network connec- tions and remote connections.
- The physical environment shall be monitored to find potentially adverse events.
- End point and network protection tools that monitor end-user behaviour for danger- ous activity shall be managed.
- External service provider activities and services shall be secured and monitored to find potentially adverse events.
- External service providers' conformance with personnel security policies and procedures and contract security requirements shall be monitored relative to their cybersecurity risks.
- The organisation shall monitor computing hardware, software, runtime environ- ments, and their data to detect potentially adverse events.
- The organisation's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management.
- Legal, regulatory, and contractual obligations related to information and cyber- security shall be continuously managed to ensure they remain accurate, up to date, and effectively applied.
- The organisation shall identify, document, and communicate the critical objectives, capabilities, and services relied upon by external stakeholders, prioritise them based on criticality, and integrate this prioritisation into the risk assessment process
- The organisation shall define and document cybersecurity requirements for essential operations, validate them through testing and audits, maintain records of results and corrective actions, and regularly update requirements based on evolving risks
- The organisation shall identify, document, and communicate its role in the supply chain, including the external capabilities, services, and dependencies it relies on (upstream), as well as its interactions with downstream stakeholders.
- Organisational-wide information and cybersecurity policies and procedures shall include the use of cryptography and, where appropriate, encryption, reflect changes in requirements, threats, technology and organisational roles, and be approved by senior management, who oversee its implementation. This control builds further on GV.PO-01.1 and focuses on the content and oversight of the cyberand information security policies themselves. It ensures that specific technical topics (such as cryptography and encryption) are addressed, policies are responsive to change and Senior leadership is actively involved in approval and oversight. Consider the following elements to be covered: · Define Scope & Objectives Ensure policies apply organisation-wide and align with business and risk priorities. · Include Cryptography & Encryption · Address encryption at-rest/in-transit, key management, and approved algorithms. · Define where encryption is required (e.g., personal data, remote access). · Keep Policies Current Update policies to reflect changes in: · Legal/regulatory requirements · Threat landscape · Technology · Organisational structure · Senior Management Oversight · Require formal approval by senior leadership. · Assign a policy owner (e.g., CISO) to oversee implementation and compliance. · Assign Roles & Responsibilities · Use ENISA ECSF Role Profiles https://www.enisa.europa.eu/publications/european-cybersecurity-skills-framework-role-profiles) to: · Define cybersecurity roles (e.g., Policy Officer, Risk Manager) · Align tasks, skills, and competencies · Communicate & Train Disseminate policies and provide role-specific training. · Monitor & Enforce Use technical controls and audits to ensure compliance.
- Information/cybersecurity objectives shall be identified, agreed to by organisational stakeholders and approved by senior management
- Risk appetite and risk tolerance statements shall be defined, documented, approved by senior management, communicated, and maintained.
- Information and Cybersecurity risks shall be documented, as part of the enterprise risk management processes, formally approved by senior management, and updated when changes occur.
- A high-level plan or vision shall be formally established and clearly communicated to everyone involved on how to manage risks, including the different strategies the organisation can employ to deal with identified risks based on risk appetite or risk tolerance level.
- To support the high-level risk management vision, the organisation shall establish clear lines of communication for cybersecurity risks, including those arising from suppliers and third parties.
- Information security and cybersecurity roles, responsibilities and authorities for employees, suppliers, customers, and partners shall be documented, reviewed, author- ised, kept up to date, communicated, and coordinated internally and externally.
- A cybersecurity process for human resources shall be developed and maintained applicable at recruitment, during employment and at termination of employment.
- Third-party providers shall notify any transfer, termination or transition of personnel with physical or logical access to business-critical system elements of the organisation.
- Requirements for addressing cybersecurity risks and the sharing of sensitive infor- mation in supply chains shall be established, prioritised, integrated into contracts and other types of formal agreements, and enforced.
- The risks posed by a supplier, its products and services and other third parties shall be identified, documented, prioritised, mitigated and assessed at least annually and when changes occur during the relationship.
- The organisation shall identify and document key personnel from relevant suppliers and other third parties to include them in incident planning, response, and recovery activities.
- The inventory of enterprise assets associated with information and information processing facilities shall reflect changes in the organisation’s context and include all information necessary for effective accountability.
- When unauthorised hardware is detected, it shall be quarantined for possible excep- tion handling, removed, or replaced, and the inventory shall be updated accordingly.
- The inventory reflecting which software, services and systems are used in the organisation shall reflect changes in the organisation’s context and include all information necessary for effective accountability.
- The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified.
- When unauthorised software is detected, it shall be quarantined for possible excep- tion handling, removed, or replaced, and the inventory shall be updated accordingly.
- Organisations shall keep a clear and up-to-date list of all external services it uses, including how they connect to their systems. These services shall be reviewed and approved before use, and the list shall be updated whenever changes happen.
- Inventories of data and associated metadata shall be maintained for designated data types.
- Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged.
- Setting up non-local maintenance and diagnostic sessions over remote network connections shall require strong authenticators and such connections shall be terminated when non-local maintenance is completed.
- The organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.
- The organisation shall ensure that the necessary measures are taken to deal with loss, misuse, damage, or theft of assets.
- The organisation shall plan, perform and document preventive maintenance and repairs on its critical system components according to approved processes and tools.
- The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems.
- Security tests and exercises, including those conducted with suppliers and relevant third parties, shall be used to identify areas for improvement.
- The organisation shall incorporate lessons learned from incident handling activities into updated or new incident handling processes and/or procedures that are framed by appropriate training after review, approval and testing.
- The organisation shall identify improvements derived from the monitoring, measure- ments, assessments, and lessons learned and consequently translate this into improved processes / procedures / technologies to enhance its cyber resilience (continuous improvement).
- The organisation shall collaborate and share information about its critical system's related security incidents and mitigation measures with designated partners.
- Communication of effectiveness of protection technologies shall be shared with relevant stakeholders.
- The organisation shall implement, where feasible, automated mechanisms to facilitate the process of information sharing and collaboration.
- Contingency and continuity plans shall be established, communicated, maintained, tested, validated, and improved.
- A process shall be established to continuously monitor, identify, and document vul- nerabilities of the organisation's business critical systems.
- The organisation shall establish and maintain a documented process that enables continuous review, analysis and remediation of vulnerabilities and provides for information sharing where applicable.
- Vulnerability scanning shall not adversely impact system functions.
- Vulnerabilities shall be identified and managed in all relevant assets, including soft- ware, network and system architectures, and facilities.
- A threat and vulnerability awareness program that includes a cross-organisation information-sharing capability shall be implemented.
- Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.
- The organisation shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and likelihood of their occurrence.
- Risk responses shall be identified, prioritised, planned, tracked and communicated.
- The organisation shall establish and implement a vulnerability management plan to identify, analyse, assess, mitigate and communicate all types of vulnerabilities including in the form of a Coordinated Vulnerability Disclosure (CVD) according to applicable legal modalities.
- Identities and credentials for authorised users, services and hardware shall be managed through automated mechanisms whenever feasible.
- The organisation shall implement documented procedures for verifying the identity of individuals before issuing credentials that provide access to the organisation's systems.
- The organisation shall define, document, and implement usage restrictions, connec- tion requirements, and authorisation procedures for remote access to its critical systems. These controls shall ensure that only approved users can connect, using secure methods, with access limited to what is necessary for their role.
- Where technically, operationally, and economically feasible — without compromising system integrity, safety, or compliance — automated mechanisms shall be imple- mented to manage user accounts on critical ICT and OT systems. Feasibility shall be determined based on system capabilities, integration potential, risk assessment, and business impact.
- Separation of duties (SoD) shall be ensured in the management of access rights.
- Privileged users shall be managed and monitored.
- Physical access controls shall include specific procedures for emergency situations, ensuring continued protection of critical and non-critical assets during such events.
- The organisation shall include insider threat awareness and reporting in its cyber- security training to help personnel recognise and respond to potential internal risks.
- Personnel shall receive training to understand their specific roles, responsibilities, and priorities during a cybersecurity or information security incident, including the steps they need to follow to respond effectively.
- Members of management bodies shall be able to demonstrate that they have com- pleted training that gives them a solid understanding of information and cybersecurity and risk management so that they can assess information and cybersecurity risks and their consequences and propose the necessary risk mitigation, considering their roles, responsibilities and authorities.
- Individuals in specialised roles shall be provided with awareness and training before privileges are granted, so that they possess the knowledge and skills to perform rel- evant tasks with cybersecurity risks in mind.
- Privileged users shall be qualified before privileges are granted, and these users shall be able to demonstrate the understanding of their roles, responsibilities, and authorities.
- The organisation shall implement software, firmware, and information integrity checks to detect unauthorised changes to its critical system components during storage, transport, start-up and when determined necessary.
- The organisation shall define and enforce clear policies and practical safeguards to manage and restrict the use of portable storage media, in order to reduce the risk of data leakage, unauthorised access, and malware introduction.
- The organisation shall only allow the use of removable media when absolutely necessary and shall put technical measures in place to block automatic execution of files from these devices.
- The reliability and integrity of backups shall be verified and tested regularly.
- The organisation shall maintain secure backups of business-critical data in a separate storage location to ensure data availability in case of system failure or data loss. Backup storage shall apply equivalent security controls as the primary environment.
- To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its critical systems.
- The organisation shall implement appropriate boundary protection measures to monitor and control communications at external and key internal boundaries of its critical systems, across both IT and OT environments, to ensure secure and reliable operations.
- The organisation shall define, implement and maintain policies and procedures related to emergency and safety systems, fire protection systems and environmental controls for its critical systems.
- A dequate resource capacity planning shall ensure that availability of organisation's critical system information processing, networking, telecommunications, and data storage is maintained.
- The organisation shall develop, document, and maintain a baseline configuration for its business critical systems.
- The organisation shall enforce restrictions on software usage and installation, and ensure that software is maintained, replaced, or removed based on its associated risk.
- Hardware used in business-critical environments shall be maintained, replaced, or removed based on its associated security and operational risk.
- The organisation shall ensure that logbook records contain an authoritative time source or internal clock time stamp that is compared and synchronised with an authoritative time source.
- A udit data from the organisation's critical systems shall be moved to an alternative system.
- Installation and execution of unauthorised software shall be prevented.
- Security shall be considered throughout the lifecycle of systems and applications, whether developed internally or acquired externally.
- Changes and exceptions shall be tested and validated before being implemented into operational systems.
- Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures.
- Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established procedures.
- The integrity of restored systems and assets shall be verified before they are returned to service. Systems and services shall be fully restored, and normal operations shall be confirmed.
- Cybersecurity incidents shall be shared with relevant external stakeholders within the timeframes defined in the Incident Response Plan, including reporting significant incidents to authorities as required by law.
- The organisation shall coordinate information/cybersecurity incident response actions with all predefined stakeholders.
For people working with the data
http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT
All data (5 statements)
Properties and relations
Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
A set of concepts, optionally including statements about semantic relationships between those concepts. |
|
A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag. |
CyFun 2025 — Delta BASIC→IMPORTANT (new requirements) |
|
The number of triples associated with the subject. |
3 |
|
Specifies the dataset the subject is part of. |
|
References
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |