Comparison Overview

PT. Jabaku Karaba Technologies

VS

4E Engineering GmbH, Basel

PT. Jabaku Karaba Technologies

None
Last Update: 2025-11-28
Between 750 and 799

kyocera cutting tools distributor and automation system PT. JABAKU KARABA TECHNOLOGIES has become authorized distributor KYOCERA Cutting tools. Which provides a variety of cutting tools need to support productivity. According to the motto KYOCERA “Contributing To Advancing Productivity”, and supported with our motto “Uncompromising Quality, Reliable Solutions, Cost Effective and On Time Delivery”, we provide the right solution for the needs of industry.

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

4E Engineering GmbH, Basel

Dornacherstrasse 101, Basel, 4053, CH
Last Update: 2025-11-27
Between 750 and 799

4E Engineering besteht seit 2008 als selbständiges, unabhängiges Ingenieurbüro mit einem breitgefächerten Angebot für Engineering- und Consulting Dienstleistungen. Zu unseren Kunden zählt vorwiegend die chemische und pharmazeutische Industrie in der Region Nordwestschweiz. Dank der langjährigen Erfahrung unserer Mitarbeiter und unserem Netzwerk zu Kunden, Lieferanten und Spezialisten, konnte sich 4E Engineering rasch am Markt etablieren. In der Folge wuchs die 4E Engineering schnell zu einem mittelständischen Ingenieurbüro, welches in der Region Nordwestschweiz als zuverlässiger und flexibler Partner wahrgenommen wird.

NAICS: None
NAICS Definition: Others
Employees: 14
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/defaultcompany.jpeg
PT. Jabaku Karaba 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
https://images.rankiteo.com/companyimages/4e-engineering-gmbh.jpeg
4E Engineering GmbH, Basel
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
PT. Jabaku Karaba Technologies
100%
Compliance Rate
0/4 Standards Verified
4E Engineering GmbH, Basel
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 PT. Jabaku Karaba Technologies in 2025.

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

No incidents recorded for 4E Engineering GmbH, Basel in 2025.

Incident History — PT. Jabaku Karaba Technologies (X = Date, Y = Severity)

PT. Jabaku Karaba Technologies cyber incidents detection timeline including parent company and subsidiaries

Incident History — 4E Engineering GmbH, Basel (X = Date, Y = Severity)

4E Engineering GmbH, Basel cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
PT. Jabaku Karaba Technologies
Incidents

No Incident

https://images.rankiteo.com/companyimages/4e-engineering-gmbh.jpeg
4E Engineering GmbH, Basel
Incidents

No Incident

FAQ

PT. Jabaku Karaba Technologies company demonstrates a stronger AI Cybersecurity Score compared to 4E Engineering GmbH, Basel company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, 4E Engineering GmbH, Basel company has disclosed a higher number of cyber incidents compared to PT. Jabaku Karaba Technologies company.

In the current year, 4E Engineering GmbH, Basel company and PT. Jabaku Karaba Technologies company have not reported any cyber incidents.

Neither 4E Engineering GmbH, Basel company nor PT. Jabaku Karaba Technologies company has reported experiencing a ransomware attack publicly.

Neither 4E Engineering GmbH, Basel company nor PT. Jabaku Karaba Technologies company has reported experiencing a data breach publicly.

Neither 4E Engineering GmbH, Basel company nor PT. Jabaku Karaba Technologies company has reported experiencing targeted cyberattacks publicly.

Neither PT. Jabaku Karaba Technologies company nor 4E Engineering GmbH, Basel company has reported experiencing or disclosing vulnerabilities publicly.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PT. Jabaku Karaba Technologies company nor 4E Engineering GmbH, Basel company has publicly disclosed detailed information about the number of their subsidiaries.

PT. Jabaku Karaba Technologies company employs more people globally than 4E Engineering GmbH, Basel company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel holds SOC 2 Type 1 certification.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel holds SOC 2 Type 2 certification.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel holds ISO 27001 certification.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel holds PCI DSS certification.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel holds HIPAA certification.

Neither PT. Jabaku Karaba Technologies nor 4E Engineering GmbH, Basel 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