Back to Blog

    Security

    Developers are a massive security risk: how to mitigate it

    Developer machines hold source code, keys and cloud sessions, and they run third-party code all day. We show how Windows 365, Intune and Dev Drive limit the damage, and checked every building block for availability in Switzerland.

    October 30, 202611 min read
    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    marcel.haas@cnext.ch
    In this article

    In June the penetration tester @techspence described on X why a developer machine is now one of the most rewarding targets in a company: it holds source code, API keys and signed-in cloud sessions, and package managers, IDE extensions, AI coding agents and MCP servers run third-party code on it all day. Since then Microsoft has moved the tools that contain this risk: Microsoft Dev Box is being retired, Windows 365 has a ready-made developer image, and Endpoint Privilege Management has been part of Microsoft 365 E5 since July 2026. We checked every building block for availability in Switzerland and say when a managed developer workstation pays off.

    What appeared on X in June

    The piece is called "The Developer Endpoint Security Problem" and is sponsored by Safety, a vendor of endpoint security. The analysis holds up regardless. A typical developer machine has local admin rights, keys and tokens on disk, access to cloud and build pipelines, plus Docker and WSL, into which an antivirus product sees only partly. As recent examples of attacks through the software supply chain, the author names Axios, LiteLLM, Shai-Hulud and Trivy/Checkmarx.

    His view of existing tools is sober. EDR detects suspicious behaviour at runtime, but not a package nobody has reported as malicious yet. Device management enforces encryption and updates, but does not know which npm packages, IDE extensions or MCP servers run on a machine. His answer has three parts: know what is installed and running; assume a developer machine will be compromised and limit the damage; monitor what happens anyway. His yardstick is simple: a single laptop must not compromise the whole company.

    A Tuesday at a software company in Bern

    A software company in Bern is building a customer portal for a health insurer with fourteen people. Two of them are external developers, one works on his own MacBook. On Tuesday morning he updates the frontend dependencies. A new version of a small helper package runs a script during installation. The script finds what sits on this machine: the token for the private package feed in the .npmrc file, the signed-in Azure CLI, a GitHub token with write access to the repository and, in the browser, an open session in the Azure portal. Next to it sit private mail, photos and online banking. The company does not know this device; it can neither check nor wipe it.

    The same Tuesday looks different when the developer works in a Windows 365 Cloud PC in Switzerland North. He opens the Windows App on his MacBook and signs in with Entra ID and a second factor. Code, package caches and tokens live only in the Cloud PC; clipboard, drives and USB are blocked towards the MacBook. The malicious script still runs, but it sees only this one workstation. There the developer works without admin rights, and his token for the package feed can only read. IT revokes the affected tokens, rebuilds the Cloud PC from policy, and in the afternoon he carries on.

    Where Microsoft 365 closes the gaps

    Local admin rights. Endpoint Privilege Management in Intune lets developers work as standard users. Whatever needs admin rights, such as an SDK installer or a driver, runs through rules: automatically for approved files, after confirmation with a justification, after approval by support, or not at all. Rules match on file hash, publisher certificate and arguments, and child processes can be controlled too. Elevated processes mostly run under a virtual account, separate from the user profile, and Intune logs every elevation.

    Keys and sessions on the laptop. A Cloud PC separates the development environment from the device that displays it. Microsoft switches off redirection of clipboard, drives, USB and printers for Cloud PCs by default; whatever is needed, IT allows through the Intune settings catalog. Conditional Access applies to the portal, the gateway and the sign-in to the Cloud PC, and can require a new sign-in at fixed intervals. For private devices that enforce no sign-in themselves, that is the most important switch.

    Tools nobody manages. Since the week of 21 September 2026 the Developer Configuration image has been generally available for Windows 365 Enterprise and Flex in dedicated mode, with Visual Studio Code, Git, GitHub CLI, WSL and the Microsoft 365 Apps. IT adds its own SDKs and tools through Intune. For physical machines, Microsoft made Windows Developer Configurations generally available at Build in June, a WinGet configuration that sets up a fresh machine reproducibly. That fixes what a developer workstation starts with, and deviations stand out.

    Fast rebuild. Reprovision deletes a Cloud PC and rebuilds it from the current provisioning policy. Data, apps and customisations are lost in the process, so code belongs in the repository and not only on the Cloud PC. Whoever wants a known good state back restores the Cloud PC to a restore point.

    Physical developer machines. Where builds run locally, Dev Drive helps. On this ReFS volume for repositories, package caches and build output, Microsoft Defender scans in performance mode, asynchronously, while real-time protection stays on for all other volumes. Microsoft explicitly describes this as a secure alternative to folder exclusions in the antivirus, which teams otherwise like to set when builds are slow. According to Microsoft, tools and SDKs belong on C:, and whether filters may be detached from a Dev Drive is decided by IT through policy.

    Testing against Microsoft 365. Whoever builds Teams apps, add-ins or Graph integrations tests in a Microsoft 365 Developer Program sandbox, separate from the production tenant. The sandbox comes with 25 licences, 24 test users and sample data. Eligible are subscribers to Visual Studio Professional or Enterprise, partners in the ISV Success Program or the Microsoft AI Cloud Partner Program, and customers with Premier or Unified Support.

    What a Cloud PC does not solve

    A malicious package runs in a Cloud PC just as it does on a laptop. What changes is its reach: no private sessions, no access to the end device, a workstation that IT rebuilds from policy. For that to hold, three more things are needed. Tokens get only the rights a task needs and expire soon; pipelines sign in through Entra ID with workload identities, without stored keys. Microsoft Defender for Endpoint runs in the Cloud PC as well and reports what a script does there. And the team knows which packages, extensions and MCP servers it uses, with pinned versions and a review for new dependencies.

    Microsoft Dev Box is being retired

    Until recently Microsoft Dev Box was the obvious answer for managed developer workstations in Azure. Microsoft has set its retirement: the closing-down period has been running since 14 September 2026, the service ends on 18 September 2028, and remaining workstations will be deleted. Existing deployments stay supported until then. Microsoft names Windows 365 as the way forward, but states itself that it is not a one-to-one replacement and that there is no automated migration tool. We therefore build new developer workstations on Windows 365. Whoever runs Dev Box today plans the move with one pilot per kind of team.

    Availability in Switzerland

    As of 30 October 2026, checked against the Microsoft Learn pages and announcements in the sources.

    Building blockStatus according to MicrosoftIn Switzerland
    Windows 365 Enterprise Cloud PCGenerally availableYes, region group Switzerland with Switzerland North
    Developer Configuration image with Microsoft 365 AppsGenerally available since the week of 21 September 2026, for Enterprise and Flex in dedicated modeGallery image; Microsoft names no regional restriction
    Cloud PCs with 32 vCPUs and with GPUAvailableCapacity in Switzerland North not checked, we clarify it per tenant
    Endpoint Privilege ManagementGenerally available; included in Microsoft 365 E5 since July 2026, otherwise an add-on at USD 3.00 per user per month (list price)Yes; Intune stores customer data in the Switzerland geography when the Entra directory lists Switzerland as its country
    Microsoft Defender for Endpoint, including performance mode on Dev DriveGenerally availableData storage in Switzerland possible; pseudonymised data may sit in central systems in the US
    Conditional Access for Cloud PCsGenerally available with Entra ID P1Applies tenant-wide, regardless of the Cloud PC region
    Dev DriveWindows 11 feature from build 22621.2338Local on the device, no cloud region
    Windows Developer ConfigurationsGenerally available since June 2026Local on the device
    Microsoft 365 Developer Program sandboxFor eligible members, up to 90 days, development and testing onlyCountry selectable at setup; not covered by the EU Data Boundary
    Microsoft Execution Containers for AI coding agentsEarly previewNot for production work
    Microsoft Dev BoxClosing-down period since 14 September 2026, ends on 18 September 2028Not for new workstations

    Windows 365 Enterprise requires Windows E3, Intune and Entra ID P1 per user, as included in Microsoft 365 E3 and E5, plus the Windows 365 licence in the right size. We calculate Cloud PC prices per tenant, because size, agreement and currency determine them.

    When it pays off

    External developers or work from personal devices. This is where the Cloud PC pays off most clearly. The company manages the workstation, not the device, and when the engagement ends, the workstation ends too. The software company in Bern is the typical case.

    Code or test data with personal data, professional secrets or bank client data. Then the team works in a Cloud PC in Switzerland North, with Intune and Defender in Swiss data storage and redirections closed. Whether that is sufficient for your data class is recorded by your data protection officer.

    Heavy local builds, hardware on the USB port or mobile emulators. Then the physical machine stays, but managed: Intune, Endpoint Privilege Management, Dev Drive with Defender in performance mode and a Developer Configuration as the starting state. A Cloud PC rarely pays off here.

    A small team on company laptops. Five developers on managed devices do not need a Cloud PC. Standard users with Endpoint Privilege Management, Conditional Access with compliant devices and short-lived tokens close the biggest gaps. With Microsoft 365 E5, Endpoint Privilege Management is already licensed.

    How we set up devices, Cloud PCs and policies and look after them on an ongoing basis is described on our Managed Workplace page.

    Limits

    None of these building blocks delivers a complete inventory of developer tools as the article demands. Which npm packages, IDE extensions and MCP servers a team uses remains a matter of repository, pipeline and approval process. Microsoft Execution Containers, meant to restrict AI coding agents to approved access, are an early preview; WSL containers with admin policies were announced in June for a preview. We have not checked the capacity of large and GPU Cloud PCs in Switzerland North. The Developer Program sandbox is short-lived by design and does not belong anywhere near production data. And Microsoft Defender for Endpoint also stores pseudonymised data in the US, which belongs in the data protection assessment.

    Next step

    What does a developer workstation look like at your company today, and who has local admin rights? Send us the number of your developers, internal and external, and the data class they work with. You get our recommendation per group: Cloud PC in Switzerland North or managed laptop, with licence needs and the state of availability in Switzerland. I look forward to the conversation.

    Marcel Haas, CEO CNEXT

    Sources: @techspence, "The Developer Endpoint Security Problem", X, 23 June 2026, sponsored by Safety. Pavan Davuluri, "Build 2026: Furthering Windows as the trusted platform for development", Windows Developer Blog, 2 June 2026. Microsoft Learn, Microsoft Dev Box retirement guide, as of 8 September 2026; Windows 365 requirements, as of 15 October 2026; What's new in Windows 365, updated 30 October 2026; Manage device RDP redirections for Cloud PCs, as of 5 August 2025; Set Conditional Access policies for Windows 365, as of 12 May 2026; Reprovision a Cloud PC, as of 15 May 2026; Endpoint Privilege Management, as of 23 June 2026; Intune data storage and processing, as of 5 May 2026; Microsoft Defender for Endpoint data storage and privacy; Set up a Dev Drive on Windows 11, updated 1 June 2026; Microsoft 365 Developer Program FAQ, as of 4 September 2026. Microsoft, Microsoft Intune plans and pricing. All facts checked on 30 October 2026.

    SecuritySchweiz
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    6x Microsoft Applied Skills

    Classify developer workstations

    We map your developer groups to a Cloud PC or a managed laptop and record what of it runs in Switzerland today.