Comparison Overview

BROSA

VS

OstermanCron

BROSA

undefined, South Melbourne, Victoria, 3205, AU
Last Update: 2025-11-26
Between 750 and 799

Brosa was born out of discontent with the status quo, and a desire to change the furniture industry for the better. Adhering by the values of quality, choice, value, and accessibility, Brosa seek to change the furniture and homewares industry and consumer landscape, by offering exceptional customer experiences underpinned by digital-first thinking. First and foremost, Brosa care about creating an amazing experience for the consumer – ultimately offering a better way to buy furniture. Brosa has built their whole business around delivering a seamless browsing and buying experience, and helps support decisions by providing advice and support throughout the whole customer journey. By owning their own supply chain, Brosa are able to deliver great furniture, at a great price point. Brosa means ‘smile’ in Icelandic: Brosa’s very first products were raw and natural, inspired by the design philosophies of that region. Brosa has since expanded their range, but the emphasis on delivering new designs and inspiration, accessible pricing, and unmatched customer experiences both online and offline remains front and centre. Brosa is changing the face of how Australians furnish their homes.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 26
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

OstermanCron

10830 Millington Court, Cincinnati, OH, 45242, US
Last Update: 2025-11-26
Between 750 and 799

OstermanCron is a progressive office furniture dealer serving Greater Cincinnati, Dayton, Northern Kentucky, and Louisville. Comprised of a hard-working, experienced, and engaged team who will deliver on time, OstermanCron provides a wide range of furniture solutions coupled with a full spectrum of services to ensure success with every project—large and small. Through our vibrant teams and partnerships, we create solutions for those we serve and set our clients apart by creating environments people love—so that we are all better at the end of the season. Founded in 1997, OstermanCron has assisted in furnishing hundreds of offices, medical facilities, and educational environments across the nation.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 32
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/brosa.jpeg
BROSA
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/ostermancron.jpeg
OstermanCron
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
BROSA
100%
Compliance Rate
0/4 Standards Verified
OstermanCron
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Furniture and Home Furnishings Manufacturing Industry Average (This Year)

No incidents recorded for BROSA in 2025.

Incidents vs Furniture and Home Furnishings Manufacturing Industry Average (This Year)

No incidents recorded for OstermanCron in 2025.

Incident History — BROSA (X = Date, Y = Severity)

BROSA cyber incidents detection timeline including parent company and subsidiaries

Incident History — OstermanCron (X = Date, Y = Severity)

OstermanCron cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/brosa.jpeg
BROSA
Incidents

No Incident

https://images.rankiteo.com/companyimages/ostermancron.jpeg
OstermanCron
Incidents

No Incident

FAQ

Both BROSA company and OstermanCron company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, OstermanCron company has disclosed a higher number of cyber incidents compared to BROSA company.

In the current year, OstermanCron company and BROSA company have not reported any cyber incidents.

Neither OstermanCron company nor BROSA company has reported experiencing a ransomware attack publicly.

Neither OstermanCron company nor BROSA company has reported experiencing a data breach publicly.

Neither OstermanCron company nor BROSA company has reported experiencing targeted cyberattacks publicly.

Neither BROSA company nor OstermanCron company has reported experiencing or disclosing vulnerabilities publicly.

Neither BROSA nor OstermanCron holds any compliance certifications.

Neither company holds any compliance certifications.

Neither BROSA company nor OstermanCron company has publicly disclosed detailed information about the number of their subsidiaries.

OstermanCron company employs more people globally than BROSA company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither BROSA nor OstermanCron holds SOC 2 Type 1 certification.

Neither BROSA nor OstermanCron holds SOC 2 Type 2 certification.

Neither BROSA nor OstermanCron holds ISO 27001 certification.

Neither BROSA nor OstermanCron holds PCI DSS certification.

Neither BROSA nor OstermanCron holds HIPAA certification.

Neither BROSA nor OstermanCron holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.