Concept list
skos:ConceptScheme
CyFun 2025
- Dataset
- CyFun Requirements
Concepts in this list
-
Other concepts
skos:inScheme -
- Asset Management
- Risk Assessment
- Awareness and Training
- Data Security
- Adverse Event Analysis
- Continuous Monitoring
- Incident Response Reporting and Communication
- Incident Analysis
- Incident Mitigation
- Incident Recovery Plan Execution
- Incident Recovery Communication
- Organizational Context
- Oversight
- Policy
- Risk Management Strategy
- Roles, Responsibilities, and Authorities
- Cybersecurity Supply Chain Risk Management
- Improvement
- Identity Management, Authentication, and Access Control
- Technology Infrastructure Resilience
- Platform Security
- Incident Management
- 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 implement automated mechanisms where feasible to review and analyse detected events.
- The logging functionality of protection and detection tools shall be enabled. Logs shall be backed up and retained for a predefined period and regularly reviewed to identify unusual or potentially harmful activity.
- The organisation shall ensure that event data from critical systems is collected and correlated using information from multiple relevant sources.
- The organisation shall combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility moni- toring, where feasible.
- The organisation shall assess the negative impacts of detected events on its oper- ations, assets, and individuals, and shall link these impacts to the results of its risk assessments.
- 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.
- Firewalls shall be installed and operated at the network boundaries, including end- point firewalls.
- Anti-virus, -spyware, and other -malware programs shall be installed and updated.
- 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 organisation shall continuously monitor its network to spot signs of cyber threats or unusual activity, using clearly defined rules for what counts as a potential security incident.
- The physical environment shall be monitored to find potentially adverse events.
- Physical access to the organisation's critical systems and devices, in addition to physical access monitoring to the facility, shall be supplemented by physical intrusion alarms, surveillance equipment, and independent monitoring teams.
- 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 shall implement hardware integrity checks to detect unauthorised tampering of critical system hardware. Controls shall be proportionate to the organ- isation’s risk profile and operational capacity.
- The organisation's incident response plan shall include measures to detect unau- thorised tampering with the hardware of critical systems.
- The organisation shall establish a system to accurately distinguish between legitimate alerts and false positives, ensuring effective detection and removal of malicious code.
- The organisation's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management.
- The organisation shall demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management.
- Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.
- 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
- Redundancy shall be implemented to meet availability requirements as defined by the organisation, legislation and/or regulations
- Recovery time and recovery point objectives for the resumption of essential ICT/ OT system processes shall be defined and monitored.
- 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.
- The information and cybersecurity risk management strategy shall be reviewed and adjusted to ensure coverage of organisational requirements and risks.
- The organisation's cybersecurity risk management performance shall be evaluated, reviewed and adjusted when necessary
- Policies and procedures for managing information and cybersecurity shall be established, documented, reviewed, approved, updated when changes occur, communicated and enforced.
- 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.
- As part of the organisation-wide risk management strategy, a comprehensive strategy to manage information and cybersecurity risks shall be developed and updated when changes occur.
- 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.
- Organisation's top management shall be responsible and accountable for cyber- security risk and shall foster a culture that is risk-aware, ethical, and continually improving.
- 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.
- The organisation shall appoint a senior-level executive information security officer.
- Personnel with access to the organisation’s most critical information or technology shall be authenticated.
- A cybersecurity process for human resources shall be developed and maintained applicable at recruitment, during employment and at termination of employment.
- A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes shall be documented, reviewed, updated when changes occur, and approved by organisational stakeholders.
- 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.
- Informationand Cybersecurity supply chain risk management shall be integrated into information/cybersecurity and enterprise risk management, risk assessment, and improvement processes.
- 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.
- Contractual information/cybersecurity requirements for suppliers and external part- ners shall be implemented to ensure a verifiable flaw resolution process and to ensure that deficiencies identified during information/cybersecurity testing and evaluation are remedied.
- The organisation shall establish contractual requirements permitting the organisation to review the information/cybersecurity programs implemented by suppliers and third-party partners.
- Planning and due diligence shall be carried out to reduce risks before entering into formal relationships with suppliers or other third parties.
- 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.
- A documented list of all critical suppliers, vendors and partners of the organisation that may be involved in a major incident shall be established, kept up-to-date and made available online and off-line with due regard to confidentiality and security.
- The organisation shall audit business-critical third-party service providers for secu- rity compliance.
- The organisation shall ensure conformity with information/cybersecurity contractual obligations by suppliers and third-party partners through regular reviews of independ- ent audits, assessments, and third-party evaluations.
- 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.
- Supply chain security practices shall be integrated into information/cybersecurity and enterprise risk management programs, and their performance shall be monitored throughout the product and service life cycle.
- Cybersecurity supply chain risk management plans shall include actions and respon- sibilities for managing risks that may arise after a supplier relationship or service agreement has ended.
- An inventory of physical and virtual infrastructure assets — such as hardware, net- work devices, and cloud-hosted environments — that support information process- ing shall be documented, reviewed, and updated as changes occur.
- 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.
- Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified.
- An inventory of software, digital services, and business systems used within the organisation shall be documented, reviewed, and updated as changes occur.
- 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.
- Mechanisms for detecting the presence of unauthorised software within the organ- isation’s ICT/OT environment shall be identified.
- 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.
- The organisation shall map, document and authorise the flow of information to/from external systems and update the flow when changes occur.
- The organisation’s assets shall be prioritised based on classification, criticality, and business value.
- Data that the organisation stores and uses shall be identified.
- Inventories of data and associated metadata shall be maintained for designated data types.
- The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.
- 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 require remote maintenance diagnostic services to be per- formed from a system that implements security features similar to the security features implemented on the equivalent organisation's critical system.
- Patches and security updates for Operating Systems and critical system compo- nents shall be installed.
- 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 ensure that disposal actions are approved, tracked, docu- mented, and verified.
- 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 prevent unauthorised removal of maintenance equipment containing critical system information of the organisation.
- The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems.
- Maintenance tools and portable storage devices shall be inspected as they enter the facility and shall be protected by anti-malware solutions that scan them for malicious code before they are used on the organisation's 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 conduct post-incident evaluations to analyse lessons learned from incident response and recovery, and consequently improve processes / proce- dures / technologies to enhance its cyber resilience.
- 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.
- The organisation shall implement independent teams to assess its processes, best practices, and technology solutions to safeguard critical systems and assets.
- The organisation shall ensure that the security plan for its critical systems facilitates the review, testing, and continual improvement of the security protection processes.
- The organisation shall conduct specialised assessments including in-depth monitoring, vulnerability scanning, malicious user testing, insider threat assessment, performance/ load testing, and verification and validation testing on the organisation's critical systems.
- Contingency and continuity plans shall be established, communicated, maintained, tested, validated, and improved.
- The organisation shall coordinate the development and the testing of Incident Response Plans and other cybersecurity plans that affect operations with stake- holders to ensure that these plans align with overall organisational goals and enhance resilience.
- Threats and vulnerabilities shall be identified in all relevant assets, including software, network and system architectures, and facilities that house critical computing assets.
- 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.
- To ensure that organisation's operations are not adversely affected by the testing process, performance/load testing and penetration testing on the organisation’s systems shall be carried out with care.
- 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.
- Automated mechanisms shall be implemented to disseminate security alerts and advisories to relevant organisation stakeholders.
- Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.
- The organisation shall conduct risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets.
- 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.
For people working with the data
http://cyfun.data.gift/data/CyFun2025
All data (12 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 |
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
The number of triples associated with the subject. |
10 |
|
Specifies the dataset the subject is part of. |
|
References
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
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. |