Comparison Overview

Standee Co.

VS

Castle Furniture

Standee Co.

None
Last Update: 2025-11-21
Between 750 and 799

Standee™ designs and manufactures stand-up desks and related products that reduce the health risks associated with sedentary work environments. Our goal is to fundamentally change the way people work, and in doing so, dramatically improve the health and longevity of the world’s workforce. We intend to revolutionize the workplace by educating companies and their workers on the health hazards of sitting at work and by empowering employers and employees to adopt a new more active, healthy, and engaging approach to work.

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

Castle Furniture

6965 S. Priest Dr. Suite 1, Tempe, 85283, US
Last Update: 2025-11-22
Between 750 and 799

Castle Furniture is a family owned and operated furniture company located in Tempe, Arizona. Established in 1993, Castle provides a variety of furniture rental packages, including custom home staging options. Castle also offers housewares rentals, which are processed in house in order to minimize rental costs for customers.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 35
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/standee-co-.jpeg
Standee Co.
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/defaultcompany.jpeg
Castle Furniture
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
Standee Co.
100%
Compliance Rate
0/4 Standards Verified
Castle Furniture
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 Standee Co. in 2025.

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

No incidents recorded for Castle Furniture in 2025.

Incident History — Standee Co. (X = Date, Y = Severity)

Standee Co. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Castle Furniture (X = Date, Y = Severity)

Castle Furniture cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/standee-co-.jpeg
Standee Co.
Incidents

No Incident

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Castle Furniture
Incidents

No Incident

FAQ

Standee Co. company demonstrates a stronger AI Cybersecurity Score compared to Castle Furniture company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Castle Furniture company has disclosed a higher number of cyber incidents compared to Standee Co. company.

In the current year, Castle Furniture company and Standee Co. company have not reported any cyber incidents.

Neither Castle Furniture company nor Standee Co. company has reported experiencing a ransomware attack publicly.

Neither Castle Furniture company nor Standee Co. company has reported experiencing a data breach publicly.

Neither Castle Furniture company nor Standee Co. company has reported experiencing targeted cyberattacks publicly.

Neither Standee Co. company nor Castle Furniture company has reported experiencing or disclosing vulnerabilities publicly.

Neither Standee Co. nor Castle Furniture holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Standee Co. company nor Castle Furniture company has publicly disclosed detailed information about the number of their subsidiaries.

Neither Standee Co. nor Castle Furniture holds SOC 2 Type 1 certification.

Neither Standee Co. nor Castle Furniture holds SOC 2 Type 2 certification.

Neither Standee Co. nor Castle Furniture holds ISO 27001 certification.

Neither Standee Co. nor Castle Furniture holds PCI DSS certification.

Neither Standee Co. nor Castle Furniture holds HIPAA certification.

Neither Standee Co. nor Castle Furniture 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.