Trust & Compliance Center
Welcome to the NormNest Trust & Compliance Center. This portal provides transparency into our security, privacy, and compliance practices.
Certifications
Completed Certifications
ISO27001:2022
ISO27001:2022
<p data-start="0" data-end="386" class="">De <strong data-start="3" data-end="25">ISO/IEC 27001:2022</strong> is een internationale norm voor informatiebeveiliging. Ze specificeert eisen voor het opzetten, implementeren, onderhouden en continu verbeteren van een <strong data-start="179" data-end="228">Information Security Management System (ISMS)</strong>. Het doel is om organisaties te helpen hun informatie systematisch te beveiligen tegen risico’s zoals datalekken, cyberaanvallen of ongeautoriseerde toegang.</p> <p data-start="388" data-end="568" class="">De versie <strong data-start="398" data-end="406">2022</strong> is een geactualiseerde editie, met meer nadruk op risicobeheer, leiderschap, en continue verbetering, en sluit beter aan bij moderne dreigingen en technologieën.</p>
KMO-Portefeuille (erkende dienstverlener)
KMO-Portefeuille (erkende dienstverlener)
<p data-start="215" data-end="640">De KMO-Portefeuille is een subsidiemaatregel van de Vlaamse overheid die kleine en middelgrote ondernemingen (KMO’s) financieel ondersteunt bij het volgen van opleidingen en het inwinnen van advies. Organisaties die erkend zijn als dienstverlener voor de KMO-Portefeuille voldoen aan specifieke kwaliteits- en administratieve vereisten en mogen via het platform diensten aanbieden aan Vlaamse ondernemingen.</p> <p data-start="642" data-end="786">Deze erkenning biedt klanten niet alleen financiële voordelen, maar ook vertrouwen in de deskundigheid en betrouwbaarheid van de dienstverlener.</p>
Data Protection Officer
Data Protection Officer
De Data Protection Officer (DPO)-certificering bevestigt onze diepgaande kennis van de Algemene Verordening Gegevensbescherming (AVG/GDPR) en onze bekwaamheid om organisaties te ondersteunen bij het waarborgen van privacy- en gegevensbeschermingsnormen. Deze certificering onderstreept onze expertise in het adviseren over privacybeleid, het beoordelen van gegevensverwerkingsactiviteiten, het management van datalekken, en het fungeren als betrouwbaar contactpunt voor toezichthoudende autoriteiten. <div><br></div><div>Onze gecertificeerde DPO’s combineren gedegen juridische kennis met ruime praktijkervaring binnen diverse sectoren, zowel privaat als publiek. Hierdoor bieden wij een volwaardige, continu beschikbare DPO-dienstverlening die perfect aansluit op de unieke privacybehoeften en compliance-uitdagingen van elke organisatie. Deze deskundigheid versterkt het vertrouwen van klanten en medewerkers en helpt organisaties effectief te voldoen aan hun wettelijke verplichtingen.</div>
ISO/IEC 27001 Lead auditor
ISO/IEC 27001 Lead auditor
Het bezit van het <strong data-start="182" data-end="224">ISO/IEC 27001 Lead Auditor-certificaat</strong> bevestigt onze grondige kennis van informatiebeveiligingsnormen en onze bekwaamheid om formele audits uit te voeren op een Information Security Management System (ISMS). Deze certificering weerspiegelt onze deskundigheid in het beoordelen van risico’s, naleving, en de doeltreffendheid van beveiligingsmaatregelen binnen organisaties. Hierdoor kunnen wij ondersteuning bieden bij zowel interne evaluaties als voorbereidingen op externe certificaties, en dit in uiteenlopende sectoren waar informatiebeveiliging van cruciaal belang is.
NIS 2 Directive: Senior Lead Implementor
NIS 2 Directive: Senior Lead Implementor
<p data-start="150" data-end="788">Het <strong data-start="154" data-end="210">NIS 2 Directive: Senior Lead Implementor-certificaat</strong> bevestigt onze diepgaande kennis van de vereisten en verantwoordelijkheden die voortvloeien uit de NIS2-richtlijn, gericht op de beveiliging van netwerk- en informatiesystemen binnen essentiële en belangrijke entiteiten. Deze certificering onderschrijft onze expertise in het opzetten, implementeren en optimaliseren van beheersmaatregelen op vlak van cybersecurity, risicobeheer, governance en incidentrespons. Ze stelt ons in staat organisaties te begeleiden bij het naleven van de NIS2-verplichtingen en bij het opbouwen van een weerbare en conforme digitale infrastructuur.</p>
Compliance
GDPR
Heb je vragen over hoe wij omgaan met jouw persoonsgegevens? Wil je informatie opvragen, gegevens laten corrigeren, verwijderen of je rechten uitoefenen zoals voorzien in de geldende wetgeving (zoals de GDPR)?
Neem dan gerust contact met ons op via dpo@cloudcom.eu. Wij helpen je graag verder in lijn met wat de normen en wetgeving voorschrijven.
We zetten alle nodige stappen in werking om deze regelgeving correct na te leven en jouw gegevens zo goed mogelijk te beschermen.
GDPR
De <strong data-start="3" data-end="11">GDPR</strong> (General Data Protection Regulation) is een Europese wetgeving die de privacy en bescherming van persoonsgegevens van burgers binnen de EU regelt. Ze is sinds mei 2018 van kracht en verplicht organisaties om zorgvuldig om te gaan met persoonlijke gegevens, transparant te zijn over het gebruik ervan, en passende beveiligingsmaatregelen te nemen. De GDPR geeft individuen meer controle over hun data en legt bedrijven strenge verplichtingen op, met hoge boetes bij niet-naleving.<div><br></div><div>Wet : <a href="https://eur-lex.europa.eu/legal-content/NL/TXT/?uri=CELEX%3A32016R0679">Verordening - 2016/679 - EN - avg - EUR-Lex</a> - https://eur-lex.europa.eu/legal-content/NL/TXT/?uri=CELEX%3A32016R0679</div><div><br></div><div>Informatie : https://www.gegevensbeschermingsautoriteit.be/professioneel/eerstehulp-avg/toolbox</div>
ISO/IEC 27001
ISO/IEC 27001
<span data-teams="true">Internationale standaard voor informatiebeveiliging. Toont aan dat je als organisatie risico’s beheerst en je data adequaat beschermt.</span>
NIS2 (EU)
NIS2 (EU)
Europese richtlijn die strengere eisen oplegt aan cybersecurity, vooral voor essentiële en belangrijke sectoren. Vanaf 2024 belangrijk voor veel bedrijven.
Cyber Fundamentals (CyFun)
Cyber Fundamentals (CyFun)
Vlaams/Nationaal raamwerk dat bedrijven helpt om hun cyberweerbaarheid op basisniveau op orde te brengen. Focus op identificeren, beschermen, detecteren, reageren en herstellen.
Cybersecurity Framework
Our cybersecurity approach is based on the NIST Cybersecurity Framework, which organizes cybersecurity activities into five core functions: Identify, Protect, Detect, Respond, and Recover.
IDENTIFY
BASIC_ID.AM-1.1: An inventory of assets associated with information and information processing facilities within the organization shall be documented, reviewed, and updated when changes occur.
Our organization maintains a comprehensive inventory of all information and information processing assets through our internal platform, my.cloudcom. This platform enables us to document, review, and update asset records efficiently, including fixed and portable computers, mobile devices, network infrastructure, and other connected or standalone components.
The inventory is continuously maintained and updated when changes occur, supported by appropriate approval flows to ensure traceability and accountability. my.cloudcom supports the management of both networked and non-networked assets and functions as a centralized IT asset management tool aligned with best practices and compliance requirements.
IMPORTANT_ID.AM-1.2: The inventory of assets associated with information and information processing facilities shall reflect changes in the organization’s context and include all information necessary for effective accountability.
- Workstations (laptops/desktops),
- Mobile devices,
- Servers (physical and virtual),
- Network equipment (firewalls, routers, switches),
- Peripheral devices (printers, external drives),
- and where applicable, links to code repositories and databases.
BASIC_ID.AM-2.1: An inventory that reflects what software platforms and applications are being used in the organization shall be documented, reviewed, and updated when changes occur.
Our organization maintains an up-to-date inventory of all software platforms and applications in use, including internally hosted solutions and outsourced services (e.g., SaaS), through our platform my.cloudcom. This platform ensures that every entry—whether software program, platform, or database—is properly documented with key attributes such as name, description, version, number of users, and the type of data processed.
Changes to the software inventory are managed through an appropriate approval flow within my.cloudcom, ensuring updates are authorized and traceable.
IMPORTANT_ID.AM-2.3: Individuals who are responsible and who are accountable for administering software platforms and applications within the organization shall be identified.
- The system’s purpose and primary function
- Responsible team for management and documentation
- Whether the system contains personal or sensitive data
- (Linked in other tasks) access roles, data location, authentication methods, and system integrations
- Microsoft 365 (Collaboration and productivity)
- Entra ID (Identity management – contains personal data)
- Jira (Internal project and ticket management)
- Confluence (Documentation and knowledge sharing)
- MyCloudCom (Asset tracking – contains internal and client data)
- Atera (Client-facing ticketing – contains client data)
IMPORTANT_ID.AM-2.4: When unauthorized software is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly.
- The organization uses Heimdal Application Control to enforce a default-deny policy for software execution on endpoints.
- Only pre-approved software is allowed to run.
- Any execution attempt of unknown or unauthorized applications is automatically blocked and logged.
- Application control policies are maintained and reviewed by the Security Team in alignment with business requirements and risk assessments.
- SentinelOne provides real-time detection of unknown or potentially unwanted applications (PUAs), even if not explicitly blacklisted.
- It flags suspicious executables, scripts, and anomalous behavior.
- It can automatically quarantine or kill unauthorized processes and isolate affected devices.
- Detected applications or behavior are reviewed by the Security Team through the SentinelOne console.
- The organization does not currently operate a traditional network-based Intrusion Detection System (IDS).
- However, equivalent functionality is provided at the endpoint level through:
- Heimdal and SentinelOne behavioral analysis
- DNS filtering to prevent unauthorized communications
- Alerting mechanisms for known malicious or unauthorized software behavior
BASIC_ID.AM-3.1: Information that the organization stores and uses shall be identified.
Our organization identifies and categorizes all types of information it stores and uses, and this information is documented and maintained within our Information Security Management System (ISMS), which supports our ISO/IEC 27001:2022 implementation.
The ISMS contains a structured list of information types relevant to our business operations, including but not limited to:
Customer and supplier data (e.g., names, email addresses, contracts)
Financial information (e.g., invoices, banking details)
Internal documentation (e.g., procedures, reports)
Technical data (e.g., source code, configuration files, system logs)
Regulatory and compliance records
Proprietary business information and intellectual property
This inventory of information is regularly reviewed and updated as part of our ISMS processes. Furthermore, we map each type of information to associated physical assets, systems, software platforms, and applications—as outlined in our hardware and software inventories (referencing ID.AM-1 and ID.AM-2)—to ensure a clear understanding of where information resides and how it is processed, transmitted, or stored.
IMPORTANT_ID.AM-3.2: All connections within the organization's ICT/OT environment, and to other organization-internal platforms shall be mapped, documented, approved, and updated as appropriate.
IMPORTANT_ID.AM-4.1: The organization shall map, document, authorize and when changes occur, update, all external services and the connections made with them.
BASIC_ID.AM-5.1: The organization’s resources (hardware, devices, data, time, personnel, information, and software) shall be prioritized based on their classification, criticality, and business value.
Our organization has conducted a comprehensive risk assessment as part of our ISMS aligned with ISO/IEC 27001:2022, which includes an evaluation of the criticality, classification, and business value of all organizational resources—such as hardware, devices, data, time, personnel, information, and software.
Through this process, we analyze potential impacts on confidentiality, integrity, and availability for each resource by asking:
What would happen if the resource were made public, damaged, or lost?
What would be the consequences if the resource’s integrity were compromised?
What would the impact be if the resource became unavailable to us or our customers?
Based on this analysis, all resources are prioritized and classified according to their business impact, and appropriate controls and safeguards are implemented in line with their level of criticality. This classification supports our decision-making regarding access control, backup strategy, incident response, and continuity planning.
IMPORTANT_ID.AM-6.1: Information security and cybersecurity roles, responsibilities and authorities within the organization shall be documented, reviewed, authorized, and updated and alignment with organization-internal roles and external partners.
IMPORTANT_ID.BE-1.1: The organization’s role in the supply chain shall be identified, documented, and communicated.
IMPORTANT_ID.BE-5.1: To support cyber resilience and secure the delivery of critical services, the necessary requirements are identified, documented and their implementation tested and approved.
- Use of security technologies: All critical services utilize technologies such as strong authentication (admin access control), encrypted communications (e.g., HTTPS, VPN), and firewall protection.
- Defined technical parameters: Network devices are configured with strict access rules, port restrictions, and default service deactivation to minimize exposure.
- Service-level requirements: Critical equipment is monitored and maintained by the Network Operations Center (NOC), with regular updates and configuration backups in place.
- Access and usage criteria: Only authorized personnel have access to manage or configure network equipment. Usage is restricted through VLANs, network segmentation, and role-based access.
- Lifecycle management: Any implementation or update of network equipment includes security requirement verification before deployment.
BASIC_ID.GV-1.1: Policies and procedures for information security and cyber security shall be created, documented, reviewed, approved, and updated when changes occur.
Our organization has a comprehensive set of documented policies and procedures in place for information security and cybersecurity, developed in accordance with the ISO/IEC 27001:2022 standard.
These documents clearly define acceptable practices, responsibilities, and expectations regarding the protection of our information assets and systems. They are used to guide daily operations, support investigations in case of security incidents, and ensure a shared understanding across the organization.
As part of our onboarding process for new employees and consultants, we include a dedicated information security onboarding procedure, ensuring all individuals are aware of their responsibilities and our security policies from day one.
All policies and procedures are:
Reviewed and approved by management,
Updated promptly following organizational or technological changes, and
Formally reviewed at least annually as part of our ISMS lifecycle.
Policy updates are communicated clearly to all staff to ensure continued awareness and compliance.
IMPORTANT_ID.GV-1.2: An organization-wide information security and cybersecurity policy shall be established, documented, updated when changes occur, disseminated, and approved by senior management.
BASIC_ID.GV-3.1: Legal and regulatory requirements regarding information/cybersecurity, including privacy obligations, shall be understood and implemented.
Our organization identifies, understands, and implements all relevant legal and regulatory requirements related to information security, cybersecurity, and privacy, in particular those arising from the General Data Protection Regulation (GDPR).
As part of our ISO/IEC 27001:2022-aligned ISMS, we maintain a register of applicable legal and regulatory requirements, which is reviewed regularly to ensure continued compliance. This includes data protection obligations, incident reporting duties, data subject rights, and requirements related to the processing, storage, and transfer of personal data.
Our internal policies, procedures, and technical controls are designed to ensure that privacy and data protection principles—such as data minimization, purpose limitation, integrity, confidentiality, and accountability—are consistently applied across all business operations.
All employees and relevant contractors are made aware of these obligations during onboarding and through ongoing training initiatives.
IMPORTANT_ID.GV-3.2: Legal and regulatory requirements regarding information/cybersecurity, including privacy obligations, shall be managed.
BASIC_ID.GV-4.1: As part of the company's overall risk management, a comprehensive strategy to manage information security and cybersecurity risks shall be developed and updated when changes occur.
As part of our ISO/IEC 27001:2022 implementation, our organization has developed a comprehensive strategy for managing information security and cybersecurity risks as an integral component of our overall risk management framework.
This strategy includes:
The identification of information security objectives aligned with our business goals,
The assessment and treatment of risks to business-critical assets,
The allocation of appropriate resources (personnel, technology, budget) to implement and maintain security controls, and
A continuous improvement cycle that ensures the strategy is updated when changes occur in our organization or threat landscape.
Our approach ensures that information and cybersecurity risks are managed proactively and in a structured manner, with clear responsibilities and measurable targets.
IMPORTANT_ID.GV-4.2: Information security and cybersecurity risks shall be documented, formally approved, and updated when changes occur.
BASIC_ID.RA-1.1: Threats and vulnerabilities shall be identified.
Our organization identifies threats and vulnerabilities as part of the security objectives and risk assessment process defined in our ISO/IEC 27001:2022-compliant ISMS.
During regular risk assessments, we evaluate:
Vulnerabilities in hardware, software, procedures, and human factors that could expose our assets,
Threats that could exploit these vulnerabilities, including both internal and external sources, and
The associated risks, based on the likelihood and potential impact of such threats materializing.
This structured process enables us to maintain a clear understanding of our threat landscape and prioritize the implementation of appropriate risk treatment measures to reduce or mitigate risks to acceptable levels.
Identified threats and vulnerabilities are documented, reviewed periodically, and updated in response to changes in technology, operations, or the external environment.
IMPORTANT_ID.RA-1.2: A process shall be established to monitor, identify, and document vulnerabilities of the organisation's business critical systems in a continuous manner.
- Endpoint vulnerabilities are detected via SentinelOne.
- Server and infrastructure vulnerabilities are detected via ManageEngine Vulnerability Manager Plus (VAS).
- High and critical vulnerabilities are prioritized based on CVSS score, exploitability, and asset criticality.
- Vulnerabilities are tracked and managed in Jira from detection to closure.
- Patch management is coordinated between the Security Team and Infrastructure Team.
- SentinelOne alerts reviewed daily for critical vulnerabilities.
- VAS vulnerability scans reviewed weekly.
IMPORTANT_ID.RA-2.1: A threat and vulnerability awareness program that includes a cross-organization information-sharing capability shall be implemented.
BASIC_ID.RA-5.1: The organization shall conduct risk assessments in which risk is determined by threats, vulnerabilities and impact on business processes and assets.
Our organization conducts formal risk assessments in accordance with our ISO/IEC 27001:2022-aligned ISMS, where risk is determined based on the relationship between threats, vulnerabilities, and their potential impact on business processes and assets.
We systematically:
Identify threats that could exploit known or potential vulnerabilities,
Assess the potential impact of these risks on the confidentiality, integrity, and availability (CIA) of our information assets,
Evaluate how these risks could affect critical business processes, and
Document, review, and update risk scenarios as part of our regular risk management cycle or when significant changes occur.
The results of these assessments guide our risk treatment planning and ensure that appropriate safeguards are in place to protect our organization’s operations and assets
IMPORTANT_ID.RA-5.2: 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.
IMPORTANT_ID.RA-6.1: 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.
IMPORTANT_ID.RM-2.1: The organization shall clearly determine it’s risk appetite.
IMPORTANT_ID.RM-3.1: The organization’s role in critical infrastructure and its sector shall determine the organization’s risk appetite.
IMPORTANT_ID.SC-2.1: 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.
IMPORTANT_ID.SC-3.1: 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.
IMPORTANT_ID.SC-4.1: 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.
IMPORTANT_ID.SC-5.1: 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.
IDENTIFY
Develop an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities.
PROTECT
BASIC_PR.AC-1.1: Identities and credentials for authorized devices and users shall be managed.
IMPORTANT_PR.AC-1.2: Identities and credentials for authorized devices and users shall be managed, where feasible through automated mechanisms.
BASIC_PR.AC-2.1: Physical access to the facility, servers and network components shall be managed.
IMPORTANT_PR.AC-2.2: The management of physical access shall include measures related to access in emergency situations.
BASIC_PR.AC-3.1: The organisation's wireless access points shall be secured.
BASIC_PR.AC-3.2: The organization's networks when accessed remotely shall be secured, including through multi-factor authentication (MFA).
IMPORTANT_PR.AC-3.3: Usage restrictions, connection requirements, implementation guidance, and authorizations for remote access to the organization’s critical systems environment shall be identified, documented and implemented.
BASIC_PR.AC-4.1: Access permissions for users to the organization’s systems shall be defined and managed.
- Define Access Requirements: Identify the information and systems required for each role or task within the organization. Access should be granted based on job function and operational necessity.
- Assign Role-Based Access Controls (RBAC): Establish predefined access profiles based on roles, ensuring employees only have permissions relevant to their responsibilities.
- Implement Separation of Duties (SoD): Ensure that no single individual has control over conflicting tasks (e.g., approval and execution of financial transactions) to prevent fraud and errors.
- Periodic Access Review: Regularly review and update access rights to ensure they align with current roles and responsibilities. Revoke access for employees who no longer require it.
- Approval Workflow: Access requests must go through an approval process, involving line managers and security officers before access is granted.
- Logging and Monitoring: Track and audit access to sensitive information, ensuring that unauthorized access attempts are detected and addressed.
- Revoke Access on Role Changes or Exit: Immediately revoke or adjust access when an employee changes roles or leaves the organization to prevent unauthorized access. This structured approach ensures compliance with security policies while minimizing risks associated with unauthorized access.
BASIC_PR.AC-4.2: It shall be identified who should have access to the organization's business's critical information and technology and the means to get access.
BASIC_PR.AC-4.3: 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).
BASIC_PR.AC-4.4: Nobody shall have administrator privileges for daily tasks.
IMPORTANT_PR.AC-4.5: 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.
IMPORTANT_PR.AC-4.6: Separation of duties (SoD) shall be ensured in the management of access rights.
- Define Access Requirements: Identify the information and systems required for each role or task within the organization. Access should be granted based on job function and operational necessity.
- Assign Role-Based Access Controls (RBAC): Establish predefined access profiles based on roles, ensuring employees only have permissions relevant to their responsibilities.
- Implement Separation of Duties (SoD): Ensure that no single individual has control over conflicting tasks (e.g., approval and execution of financial transactions) to prevent fraud and errors.
- Periodic Access Review: Regularly review and update access rights to ensure they align with current roles and responsibilities. Revoke access for employees who no longer require it.
- Approval Workflow: Access requests must go through an approval process, involving line managers and security officers before access is granted.
- Logging and Monitoring: Track and audit access to sensitive information, ensuring that unauthorized access attempts are detected and addressed.
- Revoke Access on Role Changes or Exit: Immediately revoke or adjust access when an employee changes roles or leaves the organization to prevent unauthorized access. This structured approach ensures compliance with security policies while minimizing risks associated with unauthorized access.
IMPORTANT_PR.AC-4.7: Priviliged users shall be managed and monitored.
BASIC_PR.AC-5.1: Firewalls shall be installed and activated on all the organization's networks.
BASIC_PR.AC-5.2: Where appropriate, network integrity of the organization's critical systems shall be protected by incorporating network segmentation and segregation.
IMPORTANT_PR.AC-5.3: 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.
- Setting up and configuring routers, switches, firewalls, and wireless access points
- Performing regular maintenance, updates, and patching
- Monitoring network performance and identifying potential issues or security events
- Controlling access to network devices, ensuring only authorized personnel can make changes
- Keeping network device documentation and configurations up to date
IMPORTANT_PR.AC-5.4: 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.
IMPORTANT_PR.AC-6.1: The organization shall implement documented procedures for verifying the identity of individuals before issuing credentials that provide access to organization's systems.
IMPORTANT_PR.AC-7.1: The organization shall perform a documented risk assessment on organization's critical system transactions and authenticate users, devices, and other assets (e.g., single-factor, multi-factor) commensurate with the risk of the transaction (e.g., individuals’ security and privacy risks and other organizational risks).
- Systems must only be used for work-related purposes and in line with internal security policies
- Authentication credentials (e.g. usernames, passwords, MFA tokens) are personal, must not be shared, and must be stored and used securely
- Strong passwords and multi-factor authentication (MFA) are required where supported
- Credentials are issued during onboarding and revoked during offboarding or when roles change
- Enforced MFA or VPN access
- Restrictions on administrative use
- Monitoring and audit logging requirements
- Limiting access based on role or function
- All authentication must use Multi-Factor Authentication (MFA) or higher security measures.
- If MFA is not possible, passwords must be autogenerated and securely stored in a password management tool.
BASIC_PR.AT-1.1: Employees shall be trained as appropriate.
IMPORTANT_PR.AT-2.1: 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.
- Identify Key Roles:
- Define roles critical to cybersecurity (e.g., ISMS Manager,Security Analyst, Incident Response Lead).
- Map roles to the organization's cybersecurity objectives and ISMS scope.
- Document Responsibilities:
- Create role descriptions that include tasks, accountability, and reporting structures.
- Link responsibilities to specific ISMS requirements and NIS2 compliance tasks.
- Identify Required Qualifications:
- Define educational background, certifications (e.g., CISSP, CISM, ISO 27001 Lead Implementer), and technical skills for each role.
- Include soft skills such as problem-solving, communication, and risk management.
- Set Competence Standards:
- Outline expected levels of expertise (beginner, intermediate, advanced) for tasks like risk assessments, incident response, and ISMS audits.
- Document Competence Requirements:
- Maintain a record of qualifications and required skills in HR or ISMS documentation.
- Recruitment:
- Hire personnel with the qualifications and experience needed for cybersecurity roles.
- Verify credentials and conduct security clearance checks as required.
- Training and Development:
- Develop a training plan to address gaps in competence or knowledge.
- Offer regular training on new threats, technologies, and compliance requirements.
- Include certification programs and industry-standard courses.
- Training Monitoring:
- Track employee participation in training programs.
- Maintain training records as evidence of acquired qualifications.
- Supervision:
- Assign experienced mentors to supervise new or junior cybersecurity staff.
- Establish regular check-ins to ensure performance aligns with expectations.
- Maintain Records:
- Document certifications, training completion, and experience for all key personnel.
- Use HR systems or ISMS documentation to store and update records.
- Internal Audits:
- Regularly review and verify the accuracy of qualification records.
- Include competence assessments in ISMS internal audits.
- External Validation:
- Where required, ensure certifications are externally validated or accredited.
- Assess Staffing Levels:
- Regularly evaluate the number of cybersecurity personnel against current and projected needs.
- Use workload analysis and risk assessments to determine adequacy.
- Review Competence:
- Conduct periodic evaluations of staff competence through performance reviews or practical assessments.
- Adjust Staffing and Training:
- Address deficiencies by hiring additional personnel, increasing training, or reallocating resources.
- Owner of the Task:
- Assign a responsible owner (e.g., ISMS Manager) to oversee staffing and competence adequacy.
- Ensure reviews occur on a predefined schedule (e.g., quarterly or biannually).
IMPORTANT_PR.AT-1.2: The organization shall incorporate insider threat recognition and reporting into security awareness training.
IMPORTANT_PR.AT-3.1: The organization shall establish and enforce security requirements for business-critical third-party providers and users.
IMPORTANT_PR.AT-3.2: Third-party providers shall be required to notify any personnel transfers, termination, or transition involving personnel with physical or logical access to organization's business critical system's components.
IMPORTANT_PR.AT-3.3: The organization shall monitor business critical service providers and users for security compliance.
IMPORTANT_PR.AT-4.1: Senior executives shall demonstrate the understanding of their roles, responsibilities, and authorities.
- Identify External and Internal Requirements:
- Evaluate customer promises, contractual obligations, applicable regulations (e.g., GDPR, NIS2), and industry standards.
- Identify relevant certificates (e.g., ISO 27001, SOC 2) that align with business objectives.
- Document Frameworks:
- Record chosen frameworks and requirements in the Information Security Management System (ISMS) documentation.
- Ensure alignment with organizational goals and regulatory obligations.
- Review and Approve Frameworks:
- Management reviews the selected frameworks for adequacy and relevance.
- Approve and communicate these frameworks across the organization.
- Conduct Resource Assessment:
- Identify human, technical, and financial resources required to support cybersecurity initiatives. Include training programs, software tools, and infrastructure upgrades.
- Allocate Resources:
- Top management approves and allocates resources for cybersecurity tasks and projects.
- Include cybersecurity responsibilities in job roles and ensure skilled personnel are in place.
- Monitor Resource Utilization:
- Periodically review resource usage to ensure alignment with cybersecurity objectives.
- Adjust resource allocation as necessary to meet evolving security needs.
- Develop a Communication Plan:
- Outline methods for communicating cybersecurity priorities to all stakeholders. Use channels like town halls, newsletters, internal memos, and training sessions.
- Conduct Regular Training and Awareness Programs:
- Train employees on cybersecurity best practices, including their role in achieving organizational security objectives.
- Lead by Example:
- Top management actively participates in cybersecurity initiatives to demonstrate commitment.
- Define Measurable Objectives:
- Establish KPIs (e.g., number of incidents, compliance audit results) to track progress. Implement
- Monitoring Mechanisms:
- Use tools and processes to monitor and report on cybersecurity performance.
- Conduct regular audits and risk assessments.
- Review and Act:
- Top management reviews performance reports.
- Initiate corrective actions when objectives are not met.
- Conduct Regular Management Reviews:
- Review the ISMS scope, objectives, and results periodically. Include findings from risk assessments, audits, and incident reports.
- Implement Improvement Initiatives:
- Address identified gaps through updates to policies, technologies, or practices.
- Foster a Culture of Innovation:
- Encourage feedback from employees and stakeholders to improve processes.
- Identify Scope Parameters:
- Decide if the ISMS covers all organizational information and activities or specific parts.
- Document the Scope:
- Clearly define and record the ISMS scope in the system documentation. Include justifications for any exclusions.
- Communicate the Scope:
- Ensure stakeholders understand the ISMS scope and its relevance to their roles.
IMPORTANT_PR.AT-5.1: The organization shall ensure that personnel responsible for the physical protection and security of the organization's critical systems and facilities are qualified through training before privileges are granted, and that they understand their responsibilities.
BASIC_PR.DS-3.1: Assets and media shall be disposed of safely.
- Data Wiping: All HDDs undergo a multi-pass zero-filling process to overwrite all stored data, ensuring it is irretrievable.
- The zero-filling process is performed at least three times to eliminate any residual data.
- Verification checks are conducted to confirm complete data removal.
- Physical Destruction: After the zero-filling process, HDDs are physically destroyed by drilling through the platters to render them unusable.
- Final Disposal: The remains of the HDDs are placed in the designated trash bin intended for incineration in a furnace.
- Physical Destruction: Due to the nature of SSD storage, they are directly destroyed by drilling multiple holes through the memory chips to prevent data recovery.
- Final Disposal: The remains of the SSDs are placed in the designated trash bin intended for incineration in a furnace.
- Non-storage IT equipment and peripherals (excluding storage media) are collected for proper recycling.
- Recycling Partner: All recyclable components are handed over to Recupel, ensuring environmentally responsible disposal and compliance with electronic waste regulations.
- Media requiring disposal must be clearly marked as “For Secure Disposal.”
- Only authorized personnel are permitted to perform the disposal process.
- Disposal activities are logged for compliance and audit purposes.
- The destruction process ensures that no data remains recoverable, even through forensic means.
- Compliance with data protection and security policies is maintained.
- Periodic audits are conducted to ensure adherence to disposal procedures.
- IT Security Team: Ensures proper execution of disposal procedures.
- Compliance Officer: Verifies that disposal logs are maintained and audits the process.
- Authorized Personnel: Conducts media destruction and ensures secure disposal in accordance with this process.
- This process is reviewed annually or as needed to align with evolving security best practices and regulatory requirements.
- Data Protection: Removable media can easily be lost or stolen, leading to potential data breaches.
- Compliance Requirements: Regulatory frameworks such as GDPR, NIS2, and ISO 27001 require strict controls over the handling of sensitive data.
- Security Risks: These devices are susceptible to malware, unauthorized access, and potential misuse.
- Use company-approved encrypted cloud storage or secure file-sharing platforms.
- When necessary, transfer files via secure internal networks or encrypted email attachments.
- For exceptional cases, contact IT Security for approved methods of secure data transfer.
IMPORTANT_PR.DS-3.2: The organization shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.
- Data Wiping: All HDDs undergo a multi-pass zero-filling process to overwrite all stored data, ensuring it is irretrievable.
- The zero-filling process is performed at least three times to eliminate any residual data.
- Verification checks are conducted to confirm complete data removal.
- Physical Destruction: After the zero-filling process, HDDs are physically destroyed by drilling through the platters to render them unusable.
- Final Disposal: The remains of the HDDs are placed in the designated trash bin intended for incineration in a furnace.
- Physical Destruction: Due to the nature of SSD storage, they are directly destroyed by drilling multiple holes through the memory chips to prevent data recovery.
- Final Disposal: The remains of the SSDs are placed in the designated trash bin intended for incineration in a furnace.
- Non-storage IT equipment and peripherals (excluding storage media) are collected for proper recycling.
- Recycling Partner: All recyclable components are handed over to Recupel, ensuring environmentally responsible disposal and compliance with electronic waste regulations.
- Media requiring disposal must be clearly marked as “For Secure Disposal.”
- Only authorized personnel are permitted to perform the disposal process.
- Disposal activities are logged for compliance and audit purposes.
- The destruction process ensures that no data remains recoverable, even through forensic means.
- Compliance with data protection and security policies is maintained.
- Periodic audits are conducted to ensure adherence to disposal procedures.
- IT Security Team: Ensures proper execution of disposal procedures.
- Compliance Officer: Verifies that disposal logs are maintained and audits the process.
- Authorized Personnel: Conducts media destruction and ensures secure disposal in accordance with this process.
- This process is reviewed annually or as needed to align with evolving security best practices and regulatory requirements.
- Data Protection: Removable media can easily be lost or stolen, leading to potential data breaches.
- Compliance Requirements: Regulatory frameworks such as GDPR, NIS2, and ISO 27001 require strict controls over the handling of sensitive data.
- Security Risks: These devices are susceptible to malware, unauthorized access, and potential misuse.
- Use company-approved encrypted cloud storage or secure file-sharing platforms.
- When necessary, transfer files via secure internal networks or encrypted email attachments.
- For exceptional cases, contact IT Security for approved methods of secure data transfer.
IMPORTANT_PR.DS-4.1: Capacity planning shall ensure adequate resources for organization's critical system information processing, networking, telecommunications, and data storage.
- N-able Backup
- Sophos Cloud Optix
- VMware VirtualCenter
- Atera RMM
- Veeam Backup & Replication
IMPORTANT_PR.DS-5.1: The organization shall take appropriate actions resulting in the monitoring of its critical systems at external borders and critical internal points when unauthorized access and activities, including data leakage, is detected.
- Endpoint vulnerabilities are detected via SentinelOne.
- Server and infrastructure vulnerabilities are detected via ManageEngine Vulnerability Manager Plus (VAS).
- High and critical vulnerabilities are prioritized based on CVSS score, exploitability, and asset criticality.
- Vulnerabilities are tracked and managed in Jira from detection to closure.
- Patch management is coordinated between the Security Team and Infrastructure Team.
- SentinelOne alerts reviewed daily for critical vulnerabilities.
- VAS vulnerability scans reviewed weekly.
IMPORTANT_PR.DS-6.1: The organization shall implement software, firmware, and information integrity checks to detect unauthorized changes to its critical system components during storage, transport, start-up and when determined necessary.
- Change Request Initiation – A change is proposed and recorded, including scope, purpose, affected systems, and potential risks.
- Risk Assessment – The change is assessed using Cyberday’s built-in risk assessment process to evaluate its potential impact on information security.
- Approval Process – Changes are reviewed and approved by designated personnel based on risk and scope (e.g., IT lead, security officer, or service owner).
- Implementation & Testing – Approved changes are implemented during planned windows and, where applicable, tested in a staging environment before going live.
- Documentation & Communication – Change details, risk assessments, and decisions are documented and communicated to relevant stakeholders.
- Post-Implementation Review – If required, a review is conducted to ensure the change was successful and didn’t introduce unintended issues.
- Systems that support critical business operations (e.g., identity systems, communication tools, endpoint devices used for privileged access, backup infrastructure) are prioritized for continuous malware inspection.
- SentinelOne, the organization’s active endpoint protection platform, provides real-time monitoring of all running processes, memory operations, and file activities.
- Scheduled scans are not required due to SentinelOne’s behavior-based detection engine, which continuously analyzes system behavior for signs of compromise.
- All critical endpoints are monitored 24/7 by SentinelOne agents, which automatically detect and respond to:
- Fileless malware
- Ransomware
- Exploit attempts Known and unknown threats based on machine learning
- Detected threats are immediately quarantined, and the affected system is isolated from the network when necessary.
- Heimdal DNS filtering adds an additional layer of protection by blocking communication to known malicious domains, even before payloads are delivered.
- Enhance protection of web-based and content-based threats
- Add HTTPS traffic filtering for systems accessing the internet
- SentinelOne generates an automated alert and initiates the appropriate remediation action (e.g., kill process, quarantine, rollback).
- The Security Team is notified through the SentinelOne console and email (optional configuration).
- If the threat is confirmed to impact critical systems or data, the incident response plan is triggered, which includes:
- Containment (e.g., isolating affected system)
- Analysis and triage
- Root cause investigation (using log data and EDR forensics)
- Recovery and post-incident review
IMPORTANT_PR.IP-2.1: The system and application development life cycle shall include security considerations.
IMPORTANT_PR.IP-3.1: Changes shall be tested and validated before being implemented into operational systems.
- Identification & Risk Assessment: Significant changes are identified by the IT team. Since adopting Cyberday, each change undergoes a documented risk assessment. For earlier changes, informal assessments were discussed and are now retroactively documented where applicable.
- Approval Process: In our small team, approvals are given during IT sync meetings or directly between stakeholders. We record this in Jira tickets or internal documentation using a standard approval comment format.
- Impact & Mitigation Documentation: We have introduced a short checklist to record potential impacts and planned mitigation steps. This is now part of our change documentation process. Post-Implementation Review: After the change, we log whether it was successful and note any issues or lessons learned. This is done via comments on Jira tasks.
- Communication: Changes and their potential impacts are communicated to management during regular team meetings. This is logged in ticket comments or meeting summaries.
BASIC_PR.IP-4.1: Backups for organization's business critical data shall be conducted and stored on a system different from the device on which the original data resides
- Veeam: Used for backing up servers and M365 in our private cloud.
- N-able SaaS: Used for backing up Microsoft 365 services, including emails, SharePoint, Teams, and OneDrive.
- Criticality Assessment: Each data asset is assessed based on its criticality to determine the backup frequency and retention period.
- Backup Frequency:
- Microsoft 365 (N-able SaaS)
- Emails are backed up four times per day.
- Files (SharePoint, Teams, OneDrive) are backed up three times per day.
- Private Cloud (Veeam)
- Virtual machines, databases, and critical infrastructure components are backed up daily with incremental backups every hour for mission-critical workloads.
- Retention Period:
- Microsoft 365 backups: Retained for 90 days.
- Veeam backups: Retention policies are defined based on the system's importance, ranging from 90 days to several years for compliance reasons.
- Backup Locations:
- Veeam backups are stored in our private cloud with replication to an off-site location for redundancy.
- N-able SaaS backups are stored in a secure cloud-based storage environment.
- Security Measures:
- Backups are encrypted both in transit and at rest.
- Access to backup systems is restricted to authorized personnel only.
- Multi-factor authentication (MFA) is enforced for backup management access.
- Regular integrity checks and test restores are performed to validate backup reliability.
- Data is retained according to business, legal, and compliance requirements.
- Older backups that exceed the retention period are automatically deleted unless required for long-term archival.
- Special backup retention may be applied for compliance audits or legal holds.
- Procedures Restorations are conducted based on business needs and priority levels.
- Authorized personnel can request restores via the IT service desk.
- Critical system recovery tests are performed periodically to ensure backup effectiveness.
- This backup policy is reviewed annually or when significant changes occur in IT infrastructure or business needs.
- Updates will be documented and communicated to relevant stakeholders.
- This policy aligns with regulatory requirements such as GDPR, NIS2, and ISO 27001.
- Non-compliance with backup procedures may result in disciplinary action or security remediation measures.
IMPORTANT_PR.IP-4.2: The reliability and integrity of backups shall be verified and tested on regular basis.
IMPORTANT_PR.IP-4.3: A separate alternate storage site for system backups shall be operated and the same security safeguards as the primary storage location shall be employed.
- Veeam: Used for backing up servers and M365 in our private cloud.
- N-able SaaS: Used for backing up Microsoft 365 services, including emails, SharePoint, Teams, and OneDrive.
- Criticality Assessment: Each data asset is assessed based on its criticality to determine the backup frequency and retention period.
- Backup Frequency:
- Microsoft 365 (N-able SaaS)
- Emails are backed up four times per day.
- Files (SharePoint, Teams, OneDrive) are backed up three times per day.
- Private Cloud (Veeam)
- Virtual machines, databases, and critical infrastructure components are backed up daily with incremental backups every hour for mission-critical workloads.
- Retention Period:
- Microsoft 365 backups: Retained for 90 days.
- Veeam backups: Retention policies are defined based on the system's importance, ranging from 90 days to several years for compliance reasons.
- Backup Locations:
- Veeam backups are stored in our private cloud with replication to an off-site location for redundancy.
- N-able SaaS backups are stored in a secure cloud-based storage environment.
- Security Measures:
- Backups are encrypted both in transit and at rest.
- Access to backup systems is restricted to authorized personnel only.
- Multi-factor authentication (MFA) is enforced for backup management access.
- Regular integrity checks and test restores are performed to validate backup reliability.
- Data is retained according to business, legal, and compliance requirements.
- Older backups that exceed the retention period are automatically deleted unless required for long-term archival.
- Special backup retention may be applied for compliance audits or legal holds.
- Procedures Restorations are conducted based on business needs and priority levels.
- Authorized personnel can request restores via the IT service desk.
- Critical system recovery tests are performed periodically to ensure backup effectiveness.
- This backup policy is reviewed annually or when significant changes occur in IT infrastructure or business needs.
- Updates will be documented and communicated to relevant stakeholders.
- This policy aligns with regulatory requirements such as GDPR, NIS2, and ISO 27001.
- Non-compliance with backup procedures may result in disciplinary action or security remediation measures.
IMPORTANT_PR.IP-5.1: The organization shall define, implement, and enforce policy and procedures regarding emergency and safety systems, fire protection systems, and environment controls for its critical systems.
- basic services are tested regularly
- basic services are equipped with appropriate alarm systems that detect malfunctions
- basic services are brought to the premises via several supply lines running on different physical routes
- Equipment shall be located so that access to work areas is inherently kept to a minimum.
- Critical facilities shall be protected, if necessary, by separate additional arrangements. , in order to keep the overall protection required limited
- Processing of sensitive information shall be carried out in a location that does not allow illicit viewing
- Identify critical equipment that requires surge protection and UPS backup (e.g., servers, network devices, security systems).
- Assess the power stability in the environment and determine the need for additional protective measures.
- Ensure compliance with industry standards (e.g., ISO 27001 A.13 for power supply security, IEC 62040 for UPS systems).
- Install surge protectors at:
- Power entry points to prevent voltage spikes from damaging systems.
- Workstations and server racks to protect individual devices.
- Network and communication lines to shield against transient surges.
- Conduct regular inspections and replacements of surge protectors to ensure functionality.
- Connect critical equipment to an appropriately sized UPS system to:
- Provide temporary power during short outages.
- Prevent data loss by allowing a graceful shutdown if power loss is prolonged.
- Stabilize power fluctuations and reduce the risk of hardware damage.
- Configure UPS monitoring and alerting systems to track power status and battery health.
- Perform tests on surge protectors and UPS systems to ensure reliability.
- Monitor battery health and replace aging UPS batteries as needed.
- Maintain a log of power incidents, including UPS activations and system shutdowns.
IMPORTANT_PR.IP-6.1: The organization shall ensure that its critical system's data is destroyed according to policy.
- Data Wiping: All HDDs undergo a multi-pass zero-filling process to overwrite all stored data, ensuring it is irretrievable.
- The zero-filling process is performed at least three times to eliminate any residual data.
- Verification checks are conducted to confirm complete data removal.
- Physical Destruction: After the zero-filling process, HDDs are physically destroyed by drilling through the platters to render them unusable.
- Final Disposal: The remains of the HDDs are placed in the designated trash bin intended for incineration in a furnace.
- Physical Destruction: Due to the nature of SSD storage, they are directly destroyed by drilling multiple holes through the memory chips to prevent data recovery.
- Final Disposal: The remains of the SSDs are placed in the designated trash bin intended for incineration in a furnace.
- Non-storage IT equipment and peripherals (excluding storage media) are collected for proper recycling.
- Recycling Partner: All recyclable components are handed over to Recupel, ensuring environmentally responsible disposal and compliance with electronic waste regulations.
- Media requiring disposal must be clearly marked as “For Secure Disposal.”
- Only authorized personnel are permitted to perform the disposal process.
- Disposal activities are logged for compliance and audit purposes.
- The destruction process ensures that no data remains recoverable, even through forensic means.
- Compliance with data protection and security policies is maintained.
- Periodic audits are conducted to ensure adherence to disposal procedures.
- IT Security Team: Ensures proper execution of disposal procedures.
- Compliance Officer: Verifies that disposal logs are maintained and audits the process.
- Authorized Personnel: Conducts media destruction and ensures secure disposal in accordance with this process.
- This process is reviewed annually or as needed to align with evolving security best practices and regulatory requirements.
IMPORTANT_PR.IP-7.1: The organization shall incorporate improvements derived from the monitoring, measurements, assessments, and lessons learned into protection process updates (continuous improvement).
IMPORTANT_PR.IP-8.1: The organization shall collaborate and share information about its critical system's related security incidents and mitigation measures with designated partners.
IMPORTANT_PR.IP-8.2: Communication of effectiveness of protection technologies shall be shared with appropriate parties.
IMPORTANT_PR.IP-9.1: Incident response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) shall be established, maintained, approved, and tested to determine the effectiveness of the plans, and the readiness to execute the plans.
BASIC_PR.IP-11.1: Personnel having access to the organization’s most critical information or technology shall be verified.
IMPORTANT_PR.IP-11.2: Develop and maintain a human resource information/cyber security process that is applicable when recruiting, during employment and at termination of employment.
IMPORTANT_PR.IP-12.1: The organization shall establish and maintain a documented process that allows continuous review of vulnerabilities and strategies to mitigate them.
- Endpoint vulnerabilities are detected via SentinelOne.
- Server and infrastructure vulnerabilities are detected via ManageEngine Vulnerability Manager Plus (VAS).
- High and critical vulnerabilities are prioritized based on CVSS score, exploitability, and asset criticality.
- Vulnerabilities are tracked and managed in Jira from detection to closure.
- Patch management is coordinated between the Security Team and Infrastructure Team.
- SentinelOne alerts reviewed daily for critical vulnerabilities.
- VAS vulnerability scans reviewed weekly.
- Veeam Backup & Replication
- Microsoft Azure Active Directory
- XDR
- Microsoft Authenticator
- Microsoft Defender for Endpoint
- Microsoft Defender for Cloud Apps
- Devolution RDM
- Microsoft Defender for Office 365 (MDO)
- Microsoft BitLocker
- Heimdal
- FileVault
BASIC_PR.MA-1.1: Patches and security updates for Operating Systems and critical system components shall be installed.
- Microsoft Azure Active Directory
- Microsoft Entra
IMPORTANT_PR.MA-1.2: The organization shall plan, perform and document preventive maintenance and repairs on its critical system components according to approved processes and tools.
- Repairs and maintenance is only executed by qualified personnel
- Confidential information is removed from the equipment before maintenance is performed, if necessary
- Equipment is inspected after maintenance before their deployment to ensure that devices are not tampered with or still malfunctioning
IMPORTANT_PR.MA-1.3: The organization shall enforce approval requirements, control, and monitoring of maintenance tools for use on the its critical systems.
- Every Sunday, the on-call system engineer performs routine maintenance on the equipment.
- Maintenance tasks include preventive actions, remedial actions, and defect checks.
- The system engineer records maintenance activities in a Maintenance Log, including:
- Suspected and actual defects identified during the inspection.
- Preventive actions taken to avoid future failures.
- Remedial actions applied to resolve existing defects.
- Post-maintenance equipment check results to confirm proper functionality.
- If an issue is critical, an immediate incident report is created and escalated.
- The completed maintenance log is reviewed by the IT operations manager or a designated authority.
- Any recurring defects or trends are analyzed for long-term improvements.
- If a significant defect is found that affects system reliability or security, it is:
- Escalated to senior engineers for further diagnosis.
- Documented in an incident management system for tracking.
IMPORTANT_PR.MA-1.4: The organization shall verify security controls following hardware maintenance or repairs, and take action as appropriate.
- Every Sunday, the on-call system engineer performs routine maintenance on the equipment.
- Maintenance tasks include preventive actions, remedial actions, and defect checks.
- The system engineer records maintenance activities in a Maintenance Log, including:
- Suspected and actual defects identified during the inspection.
- Preventive actions taken to avoid future failures.
- Remedial actions applied to resolve existing defects.
- Post-maintenance equipment check results to confirm proper functionality.
- If an issue is critical, an immediate incident report is created and escalated.
- The completed maintenance log is reviewed by the IT operations manager or a designated authority.
- Any recurring defects or trends are analyzed for long-term improvements.
- If a significant defect is found that affects system reliability or security, it is:
- Escalated to senior engineers for further diagnosis.
- Documented in an incident management system for tracking.
BASIC_PR.PT-1.1: Logs shall be maintained, documented, and reviewed.
IMPORTANT_PR.PT-1.2: The organization shall ensure that the log records include an authoritative time source or internal clock time stamp that are compared and synchronized to an authoritative time source.
IMPORTANT_PR.PT-2.1: The usage restriction of portable storage devices shall be ensured through an appropriate documented policy and supporting safeguards.
- Data Protection: Removable media can easily be lost or stolen, leading to potential data breaches.
- Compliance Requirements: Regulatory frameworks such as GDPR, NIS2, and ISO 27001 require strict controls over the handling of sensitive data.
- Security Risks: These devices are susceptible to malware, unauthorized access, and potential misuse.
- Use company-approved encrypted cloud storage or secure file-sharing platforms.
- When necessary, transfer files via secure internal networks or encrypted email attachments.
- For exceptional cases, contact IT Security for approved methods of secure data transfer.
IMPORTANT_PR.PT-2.2: The organisation should technically prohibit the connection of removable media unless strictly necessary; in other instances, the execution of autoruns from such media should be disabled.
- Data Protection: Removable media can easily be lost or stolen, leading to potential data breaches.
- Compliance Requirements: Regulatory frameworks such as GDPR, NIS2, and ISO 27001 require strict controls over the handling of sensitive data.
- Security Risks: These devices are susceptible to malware, unauthorized access, and potential misuse.
- Use company-approved encrypted cloud storage or secure file-sharing platforms.
- When necessary, transfer files via secure internal networks or encrypted email attachments.
- For exceptional cases, contact IT Security for approved methods of secure data transfer.
IMPORTANT_PR.PT-3.1: The organization shall configure the business critical systems to provide only essential capabilities.
- The organization uses Heimdal Application Control to enforce a default-deny policy for software execution on endpoints.
- Only pre-approved software is allowed to run.
- Any execution attempt of unknown or unauthorized applications is automatically blocked and logged.
- Application control policies are maintained and reviewed by the Security Team in alignment with business requirements and risk assessments.
- SentinelOne provides real-time detection of unknown or potentially unwanted applications (PUAs), even if not explicitly blacklisted.
- It flags suspicious executables, scripts, and anomalous behavior.
- It can automatically quarantine or kill unauthorized processes and isolate affected devices.
- Detected applications or behavior are reviewed by the Security Team through the SentinelOne console.
- The organization does not currently operate a traditional network-based Intrusion Detection System (IDS).
- However, equivalent functionality is provided at the endpoint level through:
- Heimdal and SentinelOne behavioral analysis
- DNS filtering to prevent unauthorized communications
- Alerting mechanisms for known malicious or unauthorized software behavior
- Microsoft Authenticator
- Heimdal
- SentinelOne Singularity
- Sophos Intercept X: Next-Gen Endpoint
BASIC_PR.PT-4.1: Web and e-mail filters shall be installed and used.
- The organization has deployed SentinelOne as the primary malware protection platform.
- SentinelOne is an enterprise-grade EDR (Endpoint Detection and Response) solution that provides real-time protection, behavioral detection, and autonomous response.
- Sophos is being onboarded to further strengthen endpoint security, web filtering, and malware detection across the environment.
- Coverage across Windows/macOS environments
- Real-time detection capabilities
- Centralized policy management and alerting
- Integration potential with other security platforms
- SentinelOne is installed on all corporate laptops and workstations.
- Deployment is managed centrally by the Security Team and monitored via the SentinelOne console.
- Sophos is being rolled out in phases and will be fully integrated upon completion of testing and policy configuration.
- Signature databases and behavioral detection rules in SentinelOne are updated automatically.
- Software agents are centrally managed and monitored for update compliance.
- Sophos endpoint agents will follow the same approach once live, receiving real-time updates from the Sophos Central platform.
- SentinelOne performs real-time scanning of:
- Files written to disk
- Scripts executed on the system
- Payloads dropped by applications or browser sessions
- Microsoft Defender for Office 365 (via Entra ecosystem) provides cloud-based scanning of:
- Email attachments
- Embedded links
- Downloaded files in Microsoft 365 services
- Sophos is expected to introduce additional web-layer scanning and inspection of HTTPS traffic (once deployed).
- The organization currently uses Heimdal DNS Security to block known malicious domains before users can connect to them.
- SentinelOne detects and blocks access to known Command & Control domains or payload delivery sites based on threat intelligence.
- Sophos will extend protection with URL classification, web content filtering, and file reputation scoring once fully implemented.
- SentinelOne performs continuous behavioral monitoring rather than scheduled signature-based scans.
- Any detected threats trigger automated responses, including isolation, remediation, and alerting.
- Routine scanning of removable media is managed through endpoint policy enforcement.
- The organization includes malware awareness as part of onboarding and periodic security training.
- Employees are instructed to:
- Avoid downloading software from unverified sources
- Report suspicious attachments or files
- Notify IT Security in case of unusual system behavior
- Managing firewall rules and NAT configurations
- Updating and maintaining pfSense software and packages
- Reviewing and applying changes based on operational or security needs
- Documenting configuration changes and retaining version history as part of internal change management
- Ensuring that only authorized personnel have administrative access to pfSense
- Microsoft Azure Active Directory
- XDR
- Microsoft Defender for Endpoint
- Microsoft Authenticator
- Microsoft Defender for Cloud Apps
- AdminDroid
- Microsoft Defender for Office 365 (MDO)
- Heimdal
- SentinelOne Singularity
- Tailscale
- pfSense
PROTECT
Develop and implement appropriate safeguards to ensure delivery of critical infrastructure services.
DETECT
IMPORTANT_DE.AE-2.1: The organization shall review and analyze detected events to understand attack targets and methods.
- Failed login attempts
- Privilege escalations
- Malware detection
- Suspicious application execution
- DNS filtering violations
- AdminDroid, which collects and summarizes Microsoft 365 audit data and sends alert emails for preconfigured criteria
- Heimdal and SentinelOne, which surface actionable events through their internal alerting engines
- Microsoft Defender for Endpoint, which provides real-time alerts and investigation capabilities
- Entra ID & M365: Log filtering and export through the Microsoft 365 Compliance Center and Entra portal
- AdminDroid: Prebuilt reports and alerts based on M365 logs
- Heimdal: Web-based dashboard for DNS/app control filtering and alerting
- SentinelOne: Alert console for real-time threat insights
- FortiGate/pfSense: Admin dashboards for firewall traffic and VPN logs
- Authentication anomalies (e.g., repeated failed logins, risky sign-ins)
- Privileged role assignments or changes
- Threat detection (malware, ransomware, exploit attempts)
- Unusual user behavior (e.g., unexpected file sharing, mailbox access)
- Network anomalies (e.g., unexpected VPN connections, port scanning)
- Logs from Microsoft systems are available through AdminDroid and Defender interfaces
- Security event correlation is handled at the platform level
- Sophos onboarding is in progress, and will support log analysis and possibly central correlation in the future
- AdminDroid
- Heimdal
- SentinelOne Singularity
- Sophos Intercept X: Next-Gen Endpoint
BASIC_DE.AE-3.1: The activity logging functionality of protection / detection hardware or software (e.g. firewalls, anti-virus) shall be enabled, backed-up and reviewed.
- AdminDroid
- XDR
- Microsoft Defender for Endpoint
- Heimdal
IMPORTANT_DE.AE-5.1: The organization shall implement automated mechanisms and system generated alerts to support event detection and to assist in the identification of security alert thresholds.
- Microsoft Azure Active Directory
- XDR
- Microsoft Defender for Endpoint
- Microsoft Defender for Cloud Apps
- AdminDroid
- Microsoft Defender for Office 365 (MDO)
- Microsoft BitLocker
- Heimdal
- SentinelOne Singularity
BASIC_DE.CM-1.1: Firewalls shall be installed and operated on the network boundaries and completed with firewall protection on the endpoints.
- Use of security technologies: All critical services utilize technologies such as strong authentication (admin access control), encrypted communications (e.g., HTTPS, VPN), and firewall protection.
- Defined technical parameters: Network devices are configured with strict access rules, port restrictions, and default service deactivation to minimize exposure.
- Service-level requirements: Critical equipment is monitored and maintained by the Network Operations Center (NOC), with regular updates and configuration backups in place.
- Access and usage criteria: Only authorized personnel have access to manage or configure network equipment. Usage is restricted through VLANs, network segmentation, and role-based access.
- Lifecycle management: Any implementation or update of network equipment includes security requirement verification before deployment.
IMPORTANT_DE.CM-1.2: The organization shall monitor and identify unauthorized use of its business critical systems through the detection of unauthorized local connections, network connections and remote connections.
- Network traffic data (inbound/outbound)
- Access logs from critical systems and network devices
- Security tool logs (firewalls, IDS/IPS, antivirus)
- Configuration change logs
- Configure automated log collection from relevant sources.
- Ensure logs are timestamped and stored securely.
- Utilize a centralized log management system (e.g., SIEM).
- Continuous log data stream for analysis.
- Collected logs and monitoring data
- Defined normal behavior baselines
- Apply real-time analysis using AI-based detection or rule-based anomaly detection.
- Identify deviations from normal network behavior.
- Flag suspicious activities (e.g., unusual data transfers, unauthorized access attempts).
- Alerts generated by the monitoring system
- Investigate alerts to determine
- if they represent an actual security threat.
- Cross-check anomalies against known system behaviors.
- If identified as a false positive, adjust detection rules.
- If confirmed as a security incident, escalate to the response team.
- Verified security incident report or refined detection rules.
- Verified security incident report
- Classify the incident (e.g., unauthorized access, malware, data exfiltration).
- Execute predefined incident response procedures.
- Contain the threat (e.g., isolate compromised systems, block malicious IPs).
- Apply security patches or system reconfigurations as necessary.
- Incident resolution report with applied mitigation actions.
- Heimdal
- SentinelOne Singularity
- Atera RMM
- pfSense
IMPORTANT_DE.CM-2.1: The physical environment of the facility shall be monitored for potential information/cybersecurity events.
- Strategic Camera Placement: We conduct a thorough security assessment of the property to identify vulnerable entry points, high-traffic areas, and blind spots. Cameras are positioned at these locations to maximize coverage and minimize potential security gaps.
- Real-Time Monitoring & Alerts: The motion detection cameras are connected to a centralized monitoring system, which instantly alerts security personnel or property management when movement is detected outside of scheduled activity hours.
- High-Resolution Video & Night Vision: Our cameras are equipped with high-definition (HD) recording and infrared night vision to ensure clear visibility, even in low-light conditions. This feature enhances security during nighttime hours when properties are more vulnerable to intrusions.
- Automated Recording: When motion is detected, the system automatically records footage. This ensures that all security events are documented and accessible for future review or evidence if needed.
- Remote Access & Mobile Notifications: Property owners and security teams can remotely access live camera feeds through a secure mobile app or web portal. This allows for real-time viewing and incident verification from anywhere, providing flexibility and control over security management.
- Primary Authentication: Access card, biometric authentication (fingerprint, facial recognition), or security token.
- Secondary Authentication: PIN, passcode, or one-time password (OTP) generated via an authenticator app.
- VPN Requirement: For accessing highly secure data storage, a VPN connection must be established in addition to the above authentication steps to ensure secure remote access.
- Security Officer: Oversees the implementation and enforcement of access control measures.
- IT Administrator: Manages authentication systems, including biometric devices, access control logs, and password policies.
- Facility Manager: Ensures physical security infrastructure, such as access doors, locks, and surveillance, is in place and operational.
- Authorized Personnel: Must comply with authentication policies and report any anomalies in access control.
- Request Submission: Employees requiring access must submit a request to the Security Officer.
- Authorization Check: Security Officer reviews the request based on job function, clearance level, and necessity.
- Approval & Enrollment: If approved, the IT Administrator enrolls the individual in the authentication system and provides necessary credentials.
- Access Granting: The employee is granted access based on predefined timeframes or conditions.
- All personnel must authenticate using both primary and secondary authentication before entering a secure area.
- Multi-factor authentication (MFA) mechanisms must be periodically tested and updated to mitigate security risks.
- Temporary access (e.g., for maintenance or audits) must be limited and monitored.
- For remote access to very secure data storage, a VPN connection must be used to ensure encrypted and controlled data access.
- All access attempts must be logged, including date, time, and user identity.
- Any failed authentication attempts or unauthorized access attempts must trigger an alert to security personnel.
- Logs should be reviewed regularly to identify potential security threats.
- Unauthorized Access Attempt:
- Immediate lockdown of the secure area.
- Security team notified for investigation.
- Lost or Stolen Credentials:
- Immediate deactivation of lost credentials.
- Reissuance of new authentication factors.
- Suspicious Activity Detection:
- Investigation and audit of access logs.
- Implementation of additional security measures if necessary.
- Conduct quarterly reviews of access control policies.
- Ensure compliance with regulatory requirements and internal security policies.
- Perform periodic penetration tests and security audits on the authentication mechanisms.
- Access must be revoked immediately when an employee resigns, is terminated, or no longer requires access.
- Regular audits should be performed to ensure that only authorized individuals have active access rights.
- All personnel must be trained on access control policies and the importance of secure authentication.
- Regular awareness programs should be conducted to highlight security risks and best practices.
- Microsoft Azure Active Directory
- Microsoft Authenticator
- Devolution RDM
- OpenVPN
- Tailscale
BASIC_DE.CM-3.1: End point and network protection tools to monitor end-user behavior for dangerous activity shall be implemented.
- Managing firewall rules and NAT configurations
- Updating and maintaining pfSense software and packages
- Reviewing and applying changes based on operational or security needs
- Documenting configuration changes and retaining version history as part of internal change management
- Ensuring that only authorized personnel have administrative access to pfSense
- Tailscale
- pfSense
IMPORTANT_DE.CM-3.2: End point and network protection tools that monitor end-user behavior for dangerous activity shall be managed.
- Managing firewall rules and NAT configurations
- Updating and maintaining pfSense software and packages
- Reviewing and applying changes based on operational or security needs
- Documenting configuration changes and retaining version history as part of internal change management
- Ensuring that only authorized personnel have administrative access to pfSense
- Tailscale
- pfSense
BASIC_DE.CM-4.1: Anti-virus, -spyware, and other -malware programs shall be installed and updated.
- The organization has deployed SentinelOne as the primary malware protection platform.
- SentinelOne is an enterprise-grade EDR (Endpoint Detection and Response) solution that provides real-time protection, behavioral detection, and autonomous response.
- Sophos is being onboarded to further strengthen endpoint security, web filtering, and malware detection across the environment. All endpoint protection tools are selected based on: Coverage across Windows/macOS environments Real-time detection capabilities Centralized policy management and alerting Integration potential with other security platforms
- SentinelOne is installed on all corporate laptops and workstations.
- Deployment is managed centrally by the Security Team and monitored via the SentinelOne console.
- Sophos is being rolled out in phases and will be fully integrated upon completion of testing and policy configuration.
- Signature databases and behavioral detection rules in SentinelOne are updated automatically.
- Software agents are centrally managed and monitored for update compliance.
- Sophos endpoint agents will follow the same approach once live, receiving real-time updates from the Sophos Central platform.
- SentinelOne performs real-time scanning of:
- Files written to disk
- Scripts executed on the system
- Payloads dropped by applications or browser sessions
- Microsoft Defender for Office 365 (via Entra ecosystem) provides cloud-based scanning of:
- Email attachments
- Embedded links
- Downloaded files in Microsoft 365 services
- Sophos is expected to introduce additional web-layer scanning and inspection of HTTPS traffic (once deployed).
- The organization currently uses Heimdal DNS Security to block known malicious domains before users can connect to them.
- SentinelOne detects and blocks access to known Command & Control domains or payload delivery sites based on threat intelligence.
- Sophos will extend protection with URL classification, web content filtering, and file reputation scoring once fully implemented.
- SentinelOne performs continuous behavioral monitoring rather than scheduled signature-based scans.
- Any detected threats trigger automated responses, including isolation, remediation, and alerting.
- Routine scanning of removable media is managed through endpoint policy enforcement.
- The organization includes malware awareness as part of onboarding and periodic security training.
- Employees are instructed to:
- Avoid downloading software from unverified sources
- Report suspicious attachments or files
- Notify IT Security in case of unusual system behavior
- Microsoft Azure Active Directory
- XDR
- Microsoft Defender for Endpoint
- Microsoft Authenticator
- Microsoft Defender for Cloud Apps
- AdminDroid
- Microsoft Defender for Office 365 (MDO)
- Heimdal
- SentinelOne Singularity
- Sophos Intercept X: Next-Gen Endpoint
- Business-critical: Always allowed (e.g., SaaS tools, corporate portals)
- Acceptable use: Allowed but monitored (e.g., news, productivity tools)
- Restricted: Blocked categories, such as:
- Adult content
- Gambling
- Hacking-related resources
- Cryptocurrency mining
- Piracy and illegal downloads
- Malware distribution sources
- Phishing pages
- Botnet command & control servers
- Recently registered or suspicious domains (via Heimdal’s threat intelligence feed)
- Pirated software or media
- Unlicensed software download sites
- Sites flagged by Heimdal under “Illegal Content” categories
- Heimdal DNS Security (in production)
- Protects users at the DNS layer by preventing name resolution for blocked domains
- Includes policy management, alerting, and dashboard visibility
- Sophos Web Filtering (planned)
- Will provide HTTPS-level inspection and content filtering
- Expected to be deployed as part of the endpoint protection platform
- Will complement DNS filtering by identifying threats in real-time based on URL and content inspection
- Blocking policies apply to all managed devices and remote users via the endpoint agent (Heimdal).
- Security Team is responsible for managing Heimdal policies and will also handle Sophos filtering once deployed.
- Any policy exceptions or site allow-list requests must go through IT Security review and approval.
- Systems that support critical business operations (e.g., identity systems, communication tools, endpoint devices used for privileged access, backup infrastructure) are prioritized for continuous malware inspection.
- SentinelOne, the organization’s active endpoint protection platform, provides real-time monitoring of all running processes, memory operations, and file activities.
- Scheduled scans are not required due to SentinelOne’s behavior-based detection engine, which continuously analyzes system behavior for signs of compromise.
- All critical endpoints are monitored 24/7 by SentinelOne agents, which automatically detect and respond to:
- Fileless malware
- Ransomware
- Exploit attempts
- Known and unknown threats based on machine learning
- Detected threats are immediately quarantined, and the affected system is isolated from the network when necessary.
- Heimdal DNS filtering adds an additional layer of protection by blocking communication to known malicious domains, even before payloads are delivered.
- Enhance protection of web-based and content-based threats
- Add HTTPS traffic filtering for systems accessing the internet
- SentinelOne generates an automated alert and initiates the appropriate remediation action (e.g., kill process, quarantine, rollback).
- The Security Team is notified through the SentinelOne console and email (optional configuration).
- If the threat is confirmed to impact critical systems or data, the incident response plan is triggered, which includes:
- Containment (e.g., isolating affected system)
- Analysis and triage
- Root cause investigation (using log data and EDR forensics)
- Recovery and post-incident review
- SentinelOne – Primary endpoint detection and response (EDR) solution
- Microsoft Defender – Running in passive mode, providing additional insight via Microsoft 365 integration
- Heimdal Security – DNS-based filtering, Application Control
- Sophos – Endpoint and web protection (currently being onboarded)
- SentinelOne provides real-time behavioral detection, rollback, and isolation capabilities.
- Defender, while in passive mode, contributes to:
- Microsoft 365 threat analytics
- Cloud-delivered protection (e.g., SmartScreen)
- Alert correlation in Defender for Endpoint portal
- Heimdal blocks malicious domains and applications pre-execution.
- Sophos (once live) will add HTTPS content inspection and file-based scanning.
- Fileless malware
- Domain-based threats (phishing, C2 servers)
- Behavioral anomalies
- Threats that may bypass signature-based tools
- If one layer misses a threat, others may catch it:
- Heimdal blocks access before contact is made with a malicious host
- SentinelOne reacts to process behavior at runtime
- Microsoft Defender detects suspicious file downloads through SmartScreen or Defender for Office
- Endpoint agents operate independently, adding resilience if one service fails or is unavailable.
- The Security Team evaluates the vendor stack regularly to: Eliminate unnecessary overlap
- Ensure efficient performance on endpoints
- Align capabilities with current threats and business needs
- Sophos deployment is being assessed to ensure it complements, not duplicates, existing functionality from SentinelOne and Defender.
IMPORTANT_DE.CM-5.1: The organization shall define acceptable and unacceptable mobile code and mobile code technologies; and authorize, monitor, and control the use of mobile code within the system.
- Company-Owned Devices: Enroll in Microsoft Intune for centralized management.
- Apple Devices: Use Apple Business Manager for streamlined deployment and management.
- Bring Your Own Device (BYOD): Enforce conditional access policies in Microsoft Entra to secure personal devices before granting access to corporate resources.
- Configure device compliance policies (e.g., encryption, password strength, and OS updates).
- Enforce remote wipe capabilities for lost or stolen devices.
- Restrict access to corporate data on non-compliant devices.
- Use Intune reporting to track device compliance and security status.
- Regularly review access logs and security reports to detect anomalies.
- Restrict corporate apps and data to managed devices only.
- Use app protection policies to prevent unauthorized data sharing.
- Regularly assess and refine mobile security policies based on evolving threats.
- Ensure BYOD users remain compliant with security requirements before accessing corporate resources.
- The organization uses Heimdal Application Control to enforce a default-deny policy for software execution on endpoints.
- Only pre-approved software is allowed to run.
- Any execution attempt of unknown or unauthorized applications is automatically blocked and logged.
- Application control policies are maintained and reviewed by the Security Team in alignment with business requirements and risk assessments.
- SentinelOne provides real-time detection of unknown or potentially unwanted applications (PUAs), even if not explicitly blacklisted.
- It flags suspicious executables, scripts, and anomalous behavior.
- It can automatically quarantine or kill unauthorized processes and isolate affected devices.
- Detected applications or behavior are reviewed by the Security Team through the SentinelOne console.
- The organization does not currently operate a traditional network-based Intrusion Detection System (IDS).
- However, equivalent functionality is provided at the endpoint level through:
- Heimdal and SentinelOne behavioral analysis
- DNS filtering to prevent unauthorized communications
- Alerting mechanisms for known malicious or unauthorized software behavior
IMPORTANT_DE.CM-6.1: All external connections by vendors supporting IT/OT applications or infrastructure shall be secured and actively monitored to ensure that only permissible actions occur during the connection.
IMPORTANT_DE.CM-6.2: External service providers' conformance with personnel security policies and procedures and contract security requirements shall be monitored relative to their cybersecurity risks.
- Code Review: Internal teams approve code
- Testing Evidence: Partners must provide unit, integration, and security test results.
- Communication: Regular meetings and real-time updates via collaboration platforms.
- Audit Rights: Contracts must allow audits of development processes and tools.
- Documentation: Maintain design documents, change logs, and security reports.
- Periodic security audits and reviews.
- Continuous refinement based on feedback and evolving compliance needs.
IMPORTANT_DE.CM-7.1: The organization's business critical systems shall be monitored for unauthorized personnel access, connections, devices, access points, and software.
- Periodically (e.g., weekly/monthly) by the NOC
- In response to anomalies, such as user reports, alerts, or system behavior changes
IMPORTANT_DE.CM-8.1: The organization shall monitor and scan for vulnerabilities in its critical systems and hosted applications ensuring that system functions are not adversely impacted by the scanning process.
- Veeam Backup & Replication
- Microsoft Azure Active Directory
- XDR
- Microsoft Authenticator
- Microsoft Defender for Endpoint
- Microsoft Defender for Cloud Apps
- Devolution RDM
- Microsoft Defender for Office 365 (MDO)
- Microsoft BitLocker
- Heimdal
- FileVault
IMPORTANT_DE.CM-8.2: The vulnerability scanning process shall include analysis, remediation, and information sharing.
- Veeam Backup & Replication
- Microsoft Azure Active Directory
- XDR
- Microsoft Authenticator
- Microsoft Defender for Endpoint
- Microsoft Defender for Cloud Apps
- Devolution RDM
- Microsoft Defender for Office 365 (MDO)
- Microsoft BitLocker
- Heimdal
- FileVault
IMPORTANT_DE.DP-2.1: The organization shall conduct detection activities in accordance with applicable federal and regional laws, industry regulations and standards, policies, and other applicable requirements.
IMPORTANT_DE.DP-4.1: The organization shall communicate event detection information to predefined parties.
IMPORTANT_DE.DP-5.1: Improvements derived from the monitoring, measurement, assessment, testing, review, and lessons learned, shall be incorporated into detection process revisions.
DETECT
Develop and implement appropriate activities to identify the occurrence of a cybersecurity event.
RESPOND
BASIC_RS.RP-1.1: An incident response process, including roles, responsibilities, and authorities, shall be executed during or after an information/cybersecurity event on the organization's critical systems.
- Incident Response Team (IRT):
- Incident Manager: Leads and coordinates the response.
- Technical Response Team: Investigates, contains, and mitigates the incident.
- Legal & Compliance Officer: Ensures regulatory and legal compliance.
- Communication Coordinator: Handles internal and external communications.
- Business Continuity Officer: Ensures business processes continue with minimal disruption.
- Contact Information for Key Personnel: Maintain an up-to-date list of all assigned roles and their contact details.
- Define incident categories (e.g., ransomware, data breach, system failure).
- Implement monitoring tools to detect anomalies.
- Conduct employee training and awareness.
- Establish communication and escalation procedures.
- Identify anomalies using:
- Security Information and Event Management (SIEM)
- Intrusion Detection Systems (IDS)
- End-point Detection and Response (EDR)
- Classify incidents based on severity levels (Low, Medium, High, Critical).
- Document the incident details in the Incident Log.
- Short-term Containment:
- Isolate affected systems.
- Disable compromised user accounts.
- Block malicious IPs and URLs.
- Long-term Containment:
- Apply patches and security updates.
- Remove backdoors and malicious code.
- Strengthen access controls.
- Conduct forensic analysis to determine the root cause.
- Remove malware, compromised accounts, or vulnerabilities.
- Validate that all malicious artifacts are eradicated.
- Define Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).
- Restore systems using verified backups.
- Monitor for re-infection or further compromise.
- Ensure normal operations resume securely.
- Conduct incident post-mortem to analyze response effectiveness.
- Update response playbooks to prevent recurrence.
- Measure incident response effectiveness with metrics (e.g., mean time to detect (MTTD), mean time to respond (MTTR)).
- Maintain backup communication channels.
- Establish alternative processing facilities if needed.
- Ensure critical services remain operational even if primary systems are affected.
- Distribution & Approval:
- Ensure leadership and compliance teams approve and distribute the plan.
- Testing & Exercises:
- Conduct tabletop exercises and simulated attack scenarios (e.g., phishing, ransomware attack).
- Validate response effectiveness with penetration testing.
- Regular Updates:
- Review and update the plan annually or after major incidents.
- Ensure alignment with NIS2, GDPR, ISO 27001, and SOC 2 standards.
- Detection Metrics:
- Time taken to detect an incident (MTTD).
- Number of security incidents detected per month.
- Response Metrics:
- Mean time to respond (MTTR).
- Number of incidents fully resolved within SLA.
- Recovery Metrics:
- Percentage of incidents meeting RTO & RPO.
- Downtime duration of critical systems.
- Compliance Metrics:
- Percentage of incidents documented and reported.
- Number of compliance-related violations detected.
IMPORTANT_RS.CO-1.1: The organization shall ensure that personnel understand their roles, objectives, restoration priorities, task sequences (order of operations) and assignment responsibilities for event response.
IMPORTANT_RS.CO-2.1: The organization shall implement reporting on information/cybersecurity incidents on its critical systems in an organization-defined time frame to organization-defined personnel or roles.
IMPORTANT_RS.CO-3.2: The organization shall share information/cybersecurity incident information with relevant stakeholders as foreseen in the incident response plan.
IMPORTANT_RS.CO-5.1: The organization shall share information/cybersecurity event information voluntarily, as appropriate, with external stakeholders, industry security groups,… to achieve broader information/cybersecurity situational awareness.
IMPORTANT_RS.AN-1.1: The organization shall investigate information/cybersecurity-related notifications generated from detection systems.
- AdminDroid
- XDR
- Microsoft Defender for Endpoint
- Heimdal
IMPORTANT_RS.AN-2.1: Thorough investigation and result analysis shall be the base for understanding the full implication of the information/cybersecurity incident.
IMPORTANT_RS.AN-4.1: Information/cybersecurity incidents shall be categorized according to the level of severity and impact consistent with the evaluation criteria included the incident response plan.
IMPORTANT_RS.AN-5.1: The organization shall implement vulnerability management processes and procedures that include processing, analyzing and remedying vulnerabilities from internal and external sources.
- Endpoint vulnerabilities are detected via SentinelOne.
- Server and infrastructure vulnerabilities are detected via ManageEngine Vulnerability Manager Plus (VAS).
- High and critical vulnerabilities are prioritized based on CVSS score, exploitability, and asset criticality.
- Vulnerabilities are tracked and managed in Jira from detection to closure.
- Patch management is coordinated between the Security Team and Infrastructure Team.
- SentinelOne alerts reviewed daily for critical vulnerabilities.
- VAS vulnerability scans reviewed weekly.
- Veeam Backup & Replication
- Microsoft Azure Active Directory
- XDR
- Microsoft Authenticator
- Microsoft Defender for Endpoint
- Microsoft Defender for Cloud Apps
- Devolution RDM
- Microsoft Defender for Office 365 (MDO)
- Microsoft BitLocker
- Heimdal
- FileVault
BASIC_RS.IM-1.1: The organization shall conduct post-incident evaluations to analyse lessons learned from incident response and recovery, and consequently improve processes / procedures / technologies to enhance its cyber resilience.
IMPORTANT_RS.IM-1.2: Lessons learned from incident handling shall be translated into updated or new incident handling procedures that shall be tested, approved and trained.
IMPORTANT_RS.IM-2.1: The organization shall update the response and recovery plans to address changes in its context.
RESPOND
Develop and implement appropriate activities to take action regarding a detected cybersecurity incident.
RECOVER
BASIC_RC.RP-1.1: A recovery process for disasters and information/cybersecurity incidents shall be developed and executed as appropriate.
- Incident Response Team (IRT):
- Incident Manager: Leads and coordinates the response.
- Technical Response Team: Investigates, contains, and mitigates the incident.
- Legal & Compliance Officer: Ensures regulatory and legal compliance.
- Communication Coordinator: Handles internal and external communications.
- Business Continuity Officer: Ensures business processes continue with minimal disruption.
- Contact Information for Key Personnel: Maintain an up-to-date list of all assigned roles and their contact details.
- Define incident categories (e.g., ransomware, data breach, system failure).
- Implement monitoring tools to detect anomalies.
- Conduct employee training and awareness.
- Establish communication and escalation procedures.
- Identify anomalies using:
- Security Information and Event Management (SIEM)
- Intrusion Detection Systems (IDS)
- End-point Detection and Response (EDR)
- Classify incidents based on severity levels (Low, Medium, High, Critical).
- Document the incident details in the Incident Log.
- Short-term Containment:
- Isolate affected systems.
- Disable compromised user accounts.
- Block malicious IPs and URLs.
- Long-term Containment:
- Apply patches and security updates.
- Remove backdoors and malicious code.
- Strengthen access controls.
- Conduct forensic analysis to determine the root cause.
- Remove malware, compromised accounts, or vulnerabilities.
- Validate that all malicious artifacts are eradicated.
- Define Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).
- Restore systems using verified backups.
- Monitor for re-infection or further compromise.
- Ensure normal operations resume securely.
- Conduct incident post-mortem to analyze response effectiveness.
- Update response playbooks to prevent recurrence.
- Measure incident response effectiveness with metrics (e.g., mean time to detect (MTTD), mean time to respond (MTTR)).
- Maintain backup communication channels.
- Establish alternative processing facilities if needed.
- Ensure critical services remain operational even if primary systems are affected.
- Distribution & Approval:
- Ensure leadership and compliance teams approve and distribute the plan.
- Testing & Exercises:
- Conduct tabletop exercises and simulated attack scenarios (e.g., phishing, ransomware attack).
- Validate response effectiveness with penetration testing.
- Regular Updates:
- Review and update the plan annually or after major incidents.
- Ensure alignment with NIS2, GDPR, ISO 27001, and SOC 2 standards.
- Detection Metrics:
- Time taken to detect an incident (MTTD).
- Number of security incidents detected per month.
- Response Metrics:
- Mean time to respond (MTTR).
- Number of incidents fully resolved within SLA.
- Recovery Metrics:
- Percentage of incidents meeting RTO & RPO.
- Downtime duration of critical systems.
- Compliance Metrics:
- Percentage of incidents documented and reported.
- Number of compliance-related violations detected.
IMPORTANT_RC.IM-1.1: The organization shall incorporate lessons learned from incident recovery activities into updated or new system recovery procedures and, after testing, frame this with appropriate training.
RECOVER
Develop and implement appropriate activities to maintain plans for resilience and to restore capabilities impaired by cybersecurity incidents.
Trust Policies
Risicoprofiel
Afhankelijkheid van Derden
Hosting
Hersteltijddoelstelling
Risicoprofiel
Bepaalt de veerkracht van je systeem en het belang van je dienst voor klanten. Bevat hersteldoelen, datasensitiviteit en afhankelijkheid van derden.
Productbeveiliging
Multi-Factor Authenticatie
Audit Logging
Data Beveiliging
Integraties
Passkey Ondersteuning
Role-Based Access Control
Service-Level Agreement
SSO
Team Management
Productbeveiliging
Bevat technische en organisatorische maatregelen om je product te beveiligen, toegang te controleren en gebruikersrollen te beheren.
Rapporten
Vulnerability Assessment Report
Rapporten
Verwijst naar technische en compliance-documentatie die je kunt aanleveren om je beveiligingsniveau en infrastructuur aan te tonen.
Gegevensprivacy
Cookies
Gegevensprivacy
Deze categorie schetst hoe uw organisatie persoonlijke gegevens beheert en privacy-rechten respecteert. Deze praktijken tonen uw toewijding aan naleving van gegevensprivacy en ethische gegevensverwerking.
Bedrijfsbeveiliging (Corporate Security)
Personeelsbeëindiging/Overplaatsing
Bedrijfsbeveiliging (Corporate Security)
Deze categorie omvat beveiligingspraktijken op organisatieniveau, waaronder personeelsbeleid, training en incidentrespons. Deze maatregelen tonen aan hoe de menselijke en organisatorische aspecten van beveiliging worden beheerd om een algehele beveiligingscultuur te creëren.
Beleidsregels (Policies)
Bewustzijn- en Trainingbeleid (Awareness and Training Policy)
Beleidsregels (Policies)
Deze sectie bevat de formele beleidsregels die uw beveiligingspraktijken sturen en reguleren. Deze documenten demonstreren uw systematische aanpak van beveiligingsbeheer en vormen het fundament voor consistente en effectieve beveiligingsmaatregelen binnen uw organisatie.
Incidentrespons (Incident Response)
Incidentmeldingsproces (Incident Reporting Process)
Incidentrespons (Incident Response)
Deze categorie beschrijft hoe uw organisatie zich voorbereidt op, reageert op en herstelt van beveiligingsincidenten. Deze processen tonen uw vermogen aan om effectief om te gaan met beveiligingsgebeurtenissen en de impact ervan op klanten en bedrijfsactiviteiten te minimaliseren.
Training
Security Awareness Training
Training
Deze categorie beschrijft de beveiligingstraining en bewustwordingsprogramma's voor uw medewerkers. Deze initiatieven tonen aan hoe u een sterke beveiligingscultuur opbouwt en ervoor zorgt dat personeel over de kennis beschikt om veilig te handelen en beveiligingsrisico's te herkennen.
Fysieke & Omgevingsbeveiliging (Physical & Environment)
Bezoekerscontrole (Visitor Control)
Fysieke Toegangsbeveiliging (Physical Access Security)
Fysieke & Omgevingsbeveiliging (Physical & Environment)
Deze categorie omvat maatregelen voor de beveiliging van fysieke faciliteiten en omgevingen waar uw systemen zich bevinden. Deze controles tonen aan hoe u ongeautoriseerde fysieke toegang voorkomt en bescherming biedt tegen omgevingsrisico's zoals brand of stroomuitval.