Comparison Overview

DAGIGA

VS

I.O. Metro

DAGIGA

124 Milner Ave, Toronto, Ontario, M1S 3R2, CA
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.dagiga.ca

Dagiga specializes in the design and manufacture of #1 healthcare quality thermofoil components for kitchen, residential and medical facility architects, store outfitters, property developers and custom millworkers. All of our components are manufactured by our qualified engineers who have 15+ years of experience, saving customers money and time by helping them develop the best solution. Our focus is on delivering premium grade components, without premium pricing, with fast delivery turnarounds – guaranteed. Less than 1 in 10,000 of our products is returned due to manufacturer defect, and every component that leaves our facility comes with a 5-year warranty. As a proudly Canadian company, all of the wood we use comes from Canadian mills, and our thermofoil components are all manufactured at our facility in Toronto, Canada. Please visit our factory showroom to see the full selection of our products, including our thermofoil doors, available in 70+ colours and 30 different styles.

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

I.O. Metro

316B Commercial Avenue, Lowell, AR, 72745-8868, US
Last Update: 2025-11-26
Between 750 and 799
http://www.iometro.com

We're a specialty lifestyle home furnishing retailer selling modern furniture, art and accessories in retail stores in several states in the U.S. We offer a custom upholstery line, real wood goods, colorful accessories, large-scale art and more. Our design consultants are designers first, salespeople second. We offer free design service that includes space planning, color consultations, furniture and accessory selection and installation.

NAICS: 337
NAICS Definition:
Employees: 23
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/dagiga.jpeg
DAGIGA
—
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/i-o--metro.jpeg
I.O. Metro
—
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
DAGIGA
100%
Compliance Rate
0/4 Standards Verified
I.O. Metro
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 DAGIGA in 2025.

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

No incidents recorded for I.O. Metro in 2025.

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

DAGIGA cyber incidents detection timeline including parent company and subsidiaries

Incident History — I.O. Metro (X = Date, Y = Severity)

I.O. Metro cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/dagiga.jpeg
DAGIGA
Incidents

No Incident

https://images.rankiteo.com/companyimages/i-o--metro.jpeg
I.O. Metro
Incidents

No Incident

FAQ

DAGIGA company demonstrates a stronger AI Cybersecurity Score compared to I.O. Metro company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, I.O. Metro company has disclosed a higher number of cyber incidents compared to DAGIGA company.

In the current year, I.O. Metro company and DAGIGA company have not reported any cyber incidents.

Neither I.O. Metro company nor DAGIGA company has reported experiencing a ransomware attack publicly.

Neither I.O. Metro company nor DAGIGA company has reported experiencing a data breach publicly.

Neither I.O. Metro company nor DAGIGA company has reported experiencing targeted cyberattacks publicly.

Neither DAGIGA company nor I.O. Metro company has reported experiencing or disclosing vulnerabilities publicly.

Neither DAGIGA nor I.O. Metro holds any compliance certifications.

Neither company holds any compliance certifications.

Neither DAGIGA company nor I.O. Metro company has publicly disclosed detailed information about the number of their subsidiaries.

I.O. Metro company employs more people globally than DAGIGA company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither DAGIGA nor I.O. Metro holds SOC 2 Type 1 certification.

Neither DAGIGA nor I.O. Metro holds SOC 2 Type 2 certification.

Neither DAGIGA nor I.O. Metro holds ISO 27001 certification.

Neither DAGIGA nor I.O. Metro holds PCI DSS certification.

Neither DAGIGA nor I.O. Metro holds HIPAA certification.

Neither DAGIGA nor I.O. Metro 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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References