Security & Compliance

    Security incidents: reported, assessed and resolved together.

    Our alerting service follows security advisories from Microsoft, BACS and CISA and the incidents in your tenant. An agent matches them to your environment, we get in touch with measures and coordinate the fix with you.

    For management and IT who want to hear about an exploited vulnerability in time and know who does what during an incident.

    • Microsoft Defender XDR
    • Security Update Guide
    • CISA KEV
    • BACS
    • Maester
    • AI agent
    A mountain rescuer and an IT specialist in Zermatt below the Matterhorn work through the steps of a security incident on a laptop, a warning on the phone on the table
    01

    Tuesday evening, a vulnerability in SharePoint Server

    On Tuesday evening Microsoft publishes a security update for SharePoint Server; the vulnerability is already being exploited. Our agent reads the advisory, matches it against your inventory, which lists a SharePoint Server 2019, and proposes the level critical. A person at CNEXT confirms the rating and sends you the initial alert: what is affected, what to do right away, who at CNEXT is reachable. On Wednesday morning a short call settles the maintenance window, your IT installs the update, we check the logs for traces. On Thursday you receive the closing report with timeline, measures and what we change for next time.

    02

    Watch, assess, alert, coordinate

    Many organisations learn of a vulnerability when someone happens to read about it. We turn that into a service with fixed routines: sources watched continuously, an inventory of your systems that every advisory is checked against, a rating a person confirms, and a chain of alerts that accompanies you through the incident. How fast we get in touch and whom we reach is set out in the alert plan we agree with you.

    • SourcesMicrosoft's Security Update Guide and Message Center, the CISA catalog of known exploited vulnerabilities, the advisories of the Swiss Federal Office for Cyber Security BACS, vendor notices for your business applications, plus the incidents from Microsoft Defender XDR and the deviations from your tenant's Maester runs.Result: an advisory reaches us as soon as it is published, from every source in the same form.
    • InventoryWhich servers, versions, services and Microsoft 365 features you run, maintained from Intune, Entra ID and the Active Directory and Entra Connect analyses.Result: an advisory becomes an alert only when it concerns you.
    • Rating by the agentThe agent reads every advisory, checks exposure, exploitation and available countermeasures and proposes a level. Critical cases go straight to a person at CNEXT who reviews the proposal; the rest goes into the weekly overview.Result: your IT receives few alerts, and every one of them counts.
    • Initial alertOne page with the incident, your exposure, the immediate measures, the contact at CNEXT and the next planned update, by email and phone to the people in your alert plan, outside your office hours too by agreement.Result: within the agreed time you know what is going on and what to do.
    • Coordinating the fixWe keep the list of measures with owners, deadlines and status, settle the order with your IT and your suppliers, check logs for traces of exploitation and send status reports at agreed intervals.Result: everyone involved works from the same list, and nobody waits for information.
    • Reporting duties and closureNotes on whether a case may fall under the reporting duty to BACS or to the FDPIC, with deadlines and templates for the report; after the incident a closing report with timeline, cause, measures and lessons, and the changes to inventory and alert plan.Result: an incident ends with a document that management, auditors and insurers can read.
    03

    What we need for the alerting

    An alert plan: who at your organisation receives alerts, in which order, through which channels and at which times, with deputies. An inventory of your systems, which we build with you if none exists. Read access to Defender XDR and your tenant's Maester reports if we are to include incidents from the tenant. And a decision on who at your organisation approves measures when things have to move fast.

    04

    What you hold at the end

    One-off, as incident readiness: an alert plan with contact chain, an inventory of your systems, the templates for initial alert, status report and closing report and an exercise with an invented incident, after which your team knows what to do. Monthly, as the alerting service: continuous watching of the sources against your inventory, initial alerts and coordination during an incident, a weekly overview of the advisories that do not concern you and a monthly report with every case and decision.

    What you receive from us

    The documents we work with.

    Three communications accompany an incident: the initial alert within the agreed time, status reports until the measures are implemented, and the closing report. Shown here as an invented case at a fictional Muster AG.

    Initial alert

    Sample

    Initial security incident alert

    Customer
    Muster AG, Bern (fictional)
    Incident
    INC-2026-041, vulnerability in SharePoint Server, actively exploited
    Reported on
    Tuesday, 14 April 2026, 21:40
    Level
    Critical, confirmed by CNEXT
    • 1system affected
    • 3immediate measures
    • 08:00next update
    • 2people reached

    Summary

    Microsoft has published a security update for SharePoint Server 2016, 2019 and Subscription Edition today. The vulnerability is already being exploited on the internet; it needs neither sign-in nor user interaction. Your inventory lists SRV-SP01 with SharePoint Server 2019 and access from the internet through the partner portal. We rate the case as critical.

    No.MeasureWhoBy
    1Block the partner portal on SRV-SP01 at the reverse proxy until the update is installedMuster AG ITtoday 22:30
    2Install the security update KB for SharePoint Server 2019 in the maintenance window, run the configuration wizardMuster AG IT with CNEXTWed 15 April, 07:00
    3Check IIS and ULS logs since 1 April for the known request patternsCNEXTWed 15 April, 10:00

    Contact and next update

    • Your contact at CNEXT is reachable this evening and tomorrow from 07:00 at the number in the alert plan.
    • Next status report: Wednesday, 15 April 2026, 08:00, by email to the contact chain.
    • Source: Microsoft Security Update Guide, entry of 14 April 2026; CISA has added the vulnerability to its catalog of known exploited vulnerabilities.

    Next steps

    Please confirm receipt by replying to this email or by phone. You implement measure 1 this evening; we accompany measures 2 and 3 tomorrow morning.

    Samples with invented details for a fictional Muster AG.

    Sound familiar? Tell us where you stand today.

    Contact

    Legal position and what's new.

    As of: 30 October 2026

    • Since 1 April 2025

      Cyberattacks on critical infrastructures must be reported within 24 hours.

      Operators of critical infrastructures report cyberattacks to the Swiss Federal Office for Cyber Security BACS within 24 hours of discovery and complete the report within 14 days. Since 1 October 2025 the sanctions of the Information Security Act apply. Whether your organisation falls under the duty is set out in the act and the Cyber Security Ordinance.

      Source: BACS: Information on the reporting obligation
    • Since 1 September 2023

      Data security breaches go to the FDPIC as soon as possible.

      Under article 24 of the Data Protection Act the controller notifies the FDPIC as soon as possible of a data security breach that is likely to result in a high risk for the data subjects, stating its nature, consequences and measures. The processor notifies the controller. The FDPIC accepts reports through its portal.

      Source: FDPIC: Reporting a data security breach
    • As of 2 July 2026

      Defender XDR sends incident emails, filtered by severity and source.

      The Defender portal correlates related alerts into incidents. Email notifications can be set up by severity, source and device group and name the incident's title, severity and categories. Setting them up needs the permission to manage security settings.

      Source: Microsoft Learn: Get incident notifications by email

    One-off or monthly.

    Prepare once so your team knows what to do when it matters, or the alerting service runs at CNEXT, every day.

    • One-off

      Incident readiness as a project

      Alert plan with contact chain, inventory of your systems, templates for initial alert, status report and closing report and an exercise with an invented incident. Afterwards your team runs the plan itself.

      Incident readiness as a project
    • Monthly

      Alerting service with coordination

      Continuous watching of the sources against your inventory, initial alerts and coordination of the fix during an incident, weekly overview, monthly report and maintenance of inventory and alert plan. Cancellable after the agreed notice period.

      Alerting service with coordination

    Sample documents.

    The three communications of an incident, filled with an invented case at a fictional Muster AG.

    Samples with invented details. In a real incident the documents carry your systems, your contacts and the times from your alert plan.

    What management asks.

    What does the agent do, and what does a person do?

    The agent reads the sources around the clock, matches every advisory against your inventory, summarises it and proposes a level. A person at CNEXT reviews every critical proposal, decides on the rating, finishes the initial alert and makes the call. No alert leaves us without that review, and no measure runs without your approval.

    How fast do you get in touch?

    As fast as the alert plan says, by level and time of day. Which times we commit to depends on whether you book the service for office hours or beyond; that is set out in the proposal. The initial alert always goes out first, even while the measures are still open.

    Do you fix the incident yourselves?

    We coordinate and verify; who does the hands-on work we agree with you. For systems we look after in a monthly service, such as Entra Connect or Intune, we implement the measure ourselves. For all others we keep the list, settle the order with your IT and your suppliers and check the logs. What Support & Operations takes on is set out in your support contract.

    How do you know which systems we have?

    From the inventory we build with you at the start and maintain continuously: from Intune, Entra ID, the Active Directory and Entra Connect analyses and from your details on business applications and suppliers. The inventory is your document; you report every change to your environment to us, or we see it in the next reconciliation.

    Do you handle the report to the authorities?

    We point out when a case may fall under the reporting duty for critical infrastructures to BACS or under the reporting duty of the Data Protection Act to the FDPIC, name the deadlines and provide the templates. You file the report itself; we supply the timeline and the facts for it. The legal assessment stays with your legal counsel.

    What is in the monthly report when nothing happened?

    The advisories we checked against your inventory and rated as not affecting you, with date and reason, the updates you installed, and the changes to inventory and alert plan. That way management and auditors see that the service is running, in a quiet month too.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.