Comparison Overview

South Port NZ

VS

Kuehne+Nagel

South Port NZ

Island Harbour, None, Bluff, Southland, NZ, 9814
Last Update: 2025-11-26
Between 700 and 749

Located in Bluff Harbour, at the southern tip of New Zealand’s South Island, South Port is New Zealand’s southernmost commercial deep water port. From its base on the 40ha man-made Island Harbour, South Port is proud to provide a full range of marine services, cargo and container shipping, and on-site warehousing for domestic and international customers. The port is ideally situated to service Southland’s significant export and import industries including aluminium, timber, fisheries, dairy, meat, wood chips, stock food, cement, alumina, fertiliser and petroleum products. South Port prides itself on adding value to its import and export customers, providing customised solutions to meet their needs and partnering with them to achieve their operational objectives.

NAICS: 47
NAICS Definition: Transportation and Warehousing
Employees: 57
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Kuehne+Nagel

Kuehne + Nagel, Schindellegi, 8834, CH
Last Update: 2025-11-23
Between 750 and 799

With more than 82,000 employees at almost 1,300 sites in close to 100 countries, the Kuehne+Nagel Group is one of the world's leading logistics providers. Headquartered in Switzerland, Kuehne+Nagel is listed in the Swiss blue-chip stock market index, the SMI. The Group is the global number one in air and sea logistics and has strong market positions in road and contract logistics. Kuehne+Nagel is the logistics partner of choice for 400,000 customers worldwide. Using its global network, logistics expertise and data-based insights, the Group provides end-to-end supply chain solutions for global companies and industries.

NAICS: 47
NAICS Definition: Transportation and Warehousing
Employees: 50,155
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/south-port-nz.jpeg
South Port NZ
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/kuehne-nagel.jpeg
Kuehne+Nagel
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
South Port NZ
100%
Compliance Rate
0/4 Standards Verified
Kuehne+Nagel
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Average (This Year)

No incidents recorded for South Port NZ in 2025.

Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Average (This Year)

No incidents recorded for Kuehne+Nagel in 2025.

Incident History — South Port NZ (X = Date, Y = Severity)

South Port NZ cyber incidents detection timeline including parent company and subsidiaries

Incident History — Kuehne+Nagel (X = Date, Y = Severity)

Kuehne+Nagel cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/south-port-nz.jpeg
South Port NZ
Incidents

No Incident

https://images.rankiteo.com/companyimages/kuehne-nagel.jpeg
Kuehne+Nagel
Incidents

No Incident

FAQ

Kuehne+Nagel company demonstrates a stronger AI Cybersecurity Score compared to South Port NZ company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Kuehne+Nagel company has disclosed a higher number of cyber incidents compared to South Port NZ company.

In the current year, Kuehne+Nagel company and South Port NZ company have not reported any cyber incidents.

Neither Kuehne+Nagel company nor South Port NZ company has reported experiencing a ransomware attack publicly.

Neither Kuehne+Nagel company nor South Port NZ company has reported experiencing a data breach publicly.

Neither Kuehne+Nagel company nor South Port NZ company has reported experiencing targeted cyberattacks publicly.

Neither South Port NZ company nor Kuehne+Nagel company has reported experiencing or disclosing vulnerabilities publicly.

Neither South Port NZ nor Kuehne+Nagel holds any compliance certifications.

Neither company holds any compliance certifications.

Neither South Port NZ company nor Kuehne+Nagel company has publicly disclosed detailed information about the number of their subsidiaries.

Kuehne+Nagel company employs more people globally than South Port NZ company, reflecting its scale as a Transportation, Logistics, Supply Chain and Storage.

Neither South Port NZ nor Kuehne+Nagel holds SOC 2 Type 1 certification.

Neither South Port NZ nor Kuehne+Nagel holds SOC 2 Type 2 certification.

Neither South Port NZ nor Kuehne+Nagel holds ISO 27001 certification.

Neither South Port NZ nor Kuehne+Nagel holds PCI DSS certification.

Neither South Port NZ nor Kuehne+Nagel holds HIPAA certification.

Neither South Port NZ nor Kuehne+Nagel 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