Comparison Overview

PLAZZA AG

VS

OSMAB Holding AG

PLAZZA AG

Sieberstrasse 5, Zürich, 8055, CH
Last Update: 2025-11-26
Between 750 and 799

PLAZZA plant, realisiert, bewirtschaftet und vermarktet Liegenschaften und Immobilienprojekte in der Schweiz. PLAZZA bewirtschaftet gezielt ihr Bestandesportfolio an Wohn- und Geschäftsliegenschaften mit Schwerpunkt im Wirtschaftsraum Zürich. Hinzu kommen Entwicklungsliegenschaften und -projekte in den Wirtschaftszentren Zürich und Lausanne, die schrittweise einer künftigen Nutzung zugeführt werden sollen. Die geografisch und segmentspezifisch klare Ausrichtung des Portfolios auf zentrumsnahe, gut erschlossene Liegenschaften trägt zur nachhaltigen Stabilität von PLAZZA bei und wird auch in Zukunft Erfolg versprechend sein. Die PLAZZA AG (Ticker: PLAN) ist seit Juni 2015 an der SIX Swiss Exchange kotiert und hat ihren Sitz in Zürich.

NAICS: 53
NAICS Definition: Real Estate and Rental and Leasing
Employees: 21
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

OSMAB Holding AG

Leibnizpark 4, Rösrath, 51503, DE
Last Update: 2025-11-27
Between 750 and 799

Die OSMAB Holding AG ist ein auf Immobilien spezialisiertes Unternehmen. Seit 1992 agiert die Unternehmensgruppe als Investor, Projektentwickler und Bestandshalter. Dabei werden schwerpunktmäßig Büroimmobilien und Logistikimmobilien entwickelt. Weitere Geschäftsfelder sind die Entwicklung von Baulandflächen und das Asset Management des eigenen Immobilienportfolios. Neben dem Hauptgeschäft investiert OSMAB seit über zehn jahren in erneuerbare Energien.

NAICS: 53
NAICS Definition: Real Estate and Rental and Leasing
Employees: 37
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/plazza-ag.jpeg
PLAZZA AG
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/osmab-holding-ag.jpeg
OSMAB Holding AG
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
PLAZZA AG
100%
Compliance Rate
0/4 Standards Verified
OSMAB Holding AG
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Real Estate and Equipment Rental Services Industry Average (This Year)

No incidents recorded for PLAZZA AG in 2025.

Incidents vs Real Estate and Equipment Rental Services Industry Average (This Year)

No incidents recorded for OSMAB Holding AG in 2025.

Incident History — PLAZZA AG (X = Date, Y = Severity)

PLAZZA AG cyber incidents detection timeline including parent company and subsidiaries

Incident History — OSMAB Holding AG (X = Date, Y = Severity)

OSMAB Holding AG cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/plazza-ag.jpeg
PLAZZA AG
Incidents

No Incident

https://images.rankiteo.com/companyimages/osmab-holding-ag.jpeg
OSMAB Holding AG
Incidents

No Incident

FAQ

PLAZZA AG company demonstrates a stronger AI Cybersecurity Score compared to OSMAB Holding AG company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, OSMAB Holding AG company has disclosed a higher number of cyber incidents compared to PLAZZA AG company.

In the current year, OSMAB Holding AG company and PLAZZA AG company have not reported any cyber incidents.

Neither OSMAB Holding AG company nor PLAZZA AG company has reported experiencing a ransomware attack publicly.

Neither OSMAB Holding AG company nor PLAZZA AG company has reported experiencing a data breach publicly.

Neither OSMAB Holding AG company nor PLAZZA AG company has reported experiencing targeted cyberattacks publicly.

Neither PLAZZA AG company nor OSMAB Holding AG company has reported experiencing or disclosing vulnerabilities publicly.

Neither PLAZZA AG nor OSMAB Holding AG holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PLAZZA AG company nor OSMAB Holding AG company has publicly disclosed detailed information about the number of their subsidiaries.

OSMAB Holding AG company employs more people globally than PLAZZA AG company, reflecting its scale as a Real Estate and Equipment Rental Services.

Neither PLAZZA AG nor OSMAB Holding AG holds SOC 2 Type 1 certification.

Neither PLAZZA AG nor OSMAB Holding AG holds SOC 2 Type 2 certification.

Neither PLAZZA AG nor OSMAB Holding AG holds ISO 27001 certification.

Neither PLAZZA AG nor OSMAB Holding AG holds PCI DSS certification.

Neither PLAZZA AG nor OSMAB Holding AG holds HIPAA certification.

Neither PLAZZA AG nor OSMAB Holding AG holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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