Comparison Overview

Martin-Luther-Universität Halle-Wittenberg

VS

PFH Private Hochschule Göttingen

Martin-Luther-Universität Halle-Wittenberg

Universitätzsplatz 10, Halle, Sachsen-Anhalt, 06108, DE
Last Update: 2025-12-13
Between 750 and 799

Forschung und Lehre mit über 500 Jahren Tradition: Die Martin-Luther-Universität Halle-Wittenberg (MLU) bietet ein breites Fächerspektrum in den Geistes-, Sozial-, Natur- und den medizinischen Wissenschaften an. Die größte und älteste Hochschule Sachsen-Anhalts entstand 1817 aus dem Zusammenschluss der 1502 gegründeten Universität Wittenberg und der 1694 gegründeten Friedrichs-Universität Halle. Heute hat sie rund 20.000 Studierende und 340 Professoren. Das wissenschaftliche Profil der MLU ist geprägt durch die geisteswissenschaftlichen Schwerpunkte „Aufklärung-Religion-Wissen“ und „Gesellschaft und Kultur in Bewegung. Diffusion - Experiment - Institution“ sowie durch die naturwissenschaftlichen Schwerpunkte „Materialwissenschaften – Nanostrukturierte Materialien“ und „Biowissenschaften – Makromolekulare Strukturen und biologische Informationsverarbeitung“. Eine besondere Rolle spielen außerdem die Agrarwissenschaften, für deren Profilierung in Sachsen-Anhalt die Universität Halle die alleinige Verantwortung trägt. Im Bereich der Medizin liegen die Schwerpunkte in der Epidemiologie, der Pflegeforschung und der Erforschung der Signalübertragung. Hier forschen und lehren neben Ärzten gleichberechtigt Pflegewissenschaftler. Das Dorothea Erxleben Lernzentrum ist eine der größten Lernkliniken für angehende Mediziner. Außerhalb ihrer Schwerpunkte versammelt die Universität eine Vielzahl kleiner Fächer, von denen einige deutschlandweit einzigartig sind. Eng kooperiert die MLU als Mitglied des Mitteldeutschen Universitätsbundes Halle-Jena-Leipzig mit anderen Hochschulen sowie mit außeruniversitären Einrichtungen und der Wirtschaft. Örtlich sichtbar wird das auf dem Weinberg-Campus, dem zweitgrößten Technologiepark im Osten Deutschlands. Dort hat die Universität ihre naturwissenschaftlichen Institute konzentriert und arbeitet mit ansässigen Unternehmen und Partnern der großen deutschen Forschungseinrichtungen, wie der Max-Planck- und der Fraunhofer-Gesellschaft.

NAICS: None
NAICS Definition:
Employees: 2,116
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

PFH Private Hochschule Göttingen

Weender Landstraße 3-7, Göttingen, undefined, 37073, DE
Last Update: 2025-12-13
Between 800 and 849

Die staatlich anerkannte PFH ist eine private Hochschule, die das unternehmerische Denken in den Mittelpunkt stellt. Sie bietet derzeit 55 Campus- und Fernstudiengänge in Management, Technologie, Healthcare Technology, Business Law, Wirtschaftsinformatik sowie Psychologie und Wirtschaftspsychologie an. Campusorte sind Göttingen und der Hansecampus, darüber hinaus gibt es 24 Fernstudienzentren in Deutschland, Österreich und auf Mallorca. Die PFH wurde 1995 in Göttingen gegründet. Sie hat sich der Ausbildung von qualifiziertem Führungskräftenachwuchs in den Bereichen Management und Technologie verschrieben, um einen Beitrag zur Wettbewerbssicherung Deutschlands als Wissenschafts- und Wirtschaftsstandort zu leisten. Diesem Anspruch wird die Hochschule durch konsequente Praxisorientierung und Entwicklung innovativer Lehrangebote gerecht. Impressum/Imprint: https://www.pfh.de/ueber-uns/impressum.html

NAICS: None
NAICS Definition: Others
Employees: 244
Subsidiaries: 53
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/martin-luther-university-halle-wittenberg.jpeg
Martin-Luther-Universität Halle-Wittenberg
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/private-fachhochschule-g-ttingen.jpeg
PFH Private Hochschule Göttingen
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Martin-Luther-Universität Halle-Wittenberg
100%
Compliance Rate
0/4 Standards Verified
PFH Private Hochschule Göttingen
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hochschulen und Universitäten Industry Average (This Year)

No incidents recorded for Martin-Luther-Universität Halle-Wittenberg in 2025.

Incidents vs Hochschulen und Universitäten Industry Average (This Year)

No incidents recorded for PFH Private Hochschule Göttingen in 2025.

Incident History — Martin-Luther-Universität Halle-Wittenberg (X = Date, Y = Severity)

Martin-Luther-Universität Halle-Wittenberg cyber incidents detection timeline including parent company and subsidiaries

Incident History — PFH Private Hochschule Göttingen (X = Date, Y = Severity)

PFH Private Hochschule Göttingen cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/martin-luther-university-halle-wittenberg.jpeg
Martin-Luther-Universität Halle-Wittenberg
Incidents

No Incident

https://images.rankiteo.com/companyimages/private-fachhochschule-g-ttingen.jpeg
PFH Private Hochschule Göttingen
Incidents

No Incident

FAQ

PFH Private Hochschule Göttingen company demonstrates a stronger AI Cybersecurity Score compared to Martin-Luther-Universität Halle-Wittenberg company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, PFH Private Hochschule Göttingen company has disclosed a higher number of cyber incidents compared to Martin-Luther-Universität Halle-Wittenberg company.

In the current year, PFH Private Hochschule Göttingen company and Martin-Luther-Universität Halle-Wittenberg company have not reported any cyber incidents.

Neither PFH Private Hochschule Göttingen company nor Martin-Luther-Universität Halle-Wittenberg company has reported experiencing a ransomware attack publicly.

Neither PFH Private Hochschule Göttingen company nor Martin-Luther-Universität Halle-Wittenberg company has reported experiencing a data breach publicly.

Neither PFH Private Hochschule Göttingen company nor Martin-Luther-Universität Halle-Wittenberg company has reported experiencing targeted cyberattacks publicly.

Neither Martin-Luther-Universität Halle-Wittenberg company nor PFH Private Hochschule Göttingen company has reported experiencing or disclosing vulnerabilities publicly.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds any compliance certifications.

Neither company holds any compliance certifications.

PFH Private Hochschule Göttingen company has more subsidiaries worldwide compared to Martin-Luther-Universität Halle-Wittenberg company.

Martin-Luther-Universität Halle-Wittenberg company employs more people globally than PFH Private Hochschule Göttingen company, reflecting its scale as a Hochschulen und Universitäten.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds SOC 2 Type 1 certification.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds SOC 2 Type 2 certification.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds ISO 27001 certification.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds PCI DSS certification.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds HIPAA certification.

Neither Martin-Luther-Universität Halle-Wittenberg nor PFH Private Hochschule Göttingen holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

Risk Information
cvss3
Base: 8.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Risk Information
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L