---
type: concept
title: Proprietary Software Risks
tags: [security, privacy, it-risk]
related: [vendor-lock-in, migration-to-open-source, gdpr-compliance]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_support_dokumentation_it_informationssicherheit_opensource.md"]
---

# Proprietary Software Risks

**Proprietary Software Risks** encompass the security, privacy, and operational vulnerabilities associated with using closed-source software where the vendor controls the source code and the terms of service.

## Security Vulnerabilities
Closed-source systems are viewed by the URZ as potentially more susceptible to catastrophic failures because the community cannot independently audit the code for vulnerabilities.
- **Case Study:** The 2019 cyberattack on **Justus-Liebig-Universität Gießen** is cited as an example where a massive attack forced the total shutdown of the Microsoft-based IT infrastructure.

## Privacy and Telemetry
Proprietary software often includes built-in data collection mechanisms that may conflict with strict privacy regulations.
- **Windows 10 Telemetry:** The URZ notes significant concerns from state data protection officers regarding the automatic transmission of telemetry data from Windows 10 to Microsoft, questioning its legality and suitability for use in the public sector.

## Operational Risks
- **Financial Volatility:** Sudden changes in licensing terms (as seen with CERN) can lead to unsustainable cost increases.
- **Dependency:** Reliance on a single vendor's update cycle and support roadmap.
