Comparison Overview

Shoto Corporation

VS

MOI

Shoto Corporation

6450 County Road B, Two Rivers, Wisconsin, 54241, US
Last Update: 2025-11-26
Between 750 and 799

Shoto Corporation, based in Shoto, Wisconsin is a family-owned business that was founded in 1954. Situated on the beautiful West Twin River dam, the main manufacturing facility was the former Neshoto Saw and Flour Mill, which was destroyed by fire in 1949. Portions of the existing structure were salvaged and re-built into 4,500 sq. ft. of space to start a local cabinet shop business (Shoto Fixture and Supply) with the first customers being home owners interested in beautiful kitchen and bath cabinetry. Over the years, products manufactured expanded into the hospitality, healthcare, office furniture, and school furniture markets. At this point, Shoto became one of the premier builders of bars and restaurant fixtures in the Midwest. This expansion of products and customers required additional floor space with multiple facility expansions from 1963-1977 at the main site. In 1999, a second building was erected in nearby Two Rivers, Wisconsin to support growth and future expanstion. As our facilities have grown, Shoto has also diversified its capabilities by investing in state of the art CNC machinery and production processes. Regardless of the reliability and accuracy of our machinery, attention to detail and quality remains our hallmark. Shoto Corporation currently employs 75 full time workers and continues to produce first-class products at both facilities.

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

MOI

1801 Porter Street, Suite 100, Baltimore, MD, US, 21230
Last Update: 2025-11-26
Between 750 and 799

MOI partners to create unique spaces that reflect our clients’ needs, transform their environments, and enhance their cultures. We have worked with global law firms, large tech companies, government agencies, small boutiques, and everything in between. We partner with you to create intelligent spaces where people want to work, live, and stay.

NAICS: 337
NAICS Definition: Furniture and Related Product Manufacturing
Employees: 2,367
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/shoto-corporation.jpeg
Shoto Corporation
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/moiinc.jpeg
MOI
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
Shoto Corporation
100%
Compliance Rate
0/4 Standards Verified
MOI
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 Shoto Corporation in 2025.

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

No incidents recorded for MOI in 2025.

Incident History — Shoto Corporation (X = Date, Y = Severity)

Shoto Corporation cyber incidents detection timeline including parent company and subsidiaries

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

MOI cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/shoto-corporation.jpeg
Shoto Corporation
Incidents

No Incident

https://images.rankiteo.com/companyimages/moiinc.jpeg
MOI
Incidents

No Incident

FAQ

MOI company demonstrates a stronger AI Cybersecurity Score compared to Shoto Corporation company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, MOI company has disclosed a higher number of cyber incidents compared to Shoto Corporation company.

In the current year, MOI company and Shoto Corporation company have not reported any cyber incidents.

Neither MOI company nor Shoto Corporation company has reported experiencing a ransomware attack publicly.

Neither MOI company nor Shoto Corporation company has reported experiencing a data breach publicly.

Neither MOI company nor Shoto Corporation company has reported experiencing targeted cyberattacks publicly.

Neither Shoto Corporation company nor MOI company has reported experiencing or disclosing vulnerabilities publicly.

Neither Shoto Corporation nor MOI holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Shoto Corporation company nor MOI company has publicly disclosed detailed information about the number of their subsidiaries.

MOI company employs more people globally than Shoto Corporation company, reflecting its scale as a Furniture and Home Furnishings Manufacturing.

Neither Shoto Corporation nor MOI holds SOC 2 Type 1 certification.

Neither Shoto Corporation nor MOI holds SOC 2 Type 2 certification.

Neither Shoto Corporation nor MOI holds ISO 27001 certification.

Neither Shoto Corporation nor MOI holds PCI DSS certification.

Neither Shoto Corporation nor MOI holds HIPAA certification.

Neither Shoto Corporation nor MOI 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.