Comparison Overview

Kada

VS

Pigott

Kada

165 The Strand , Auckland, Auckland , 1010, NZ
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.kada.co.nz

We represent leading furniture brands A.WORKS, Actiu, Artek, Dauphin, Framery, Schiavello, Steelcase and Vitra exclusively in New Zealand. Our ethos is to supply quality workplace solutions for contemporary and streamlined corporate office, education and hospitality environments. Our offerings are leading edge in all forms of workplace trends, giving you quality, innovative and collaborative designs. Kada has delivered projects that have changed the traditional hierarchical office structures into contemporary, fluid, changeable office spaces that meet the needs for team collaboration, and multi functional work environments that engage the users. Our Auckland and Wellington showrooms are open to visit Mon - Fri between 8am and 5pm.

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

Pigott

3815 Ingersoll Avenue, Des Moines, IA, 50312, US
Last Update: 2025-11-26
Between 750 and 799
http://www.pigottnet.com

As a Certified MillerKnoll Dealer, Pigott is Iowa and South Dakota's premiere source for commercial interior design solutions, specializing in corporate, healthcare, government & education interiors. MillerKnoll 2023 Platinum Award Winner When people are inspired by place, anything is possible. An environment powered by human-centered design can spark potential and drive prosperity. People-First Approach We apply proven insights about the connection between people and place to enhance engagement and boost performance. Result-Driven Design From understanding your aspirations to exceptional implementation, we’llwork together to create elevated places that drive success. Forward-Thinking Solutions With our innovative place-making solutions and broad product offering, your space will fuel results now—and long into the future.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 135
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/kada.jpeg
Kada
—
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/pigott-inc-.jpeg
Pigott
—
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
Kada
100%
Compliance Rate
0/4 Standards Verified
Pigott
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 Kada in 2025.

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

No incidents recorded for Pigott in 2025.

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

Kada cyber incidents detection timeline including parent company and subsidiaries

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

Pigott cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kada.jpeg
Kada
Incidents

No Incident

https://images.rankiteo.com/companyimages/pigott-inc-.jpeg
Pigott
Incidents

No Incident

FAQ

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

Historically, Pigott company has disclosed a higher number of cyber incidents compared to Kada company.

In the current year, Pigott company and Kada company have not reported any cyber incidents.

Neither Pigott company nor Kada company has reported experiencing a ransomware attack publicly.

Neither Pigott company nor Kada company has reported experiencing a data breach publicly.

Neither Pigott company nor Kada company has reported experiencing targeted cyberattacks publicly.

Neither Kada company nor Pigott company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kada nor Pigott holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Kada company nor Pigott company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Kada nor Pigott holds SOC 2 Type 1 certification.

Neither Kada nor Pigott holds SOC 2 Type 2 certification.

Neither Kada nor Pigott holds ISO 27001 certification.

Neither Kada nor Pigott holds PCI DSS certification.

Neither Kada nor Pigott holds HIPAA certification.

Neither Kada nor Pigott 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