Comparison Overview

Eagle

VS

Savage Arms (Canada), Inc.

Eagle

First Floor, 11-13 Godstone Road, Caterham, CR3 6RE, GB
Last Update: 2025-11-21
Between 750 and 799

Eagle have been producing quality golf products for over 30 years. We offer products to golf courses throughout the United Kingdom, Europe, Asia and the United States. We pride ourselves on our range of first-class products that will help your course to stand out from the rest. We have established a portfolio of products that look great, perform well and importantly, they will last. In addition, we also offer a bespoke design service through our studio so if you have an idea, why not allow us to harness your creativity and turn it into a reality.

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

Savage Arms (Canada), Inc.

248 Water St., Lakefield, Ontario, undefined, CA
Last Update: 2025-11-26
Between 750 and 799

Savage Arms Canada Inc. is a market leader of quality rimfire sporting rifles. We machine, assemble, and distribute our products worldwide. We are passionate and committed to delivering quality products to our customers and our culture is centered on an engaged and accountable workforce. Our goal is to attract and retain a diverse workforce; rich in talent, background, ideas and experience. We have been operating in Lakefield since 1969. We distribute over 400 models worldwide, producing between 200,000 and 300,000 units annually. Savage Arms is a strong supporter of many community causes including Santa’s Sleigh, Peterborough Musicfest, Kawartha Foodshare, Peterborough Regional Health Centre and many more. savagearms.com www.facebook.com/savagearmscanada/

NAICS: None
NAICS Definition: Others
Employees: 52
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/eagle-promotions-ltd.jpeg
Eagle
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/savage-arms-canada-inc-.jpeg
Savage Arms (Canada), Inc.
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
Eagle
100%
Compliance Rate
0/4 Standards Verified
Savage Arms (Canada), Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Eagle in 2025.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Savage Arms (Canada), Inc. in 2025.

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

Eagle cyber incidents detection timeline including parent company and subsidiaries

Incident History — Savage Arms (Canada), Inc. (X = Date, Y = Severity)

Savage Arms (Canada), Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/eagle-promotions-ltd.jpeg
Eagle
Incidents

No Incident

https://images.rankiteo.com/companyimages/savage-arms-canada-inc-.jpeg
Savage Arms (Canada), Inc.
Incidents

No Incident

FAQ

Eagle company demonstrates a stronger AI Cybersecurity Score compared to Savage Arms (Canada), Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Savage Arms (Canada), Inc. company has disclosed a higher number of cyber incidents compared to Eagle company.

In the current year, Savage Arms (Canada), Inc. company and Eagle company have not reported any cyber incidents.

Neither Savage Arms (Canada), Inc. company nor Eagle company has reported experiencing a ransomware attack publicly.

Neither Savage Arms (Canada), Inc. company nor Eagle company has reported experiencing a data breach publicly.

Neither Savage Arms (Canada), Inc. company nor Eagle company has reported experiencing targeted cyberattacks publicly.

Neither Eagle company nor Savage Arms (Canada), Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Eagle nor Savage Arms (Canada), Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Eagle company nor Savage Arms (Canada), Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Eagle company employs more people globally than Savage Arms (Canada), Inc. company, reflecting its scale as a Sporting Goods.

Neither Eagle nor Savage Arms (Canada), Inc. holds SOC 2 Type 1 certification.

Neither Eagle nor Savage Arms (Canada), Inc. holds SOC 2 Type 2 certification.

Neither Eagle nor Savage Arms (Canada), Inc. holds ISO 27001 certification.

Neither Eagle nor Savage Arms (Canada), Inc. holds PCI DSS certification.

Neither Eagle nor Savage Arms (Canada), Inc. holds HIPAA certification.

Neither Eagle nor Savage Arms (Canada), Inc. 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