Comparison Overview

Mod43, Inc.

VS

Verizon

Mod43, Inc.

7946 North Lilley, Canton, MI, 48187, US
Last Update: 2025-03-06 (UTC)
Between 900 and 1000

Excellent

We are your single source for implementing Oracle Warehouse Management System (WMS) and Mobile Supply Chain Applications (MSCA). We have been with the product since its inception to its most current version in Release 12. Our team worked with Oracle Development on Beta WMS implementations, including the very first adopters. We have trained many other consultants, early adopters, and other major consulting firms on the product. In addition to working with the Oracle eBusiness Suite, we deliver full integration with barcode printing and handheld scanning for the warehouse environment. We assist our clients with training and configuration for popular label printing packages, as well as for handheld scanning equipment and RFID. Mod43 was founded in Canton, Michigan in 2005 by John McKeehan and Quinton Ritz. The company had previously been operating as JQCorp, LLC. Our team consists of the best talent in the field for implementing Oracle WMS. We have collectively been part of over 120 WMS, MSCA, and Loftware implementations......all successful. When your organization has need for the most experienced WMS implementation specialists in the industry, contact Mod43 for a discussion of your needs and goals.

NAICS: 541
NAICS Definition:
Employees: 13
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Verizon

One Verizon Way, None, Basking Ridge, NJ, US, 07920-1097
Last Update: 2025-08-04 (UTC)

Strong

We get you. You want more out of a career. A place to share your ideas freely โ€” even if theyโ€™re daring or different. Where the true you can learn, grow, and thrive. Youโ€™ll find all that here. Because we empower you. We power and empower how people live, work and play by connecting them to what brings them joy. The same is true inside our walls. We do what we love โ€” driving innovation, creativity, and impact in the world. And wherever you go, we got your back. This is a team sport. Our V Team is a community of people who anticipate, lead, and believe that listening is where learning begins. In crisis and in celebration, we come togetherโ€” lifting our communities and building trust in how we show up, everywhere & always. Want in? Join the V Team Life.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 97,839
Subsidiaries: 12
12-month incidents
1
Known data breaches
9
Attack type number
4

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/mod43-inc-.jpeg
Mod43, Inc.
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/verizon.jpeg
Verizon
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
Compliance Summary
Mod43, Inc.
100%
Compliance Rate
0/4 Standards Verified
Verizon
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for Mod43, Inc. in 2025.

Incidents vs IT Services and IT Consulting Industry Average (This Year)

Verizon has 69.49% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History โ€” Mod43, Inc. (X = Date, Y = Severity)

Mod43, Inc. cyber incidents detection timeline including parent company and subsidiaries

Incident History โ€” Verizon (X = Date, Y = Severity)

Verizon cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/mod43-inc-.jpeg
Mod43, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/verizon.jpeg
Verizon
Incidents

Date Detected: 4/2025
Type:Vulnerability
Attack Vector: Unsecured API
Blog: Blog

Date Detected: 10/2024
Type:Cyber Attack
Motivation: Influence Operations, Espionage
Blog: Blog

Date Detected: 10/2024
Type:Breach
Attack Vector: Network Penetration
Motivation: Espionage, Influence Operations
Blog: Blog

FAQ

Mod43, Inc. company company demonstrates a stronger AI risk posture compared to Verizon company company, reflecting its advanced AI governance and monitoring frameworks.

Verizon company has historically faced a number of disclosed cyber incidents, whereas Mod43, Inc. company has not reported any.

In the current year, Verizon company has reported more cyber incidents than Mod43, Inc. company.

Neither Verizon company nor Mod43, Inc. company has reported experiencing a ransomware attack publicly.

Verizon company has disclosed at least one data breach, while Mod43, Inc. company has not reported such incidents publicly.

Verizon company has reported targeted cyberattacks, while Mod43, Inc. company has not reported such incidents publicly.

Verizon company has disclosed at least one vulnerability, while Mod43, Inc. company has not reported such incidents publicly.

Verizon company has more subsidiaries worldwide compared to Mod43, Inc. company.

Verizon company employs more people globally than Mod43, Inc. company, reflecting its scale as a IT Services and IT Consulting.

Latest Global CVEs (Not Company-Specific)

Description

Vulnerability in Drupal Owl Carousel 2.This issue affects Owl Carousel 2: *.*.

Description

Vulnerability in Drupal API Key manager.This issue affects API Key manager: *.*.

Description

Vulnerability in Drupal Synchronize composer.Json With Contrib Modules.This issue affects Synchronize composer.Json With Contrib Modules: *.*.

Description

Improper Restriction of Excessive Authentication Attempts vulnerability in Drupal Protected Pages allows Brute Force.This issue affects Protected Pages: from 0.0.0 before 1.8.0.

Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Facets allows Cross-Site Scripting (XSS).This issue affects Facets: from 0.0.0 before 2.0.10, from 3.0.0 before 3.0.1.