Comparison Overview

UBC Baja SAE

VS

Herman Goldner Co., Inc.

UBC Baja SAE

2345 East Mall, Vancouver, British Columbia, V6T, CA
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.ubcbaja.com/

UBC Baja is a team of dedicated Undergraduate Engineering Students from The University of British Columbia. Together the team works to design, build, test, and race a single seat all-terrain vehicle in International SAE Baja competitions. At competition, the team competes against 100+ other teams from across the globe and interact with automotive and off-road industry leaders. To follow this path effectively, UBC Baja creates a professional environment to not only provide an effective & collaborative environment for team members, but also facilitate the development of a vehicle that represent the team’s sponsors and the University well.

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

Herman Goldner Co., Inc.

7777 Brewster Ave., Philadelphia, PA, 19153, US
Last Update: 2025-11-27
Between 750 and 799
http://goldner.com/

Since 1887, Herman Goldner Co., Inc has provided the Philadelphia, New Jersey, and Northern Delaware areas with quality customer service and craftsmanship. We are a full service mechanical and solutions provider specializing in HVAC, chiller service & repair, mechanical construction, plumbing, sanitary process piping, building automation services, and fabrication. The Company has committed itself to providing quality craftsmanship with an emphasis on customer service. Meeting the needs of our customers is paramount within our organization. Our experienced team of Account Executives, Project Managers, Engineers and Skilled Tradesmen offer our clients quality, cost-effective solutions.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ubc-baja-sae.jpeg
UBC Baja SAE
—
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/herman-goldner-co--inc-.jpeg
Herman Goldner Co., 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
UBC Baja SAE
100%
Compliance Rate
0/4 Standards Verified
Herman Goldner Co., Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for UBC Baja SAE in 2025.

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for Herman Goldner Co., Inc. in 2025.

Incident History — UBC Baja SAE (X = Date, Y = Severity)

UBC Baja SAE cyber incidents detection timeline including parent company and subsidiaries

Incident History — Herman Goldner Co., Inc. (X = Date, Y = Severity)

Herman Goldner Co., Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ubc-baja-sae.jpeg
UBC Baja SAE
Incidents

No Incident

https://images.rankiteo.com/companyimages/herman-goldner-co--inc-.jpeg
Herman Goldner Co., Inc.
Incidents

No Incident

FAQ

Both UBC Baja SAE company and Herman Goldner Co., Inc. company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Herman Goldner Co., Inc. company has disclosed a higher number of cyber incidents compared to UBC Baja SAE company.

In the current year, Herman Goldner Co., Inc. company and UBC Baja SAE company have not reported any cyber incidents.

Neither Herman Goldner Co., Inc. company nor UBC Baja SAE company has reported experiencing a ransomware attack publicly.

Neither Herman Goldner Co., Inc. company nor UBC Baja SAE company has reported experiencing a data breach publicly.

Neither Herman Goldner Co., Inc. company nor UBC Baja SAE company has reported experiencing targeted cyberattacks publicly.

Neither UBC Baja SAE company nor Herman Goldner Co., Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither UBC Baja SAE nor Herman Goldner Co., Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Herman Goldner Co., Inc. company has more subsidiaries worldwide compared to UBC Baja SAE company.

Herman Goldner Co., Inc. company employs more people globally than UBC Baja SAE company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither UBC Baja SAE nor Herman Goldner Co., Inc. holds SOC 2 Type 1 certification.

Neither UBC Baja SAE nor Herman Goldner Co., Inc. holds SOC 2 Type 2 certification.

Neither UBC Baja SAE nor Herman Goldner Co., Inc. holds ISO 27001 certification.

Neither UBC Baja SAE nor Herman Goldner Co., Inc. holds PCI DSS certification.

Neither UBC Baja SAE nor Herman Goldner Co., Inc. holds HIPAA certification.

Neither UBC Baja SAE nor Herman Goldner Co., 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References