Comparison Overview

Magpul Industries Corp.

VS

Sport Court

Magpul Industries Corp.

8226 Bee Cave Rd, Austin, 78746, US
Last Update: 2025-11-21
Between 750 and 799

Magpul was founded in 1999 with the idea of developing a simple product to aid in the handling of rifle magazines under stress. The company name comes from this original product, called the Magpul. Over the last 22+ years, Magpul has continued to grow and develop, following the same mission and processes and focusing on innovation, simplicity, and efficiency. Our product lines include hundreds of firearms accessories and other gear that have all been designed to professional-use standards. There are now more than 300 unique products with hundreds of variants, including magazines, stocks, slings, sights, grips, handguards, bipods, eyewear, and other dependable, hard-use gear.

NAICS: None
NAICS Definition: Others
Employees: 243
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Sport Court

5445 W Harold Gatty Dr, Salt Lake City, US
Last Update: 2025-11-21
Between 750 and 799

Champions Start Here For over 40 years, Sport Court has helped families and kids unlock their true potential. Through our 150,000 courts in more than 100 countries on all seven continents, our courts have created safe colorful places for kids to learn the values taught by sport. In fact, many of the world’s leading sports association trust Sport Court for their athletes. In fact, USA Volleyball Olympic National Teams, the NCAA Men's and Women's Volleyball Championships, FIBA 3x3 World Championships and US Youth Futsal Championships all take place on our surface! From the backyard to the sports facility, Sport Court helps its customers unlock their potential, in sports and in life. Find out more about our organization at www.sportcourt.com

NAICS: None
NAICS Definition: Others
Employees: 138
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/magpul-industries-corp.jpeg
Magpul Industries Corp.
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/sport-court.jpeg
Sport Court
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
Magpul Industries Corp.
100%
Compliance Rate
0/4 Standards Verified
Sport Court
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Magpul Industries Corp. in 2025.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Sport Court in 2025.

Incident History — Magpul Industries Corp. (X = Date, Y = Severity)

Magpul Industries Corp. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Sport Court (X = Date, Y = Severity)

Sport Court cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/magpul-industries-corp.jpeg
Magpul Industries Corp.
Incidents

No Incident

https://images.rankiteo.com/companyimages/sport-court.jpeg
Sport Court
Incidents

No Incident

FAQ

Magpul Industries Corp. company demonstrates a stronger AI Cybersecurity Score compared to Sport Court company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Sport Court company has disclosed a higher number of cyber incidents compared to Magpul Industries Corp. company.

In the current year, Sport Court company and Magpul Industries Corp. company have not reported any cyber incidents.

Neither Sport Court company nor Magpul Industries Corp. company has reported experiencing a ransomware attack publicly.

Neither Sport Court company nor Magpul Industries Corp. company has reported experiencing a data breach publicly.

Neither Sport Court company nor Magpul Industries Corp. company has reported experiencing targeted cyberattacks publicly.

Neither Magpul Industries Corp. company nor Sport Court company has reported experiencing or disclosing vulnerabilities publicly.

Neither Magpul Industries Corp. nor Sport Court holds any compliance certifications.

Neither company holds any compliance certifications.

Sport Court company has more subsidiaries worldwide compared to Magpul Industries Corp. company.

Magpul Industries Corp. company employs more people globally than Sport Court company, reflecting its scale as a Sporting Goods.

Neither Magpul Industries Corp. nor Sport Court holds SOC 2 Type 1 certification.

Neither Magpul Industries Corp. nor Sport Court holds SOC 2 Type 2 certification.

Neither Magpul Industries Corp. nor Sport Court holds ISO 27001 certification.

Neither Magpul Industries Corp. nor Sport Court holds PCI DSS certification.

Neither Magpul Industries Corp. nor Sport Court holds HIPAA certification.

Neither Magpul Industries Corp. nor Sport Court holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H