Comparison Overview

AH Beard

VS

Vaughan Benz

AH Beard

1/35 Bryant St, Padstow, New South Wales, 2211, AU
Last Update: 2025-11-26
Between 750 and 799

At A.H.Beard, we are passionate about sleep, and with 120 years of experience crafting quality mattresses, it’s a topic we know a lot about. Five generations of the A.H. Beard family have been committed to continuous innovation to ensure that we remain leaders in our field. Today, A.H. Beard employs a team of over 400 dedicated and highly skilled people to produce up to 10,000 mattress each week, which are sold in Australia, New Zealand and around the world.

NAICS: 337
NAICS Definition:
Employees: 146
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Vaughan Benz

1635 N. Main Street, Los Angeles, California 90012, US
Last Update: 2025-11-28
Between 750 and 799

Vaughan Benz is a leading manufacturer of high-end custom-made wood and upholstered furniture for the hospitality industry. Based in Los Angeles with factories in California and China, Vaughan Benz specializes in superior-quality furniture for some of the world’s finest four and five-star hotels and restaurants. Our products grace the interiors of such international and luxury hotel chains as Four Seasons, Peninsula and Ritz-Carlton. We are a favored source of many award winning interior designers and design firms.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 29
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/a.-h-beard.jpeg
AH Beard
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/vaughan-benz.jpeg
Vaughan Benz
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
AH Beard
100%
Compliance Rate
0/4 Standards Verified
Vaughan Benz
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 AH Beard in 2025.

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

No incidents recorded for Vaughan Benz in 2025.

Incident History — AH Beard (X = Date, Y = Severity)

AH Beard cyber incidents detection timeline including parent company and subsidiaries

Incident History — Vaughan Benz (X = Date, Y = Severity)

Vaughan Benz cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/a.-h-beard.jpeg
AH Beard
Incidents

No Incident

https://images.rankiteo.com/companyimages/vaughan-benz.jpeg
Vaughan Benz
Incidents

No Incident

FAQ

Both AH Beard company and Vaughan Benz company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Vaughan Benz company has disclosed a higher number of cyber incidents compared to AH Beard company.

In the current year, Vaughan Benz company and AH Beard company have not reported any cyber incidents.

Neither Vaughan Benz company nor AH Beard company has reported experiencing a ransomware attack publicly.

Neither Vaughan Benz company nor AH Beard company has reported experiencing a data breach publicly.

Neither Vaughan Benz company nor AH Beard company has reported experiencing targeted cyberattacks publicly.

Neither AH Beard company nor Vaughan Benz company has reported experiencing or disclosing vulnerabilities publicly.

Neither AH Beard nor Vaughan Benz holds any compliance certifications.

Neither company holds any compliance certifications.

Neither AH Beard company nor Vaughan Benz company has publicly disclosed detailed information about the number of their subsidiaries.

AH Beard company employs more people globally than Vaughan Benz company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither AH Beard nor Vaughan Benz holds SOC 2 Type 1 certification.

Neither AH Beard nor Vaughan Benz holds SOC 2 Type 2 certification.

Neither AH Beard nor Vaughan Benz holds ISO 27001 certification.

Neither AH Beard nor Vaughan Benz holds PCI DSS certification.

Neither AH Beard nor Vaughan Benz holds HIPAA certification.

Neither AH Beard nor Vaughan Benz 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.