Concept list
skos:ConceptScheme
CyFun 2025 — Delta IMPORTANT→ESSENTIAL (new requirements)
- Dataset
- CyFun Requirements
Concepts in this list
-
Other concepts
skos:inScheme -
- The organisation shall implement automated mechanisms where feasible to review and analyse detected events.
- 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.
- 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.
- 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.
- 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 shall demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management.
- 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 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
- 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.
- The organisation shall appoint a senior-level executive information security officer.
- 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.
- Informationand Cybersecurity supply chain risk management shall be integrated into information/cybersecurity and enterprise risk management, risk assessment, and improvement processes.
- 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.
- 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.
- 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.
- Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified.
- Mechanisms for detecting the presence of unauthorised software within the organ- isation’s ICT/OT environment shall be identified.
- The organisation shall map, document and authorise the flow of information to/from external systems and update the flow when changes occur.
- The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.
- 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.
- The organisation shall ensure that disposal actions are approved, tracked, docu- mented, and verified.
- The organisation shall prevent unauthorised removal of maintenance equipment containing critical system information of the organisation.
- 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.
- 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.
- 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.
- 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.
- Automated mechanisms shall be implemented to disseminate security alerts and advisories to relevant organisation stakeholders.
- Risk assessment results shall be disseminated to relevant stakeholders.
- The organisation shall implement automated mechanisms for disseminating and track- ing remedial measures related to vulnerability information that automatically handles vulnerability data collection, disseminates information, tracks remedial measures, includes reporting and accountability, and enables continuous monitoring.
- System credentials shall be deactivated after a specified period of inactivity unless it would compromise the safe operation of (critical) processes.
- For transactions within the organisation's critical systems, the organisation shall implement Multi Factor Authentication (MFA), cryptographic certificates, identity tokens, cryptographic keys and other credentials as appropriate and where feasible.
- The organisation’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.
- The organisation shall ensure that unique credentials are used for each authenti- cated user, device, and process interacting with the organisation's critical systems. These credentials shall be verified, and the unique identifiers shall be captured during system interactions. Exceptions may be made for emergency access ("break- glass" procedures), provided such access is strictly controlled, logged, and reviewed.
- Remote access to the organisation’s critical systems shall be monitored and cryp- tographic mechanisms shall be implemented where determined necessary.
- The security for connections with external systems shall be verified and framed by documented agreements.
- Identity assertions shall be protected, conveyed, and verified
- Account usage restrictions for specific time periods and locations shall be taken into account in the organisation's security access policy and applied accordingly.
- Privileged users shall be managed, monitored and audited.
- Critical zones shall have additional physical access controls beyond those applied to general facilities.
- Assets located within critical zones shall be physically protected against unauthorised access, damage, or interference.
- The organisation shall evaluate whether its cybersecurity awareness training is effec- tive in improving knowledge, behaviour, and readiness across the organisation.
- The organisation shall implement automated tools where feasible to provide notifi- cation upon discovering discrepancies during integrity verification.
- The organisation shall define and implement automated responses to detected integrity violations, using predefined safeguards that are proportionate to the severity and impact of the violation.
- The organisation shall protect the confidentiality of its critical assets while at rest.
- Portable storage devices containing system data shall be controlled and protected while in transit and in storage.
- The organisation shall protect its critical and sensitive information while in transit.
- The organisation’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited.
- The organisation shall regularly verify the integrity and recoverability of backups through coordinated testing with all relevant continuity and incident response func- tions. Backup testing shall be integrated into broader resilience planning, including business continuity, disaster recovery, and cyber incident response.
- is an evolution — not a repetition — of PR.DS-11.3 and PR.DS-11.4. While the earlier controls focus on where and how backups are stored and verified, PR.DS-11.5 focuses on what is being backed up and how it is logically separated to optimise recovery: · PR.DS-11.3 ensures backups are secure and stored separately. · PR.DS-11.4 ensures backups are tested and integrated into recovery planning. · PR.DS-11.5 ensures functional separation between system and data backups to enable faster, more targeted recovery.
- The organisation shall implement, where feasible, authenticated proxy servers or fire- walls with URL filtering and threat intelligence capabilities for defined communications traffic between its critical systems and external networks.
- The organisation shall ensure that its critical systems are designed to fail securely and remain protected in the event of an operational failure of a border protection device.
- The organisation shall ensure that development and test environments are strictly separated from the production environment, particularly in ICS/OT systems where any crossover could compromise safety, endanger health, or disrupt essential operations.
- The organisation shall define, monitor, and control the flow of information and data within and between its critical systems to ensure that only authorised and secure exchanges occur, regardless of network boundaries or system architecture.
- The organisation shall manage interfaces with external telecommunications services as part of its broader network security policy, by defining how traffic is controlled, ensuring the confidentiality and integrity of transmitted information, and reviewing and documenting any exceptions to established rules.
- The organisation shall implement fire detection devices that activate and notify key personnel automatically in the event of a fire.
- The organisation shall implement mechanisms to ensure that critical systems and services remain operational or can be quickly restored during both normal opera- tions and adverse conditions.
- The organisation shall configure its business-critical systems to operate with only the essential functions needed for their intended purpose. This includes reviewing and updating baseline configurations to disable any non-essential capabilities.
- The organisation shall identify and disable specific functions, ports, protocols, and services within its critical systems that are not required for business operations.
- The organisation shall implement technical safeguards to enforce a policy of ‘deny-all’ and ‘permit-by-exception’ so that only authorised software programmes are executed.
- Unauthorised configuration changes to organisation's systems shall be monitored and addressed with the appropriate mitigation actions.
- The organisation shall ensure that audit processing failures on the organisation's systems generate alerts and trigger defined responses.
- The organisation shall ensure that authorised personnel can extend or enhance audit logging and monitoring capabilities when needed to support investigations or incident response.
- Secure software development practices shall be integrated into all phases of the software development lifecycle, and their effectiveness should be regularly moni- tored and improved.
- The organisation shall assign a Public Relations Officer (PRO) to manage public communications during information/cybersecurity incident recovery, ensuring that public updates are shared while maintaining the confidentiality, integrity, and accuracy of the information.
- The organisation shall implement a crisis communication strategy to mitigate nega- tive impacts during a crisis and help restore its reputation afterward.
- The organisation's essential functions and services shall be continued with little or no loss of operational continuity, and continuity shall be maintained until full system recovery.
- Each incident shall be analysed to determine what occurred and to identify its root cause.
- Actions performed during an investigation shall be recorded, and the records' integrity and provenance shall be preserved.
- Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.
- A n incident’s magnitude shall be estimated and validated.
- Automated tools shall be used to support the investigation and impact assessment of validated cybersecurity incidents.
For people working with the data
http://cyfun.data.gift/data/CyFun2025_delta_IMPORTANT_to_ESSENTIAL
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 IMPORTANT→ESSENTIAL (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. |