Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
The CyberFundamentals framework is created by Centre for Cyber security Belgium. It provides a set of concrete measures to protect your data, significantly reduce the risk of the most common cyber-attacks, and increase your organisation's cyber resilience.
The CyberFundamentals framework is created by Centre for Cybersecurity Belgium. It provides a set of concrete measures to protect your data, significantly reduce the risk of the most common cyber-attacks, and increase your organisation's cyber resilience. The framework is based on:
The Cyberfundamentals are structured in 4 levels, with a subsequent level containing a little more measures than the previous one each time. A beginner level Small, followed by Basic, Important and Essential. The Essential level contains all the basic information security mesures from previous ones and introduces more advanced controls. The essential level is in line with the NIS2 directive.
Below you'll find all of the requirements of this framework. In Cyberday, we map all requirement to global tasks, making multi-compliance management easy. Do it once, and see the progress across all frameworks!
The organization shall conduct risk assessments in which risk is determined by threats, vulnerabilities and impact on business processes and assets.
Guidance
- Keep in mind that threats exploit vulnerabilities.
- Identify the consequences that losses of confidentiality, integrity and availability may have on the assets and related business processes.
The organization shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and the likelihood of their occurrence.
Guidance
- Risk assessment should include threats from insiders and external parties.
- Qualitative and/or quantitative risk analysis methods
(MAPGOOD, ISO27005, CIS RAM, …) can be used together with software tooling.
Risk assessment results shall be disseminated to relevant stakeholders.
A comprehensive strategy shall be developed and implemented to manage risks to the organization’s critical systems, that includes the identification and prioritization of risk responses.
Guidance
- Management and employees should be involved in information- and cybersecurity.
- It should be identified what the most important assets are, and how they are protected.
- It should be clear what impact will be if these assets are compromised.
- It should be established how the implementation of adequate mitigation measures will be organized.
A cyber risk management process that identifies key internal and external stakeholders andfacilitates addressing risk-related issues and information shall be created, documented, reviewed, approved, and updated when changes occur.
Guidance
External stakeholders include customers, investors and shareholders, suppliers, government agencies and the wider community.
The organization shall clearly determine its risk appetite.
Guidance
Determination and expression of risk tolerance (risk appetite) should be in line with the policies on information security and cybersecurity, to facilitate demonstration of coherence between policies, risk tolerance and measures.
The organization’s role in critical infrastructure and its sector shall determine the organization’s risk appetite.
The organization shall document, review, approve, update when changes occur, and implement a cyber supply chain risk management process that supports the identification, assessment, and mitigation of the risks associated with the distributed and interconnected nature of ICT/OT product and service supply chains.
The organization shall conduct cyber supply chain risk assessments at least annually or when a change to the organization’s critical systems, operational environment, or supply chain occurs; These assessments shall be documented, and the results disseminated to relevant stakeholders including those responsible for ICT/OT systems.
Guidance
This assessment should identify and prioritize potential negative impacts to the organization from the risks associated with the distributed and interconnected nature of ICT/OT product and service supply chains.
A documented list of all the organization’s suppliers, vendors and partners who may be involved in a major incident shall be established, kept up-to-date and made available online and offline.
Guidance
This list should include suppliers, vendors and partners contact information and the services they provide,so they can be contacted for assistance in the event of an outage or service degradation.
Based on the results of the cyber supply chain risk assessment, a contractual framework for suppliers and external partners shall be established to address sharing of sensitive information and distributed and interconnected ICT/OT products and services.
Guidance
- Entities not subject to the NIS legislation should consider business critical suppliers and third-party partners only.
- Keep in mind that GDPR requirements need to be fulfilled when business information contains personal data (applicable on all levels), i.e. security measures need to be addressed in the contractual framework.
Contractual ‘information security and cybersecurity’ requirements for suppliers and thirdparty partners shall be implemented to ensure a verifiable flaw remediation process, and to ensure the correction of flaws identified during ‘information security and cybersecurity’ testing and evaluation.
Guidance
- Information systems containing software (or firmware) affected by recently announced software flaws (and potential vulnerabilities resulting from those flaws) should be identified.
- Newly released security relevant patches, service packs, and hot fixes should be installed, and these patches, service packs, and hot fixes are tested for effectiveness and potential side effects on the organization’s information systems before installation. Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling are also addressed expeditiously. Flaw remediation should be incorporated into configuration management as an emergency change.
The organization shall establish contractual requirements permitting the organization to review the ‘information security and cybersecurity’ programs implemented by suppliers and third-party partners.
The organization shall review assessments of suppliers’ and third-party partner’s compliance with contractual obligations by routinely reviewing audits, test results, and other evaluations.
Guidance
Entities not subject to the NIS legislation could limit themselves to business-critical suppliers and thirdparty partners only.
The organization shall review assessments of suppliers’ and third-party partner’s compliance with contractual obligations by routinely reviewing third-party independent audits, test results, and other evaluations.
Guidance
The depth of the review should depend on the criticality of delivered products and services.
The organization shall identify and document key personnel from suppliers and third-party partners to include them as stakeholders in response and recovery planning activities.
Guidance
Entities not subject to the NIS legislation could limit themselves to business-critical suppliers and thirdparty partners only.
The organization shall identify and document key personnel from suppliers and third-party partners to include them as stakeholders in testing and execution of the response and recovery plans.
Identities and credentials for authorized devices and users shall be managed.
Guidance
Identities and credentials for authorized devices and users could be managed through a password policy. A password policy is a set of rules designed to enhance ICT/OT security by encouraging organization’s to (Not limitative list and measures to be considered as appropriate):
- Change all default passwords.
- Ensure that no one works with administrator privileges for daily tasks.
- Keep a limited and updated list of system administrator accounts.
- Enforce password rules, e.g. passwords must be longer than a state-of-the-art number of characters with a combination of character types and changed periodically or when there is any suspicion of compromise.
- Use only individual accounts and never share passwords.
- Immediately disable unused accounts.
- Rights and privileges are managed by user groups.
Identities and credentials for authorized devices and users shall be managed, where feasible through automated mechanisms.
Guidance
- Automated mechanisms can help to support the management and auditing of information system credentials.
- Consider strong user authentication, meaning an authentication based on the use of at least two authentication factors from different categories of either knowledge (something only the user knows), possession (something only the user possesses) or inherence (something the user is) that are independent, in that the breach of one does not compromise the reliability of the others, and is designed in such a way to protect the confidentiality of the authentication data.
System credentials shall be deactivated after a specified period of inactivity unless it would compromise the safe operation of (critical) processes.
Guidance
- To guarantee the safe operation, service accounts should be used for running processes and services.
- Consider the use of a formal access procedure for external parties.
For transactions within the organization's critical systems, the organization shall implement:
- multi-factor end-user authentication (MFA or "strong authentication").
- certificate-based authentication for system-to-system communications.
Guidance
Consider the use of SSO (Single Sign On) in combination with MFA for the organization's internal and external critical systems.
The organization’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.
Guidance
- Consider limiting the number of failed login attempts by implementing automatic lockout.
- The locked account won’t be accessible until it has been reset or the account lockout duration elapses.
Physical access to the facility, servers and network components shall be managed.
Guidance
- Consider to strictly manage keys to access the premises and alarm codes. The following rules should be considered:
- Always retrieve an employee's keys or badges when they leave the company permanently.
- Change company alarm codes frequently.
- Never give keys or alarm codes to external service providers (cleaning agents, etc.), unless it is possible to trace these accesses and restrict them technically to given time slots.
- Consider to not leaving internal network access outlets accessible in public areas. These public places can be waiting rooms, corridors...
Physical access shall be managed, including measures related to access in emergency situations.
Guidance
- Physical access controls may include, for example lists of authorized individuals, identity credentials, escort requirements, guards, fences, turnstiles, locks, monitoring of facility access, camera surveillance.
- The following measures should be considered:
- Implement a badge system and create different security zones.
- Limit physical access to servers and network components to authorized personnel.
- Log all access to servers and network components.
- Visitor access records should be maintained, reviewed and acted upon as required.
Physical access to critical zones shall be controlled in addition to the physical access to the facility.
Guidance
E.g. production, R&D, organization’s critical systems equipment (server rooms…)
Assets related to critical zones shall be physically protected.
Guidance
- Consider protecting power equipment, power cabling, network cabling, and network access interfaces from accidental damage, disruption, and physical tampering.
- Consider implementing redundant and physically separated power systems for organization’s critical operations.
The organisation's wireless access points shall be secured.
Guidance
Consider the following when wireless networking is used:
- Change the administrative password upon installation of a wireless access points.
- Set the wireless access point so that it does not broadcast its Service Set Identifier (SSID).
- Set your router to use at least WiFi Protected Access (WPA-2 or WPA-3 where possible), with the Advanced Encryption Standard (AES) for encryption.
- Ensure that wireless internet access to customers is separated from your business network.
- Connecting to unknown or unsecured / guest wireless access points, should be avoided, and if unavoidable done through an encrypted virtual private network (VPN) capability.
- Manage all endpoint devices (fixed and mobile) according to the organization's security policies.
Usage restrictions, connection requirements, implementation guidance, and authorizations
for remote access to the organization’s critical systems environment shall be identified, documented, and implemented.
Guidance
Consider the following:
- Remote access methods include, for example, wireless, broadband, Virtual Private Network (VPN) connections, mobile device connections, and communications through external networks.
- Login credentials should be in line with company's user authentication policies.
- Remote access for support activities or maintenance of organizational assets should be approved, logged, and performed in a manner that prevents unauthorized access.
- The user should be made aware of any remote connection to its device by a visual indication.
Remote access to the organization’s critical systems shall be monitored and cryptographic mechanisms shall be implemented where determined necessary.
Guidance
This should include that only authorized use of privileged functions from remote access is allowed.
The organization's networks when accessed remotely shall be secured, including through multi-factor authentication (MFA).
Guidance
Enforce MFA (e.g. 2FA) on Internet-facing systems, such as email, remote desktop, and Virtual Private Network (VPNs).
The security of connections with external systems shall be verified and framed by documented agreements.
Guidance
Access from pre-defined IP addresses could be considered.
Access permissions for users to the organization’s systems shall be defined and managed.
- key measure -
Guidance
The following should be considered:
- Draw up and review regularly access lists per system (files, servers, software, databases, etc.), possibly through analysis of the Active Directory in Windows-based systems, with the objective of determining who needs what kind of access (privileged or not), to what, to perform their duties in
the organization.
- Set up a separate account for each user (including any contractors needing access) and require that strong, unique passwords be used for each account.
- Ensure that all employees use computer accounts without administrative privileges to perform typical work functions. This includes separation of personal and admin accounts.
- For guest accounts, consider using the minimal privileges (e.g. internet access only) as required for your business needs.
- Permission management should be documented in a procedure and updated when appropriate.
- Use 'Single Sign On' (SSO) when appropriate.
Where feasible, automated mechanisms shall be implemented to support the management of user accounts on the organisation's critical systems, including disabling, monitoring, reporting and deleting user accounts.
Guidance
Consider separately identifying each person with access to the organization's critical systems with a username to remove generic and anonymous accounts and access.
Account usage restrictions for specific time periods and locations shall be considered in the organization's security access policy and applied accordingly.
Guidance
Specific restrictions can include, for example, restricting usage to certain days of the week, time of day, or specific durations of time.
It shall be identified who should have access to the organization's business's critical information and technology and the means to get access.
Guidance
Means to get access may include: a key, password, code, or administrative privilege.
Employee access to data and information shall be limited to the systems and specific information they need to do their jobs (the principle of Least Privilege).
Guidance
- The principle of Least Privilege should be understood as the principle that a security architecture should be designed so that each employee is granted the minimum system resources and authorizations that the employee needs to perform its function.
- Consider to:
- Not allow any employee to have access to all the business’s information.
- Limit the number of Internet accesses and interconnections with partner networks to the strict necessary to be able to centralize and homogenize the monitoring of exchanges more easily.
- Ensure that when an employee leaves the business, all access to the business’s information or systems is blocked instantly.
Separation of duties shall be ensured in the management of access rights.
Guidance
Separation of duties includes, for example:
- dividing operational functions and system support functions among different roles.
- conducting system support functions with different individuals.
- not allow a single individual to both initiate and approve a transaction (financial or otherwise).
- ensuring that security personnel administering access control functions do not also administer audit functions.
Nobody shall have administrator privileges for daily tasks.
Guidance
Consider the following:
- Separate administrator accounts from user accounts.
- Do not privilege user accounts to effectuate administration tasks.
- Create unique local administrator passwords and disable unused accounts.
- Consider prohibiting Internet browsing from administrative accounts.
Privileged users shall be managed, monitored and audited.
Firewalls shall be installed and activated on all the organization's networks.
Guidance
Consider the following:
- Install and operate a firewall between your internal network and the Internet. This may be a function of a (wireless) access point/router, or it may be a function of a router provided by the Internet Service Provider (ISP).
- Ensure there is antivirus software installed on purchased firewall solutions and ensure that the
administrator’s log-in and administrative password is changed upon installation and regularly thereafter.
- Install, use, and update a software firewall on each computer system (including smart phones and
other networked devices).
- Have firewalls on each of your computers and networks even if you use a cloud service provider or a
virtual private network (VPN). Ensure that for telework home network and systems have hardware
and software firewalls installed, operational, and regularly updated.
- Consider installing an Intrusion Detection / Prevention System (IDPS). These devices analyse network
traffic at a more detailed level and can provide a greater level of protection.
Where appropriate, network integrity of the organization's critical systems shall be protected by incorporating network segmentation and segregation.
Guidance
- Consider creating different security zones in the network (e.g. basic network segmentation through
VLAN’s or other network access control mechanisms) and control/monitor the traffic between these zones.
- When the network is "flat", the compromise of a vital network component can lead to the compromise of the entire network.
Where appropriate, network integrity of the organization's critical systems shall be
protected by
(1) Identifying, documenting, and controlling connections between system components.
(2) Limiting external connections to the organization's critical systems.
Guidance
Boundary protection mechanisms include, for example, routers, gateways, unidirectional gateways,
data diodes, and firewalls separating system components into logically separate networks or
subnetworks.
The organization shall implement, where feasible, authenticated proxy servers for defined
communications traffic between the organization's critical systems and external networks.
The organization shall monitor and control connections and communications at the external
boundary and at key internal boundaries within the organization's critical systems by
implementing boundary protection devices where appropriate.
Guidance
Consider implementing the following recommendations:
- Separate your public WIFI network from your business network.
- Protect your business WIFI with state-of-the-art encryption.
- Implement a network access control (NAC) solution.
- Encrypt connections to your corporate network.
- Divide your network according to security levels and apply firewall rules. Isolate your networks for
server administration.
- Force VPN on public networks.
- Implement a closed policy for security gateways (deny all policy: only allow/open connections that
have been explicitly pre-authorized).
The organization shall ensure that the organization's critical systems fail safely when a border protection device fails operationally.
The organization shall implement documented procedures for verifying the identity of
individuals before issuing credentials that provide access to organization's systems.
The organization shall ensure the use of unique credentials bound to each verified user,
device, and process interacting with the organization's critical systems; make sure that they
are authenticated, and that the unique identifiers are captured when performing system
interactions.
Explore our comprehensive resources and improve your security with the themes of this framework.
Discover specific ways our platform streamlines your ISO 27001 compliance process, from automated controls to audit preparation.
Explore use caseTake our comprehensive assessment to identify gaps in your current implementation and get personalized recommendations.
Start assessmentDive deeper with our articles, case studies, and expert insights on framework implementation.
Read articleGet a concise overview of all requirements, controls, and implementation steps in our quick guide.
Get the guideSee how the overlap and differences with any other framework to optimize your compliance strategy.
Compare frameworkParticipate in expert-led sessions covering implementation strategies, common pitfalls, and best practices for compliance.
Register for webinarParticipate in expert-led sessions covering implementation strategies, common pitfalls, and best practices for compliance.
Register for webinarUnderstand the basics of cyber security frameworks with our comprehensive guide.
Read the articleWhen building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
Break down the framework into specific obligations that must be met.
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.