Comparison Overview

e2e4

VS

Fractal Scientific

e2e4

None
Last Update: 2025-11-27
Between 800 and 849

The Open Technologies LLC has been operating on the Siberian market of computer hardware and digital technologies since 2003. We started rebranding in April 2012 and launched the new trademark - e2e4. Nowadays the Open Technologies retail chain includes seventeen e2e4 outlets in Novosibirsk, Kemerovo and Tomsk Regions and also in Altai, Omsk and Krasnoyarsk. Open Technologies LLC is a part of Top 100 biggest companies of Novosibirsk Region and of the Top 100 Internet shops according to the Kommersant newspaper.

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

Fractal Scientific

14 Cerqua St, Woburn, Massachusetts, 01801, US
Last Update: 2025-11-27

Fractal Scientific specializes in the design and development of precision IoT-enabled sensors for demanding industrial applications. Our goal is to help our customers transition to a smarter and more connected factory, site, or refinery. Adopting “smart” sensors allows operators to access more detailed data, giving them the opportunity to optimize their processes and quickly make informed decisions. Transitioning to a smart factory does not need to be complicated or expensive. Industrial asset management often requires manual data acquisition in dangerous or hard-to-reach areas. Smart sensors can automate this process, reducing the risk of work related accidents while providing more reliable results.

NAICS: None
NAICS Definition:
Employees: 3
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/e2e4.jpeg
e2e4
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/fractal-scientific.jpeg
Fractal Scientific
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
e2e4
100%
Compliance Rate
0/4 Standards Verified
Fractal Scientific
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Computer Hardware Industry Average (This Year)

No incidents recorded for e2e4 in 2025.

Incidents vs Computer Hardware Industry Average (This Year)

No incidents recorded for Fractal Scientific in 2025.

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

e2e4 cyber incidents detection timeline including parent company and subsidiaries

Incident History — Fractal Scientific (X = Date, Y = Severity)

Fractal Scientific cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/e2e4.jpeg
e2e4
Incidents

No Incident

https://images.rankiteo.com/companyimages/fractal-scientific.jpeg
Fractal Scientific
Incidents

No Incident

FAQ

e2e4 company demonstrates a stronger AI Cybersecurity Score compared to Fractal Scientific company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Fractal Scientific company has disclosed a higher number of cyber incidents compared to e2e4 company.

In the current year, Fractal Scientific company and e2e4 company have not reported any cyber incidents.

Neither Fractal Scientific company nor e2e4 company has reported experiencing a ransomware attack publicly.

Neither Fractal Scientific company nor e2e4 company has reported experiencing a data breach publicly.

Neither Fractal Scientific company nor e2e4 company has reported experiencing targeted cyberattacks publicly.

Neither e2e4 company nor Fractal Scientific company has reported experiencing or disclosing vulnerabilities publicly.

Neither e2e4 nor Fractal Scientific holds any compliance certifications.

Neither company holds any compliance certifications.

Neither e2e4 company nor Fractal Scientific company has publicly disclosed detailed information about the number of their subsidiaries.

e2e4 company employs more people globally than Fractal Scientific company, reflecting its scale as a Computer Hardware.

Neither e2e4 nor Fractal Scientific holds SOC 2 Type 1 certification.

Neither e2e4 nor Fractal Scientific holds SOC 2 Type 2 certification.

Neither e2e4 nor Fractal Scientific holds ISO 27001 certification.

Neither e2e4 nor Fractal Scientific holds PCI DSS certification.

Neither e2e4 nor Fractal Scientific holds HIPAA certification.

Neither e2e4 nor Fractal Scientific 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