Comparison Overview

Berlin School of Creative Leadership

VS

Hochschule für Life Sciences FHNW

Berlin School of Creative Leadership

Rudower Chaussee 28, Berlin, BE, 12489, DE
Last Update: 2025-12-15
Between 750 and 799

Berlin School of Creative Leadership at Steinbeis University Berlin is a leading institute for quality executive education and research on creative leadership. Since opening its doors in 2006, the school has built a global community of senior professionals from across the full spectrum of business and industry– wherever creativity and innovation set the standard– in over 60 countries around the world. At the heart of the Berlin School is its Executive MBA in Creative Leadership, a part-time degree, taught both online and in-person in a flexible and modular format, including residencies in Berlin, New York, San Francisco, Shanghai and Tokyo. A degree from the Berlin School teaches leaders to cultivate new and different ways of seeing, interpreting and acting in an ever-evolving, digitally networked society. In the understanding that creative business leadership is a way of thinking, a methodology and a repertoire of skills all at once, participants are taught in a rigorous and an unfolding process to become continually creative learners – and un-learners of old habits. Simultaneously, they become deeply versed in the techniques and mindset necessary to catalyze business activity across multiple situations, amidst often competing objectives, demands and contexts. In addition to the Executive MBA, the Berlin School offers various open and custom programs providing executives with essential skills, tools and insights to lead their organizations more effectively and more creatively.

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

Hochschule für Life Sciences FHNW

Hofackerstrasse 30, Muttenz, Basel-Landschaft, 4132, CH
Last Update: 2025-12-13

Die Hochschule für Life Sciences FHNW mit Sitz in Muttenz gehört zur Fachhochschule Nordwestschweiz (FHNW). Sie ist Teil des grössten Life Sciences-Standorts Europas. In diesem Zentrum von Pharma- und Medizintechnik, der chemischen Industrie sowie Umwelt- und Biotechnologie werden kompetente Fachkräfte ausgebildet und Lösungen für die gesellschaftlichen und wirtschaftlichen Anforderungen von morgen erarbeitet. Wir setzen uns ein für neue präventive und therapeutische Produkte und Dienstleistungen, eine verbesserte Lebensqualität und einen nachhaltigen Umgang mit der Umwelt.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/berlin-school-of-creative-leadership.jpeg
Berlin School of Creative Leadership
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/lifesciences_fhnw.jpeg
Hochschule für Life Sciences FHNW
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
Berlin School of Creative Leadership
100%
Compliance Rate
0/4 Standards Verified
Hochschule für Life Sciences FHNW
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 Berlin School of Creative Leadership in 2025.

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

No incidents recorded for Hochschule für Life Sciences FHNW in 2025.

Incident History — Berlin School of Creative Leadership (X = Date, Y = Severity)

Berlin School of Creative Leadership cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hochschule für Life Sciences FHNW (X = Date, Y = Severity)

Hochschule für Life Sciences FHNW cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/berlin-school-of-creative-leadership.jpeg
Berlin School of Creative Leadership
Incidents

No Incident

https://images.rankiteo.com/companyimages/lifesciences_fhnw.jpeg
Hochschule für Life Sciences FHNW
Incidents

No Incident

FAQ

Berlin School of Creative Leadership company demonstrates a stronger AI Cybersecurity Score compared to Hochschule für Life Sciences FHNW company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Hochschule für Life Sciences FHNW company has disclosed a higher number of cyber incidents compared to Berlin School of Creative Leadership company.

In the current year, Hochschule für Life Sciences FHNW company and Berlin School of Creative Leadership company have not reported any cyber incidents.

Neither Hochschule für Life Sciences FHNW company nor Berlin School of Creative Leadership company has reported experiencing a ransomware attack publicly.

Neither Hochschule für Life Sciences FHNW company nor Berlin School of Creative Leadership company has reported experiencing a data breach publicly.

Neither Hochschule für Life Sciences FHNW company nor Berlin School of Creative Leadership company has reported experiencing targeted cyberattacks publicly.

Neither Berlin School of Creative Leadership company nor Hochschule für Life Sciences FHNW company has reported experiencing or disclosing vulnerabilities publicly.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW holds any compliance certifications.

Neither company holds any compliance certifications.

Hochschule für Life Sciences FHNW company has more subsidiaries worldwide compared to Berlin School of Creative Leadership company.

Berlin School of Creative Leadership company employs more people globally than Hochschule für Life Sciences FHNW company, reflecting its scale as a Hochschulen und Universitäten.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW holds SOC 2 Type 1 certification.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW holds SOC 2 Type 2 certification.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW holds ISO 27001 certification.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW holds PCI DSS certification.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW holds HIPAA certification.

Neither Berlin School of Creative Leadership nor Hochschule für Life Sciences FHNW 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