Comparison Overview

TekTracking

VS

American Turbocharger Technologies

TekTracking

10 Norbrook rd, Fairport, New York, 14450, US
Last Update: 2025-11-27
Between 700 and 749

TekTracking specializes in assisting manufacturers and suppliers with their market reach in North America, we have in depth knowledge of engineering standards and requirements and help our clients prepare their offering for market entry. Our leadership has developed a network of clients spanning all Class 1, passenger, regional and short line railroads. The team is comprised of industry experienced experts who can effectively present technical products and solutions to our railroad customer base. We have developed a network of key decision makers to whom we effectively communicate the value proposition of our client’s technology products. We understand how to navigate the complex selling environment present in the rail industry, and generate orders to grow top line and bottom line results for our clients. Our team travels extensively to meet our railroad customers to professionally represent your products.

NAICS: 336
NAICS Definition:
Employees: 8
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

American Turbocharger Technologies

None
Last Update: 2025-11-27

We provide fast and professional services for operators of 901-5,000 horsepower marine, locomotive and stationary diesel engines. American Turbocharger Technologies remanufactures each turbocharger with integrity and precision to allow our customers the dependability to take care of theirs. With over a combined 200 years of experience in the turbocharger repair business, and a 20,000-square-foot facility located in the center of the world’s largest naval port (Newport News, VA) – we are easily accessible and well-equipped to take on your most difficult challenges!

NAICS: 3365
NAICS Definition: Railroad Rolling Stock Manufacturing
Employees: 10
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/tektracking.jpeg
TekTracking
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/american-turbocharger-technologies.jpeg
American Turbocharger Technologies
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
TekTracking
100%
Compliance Rate
0/4 Standards Verified
American Turbocharger Technologies
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for TekTracking in 2025.

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for American Turbocharger Technologies in 2025.

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

TekTracking cyber incidents detection timeline including parent company and subsidiaries

Incident History — American Turbocharger Technologies (X = Date, Y = Severity)

American Turbocharger Technologies cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/tektracking.jpeg
TekTracking
Incidents

No Incident

https://images.rankiteo.com/companyimages/american-turbocharger-technologies.jpeg
American Turbocharger Technologies
Incidents

No Incident

FAQ

American Turbocharger Technologies company demonstrates a stronger AI Cybersecurity Score compared to TekTracking company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, American Turbocharger Technologies company has disclosed a higher number of cyber incidents compared to TekTracking company.

In the current year, American Turbocharger Technologies company and TekTracking company have not reported any cyber incidents.

Neither American Turbocharger Technologies company nor TekTracking company has reported experiencing a ransomware attack publicly.

Neither American Turbocharger Technologies company nor TekTracking company has reported experiencing a data breach publicly.

Neither American Turbocharger Technologies company nor TekTracking company has reported experiencing targeted cyberattacks publicly.

Neither TekTracking company nor American Turbocharger Technologies company has reported experiencing or disclosing vulnerabilities publicly.

Neither TekTracking nor American Turbocharger Technologies holds any compliance certifications.

Neither company holds any compliance certifications.

American Turbocharger Technologies company has more subsidiaries worldwide compared to TekTracking company.

American Turbocharger Technologies company employs more people globally than TekTracking company, reflecting its scale as a Railroad Equipment Manufacturing.

Neither TekTracking nor American Turbocharger Technologies holds SOC 2 Type 1 certification.

Neither TekTracking nor American Turbocharger Technologies holds SOC 2 Type 2 certification.

Neither TekTracking nor American Turbocharger Technologies holds ISO 27001 certification.

Neither TekTracking nor American Turbocharger Technologies holds PCI DSS certification.

Neither TekTracking nor American Turbocharger Technologies holds HIPAA certification.

Neither TekTracking nor American Turbocharger Technologies 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