Comparison Overview

Xylem

VS

Johnson Controls

Xylem

Last Update: 2025-11-20
Between 750 and 799

Xylem is the global leader in advanced technologies, solutions and services that address the world’s biggest water challenges. We enable our customers to dramatically improve the way water and wastewater is used, managed, conserved, re-used and returned to nature. At every level, our global team is committed to access, equity, inclusion, and diversity. Our goal is for all our colleagues to be involved, respected, valued, connected, and free to bring their authentic selves and ideas. If you are excited and passionate about solving water, we want to hear from you. #LetsSolveWater

NAICS: 3332
NAICS Definition: Industrial Machinery Manufacturing
Employees: 15,232
Subsidiaries: 19
12-month incidents
0
Known data breaches
0
Attack type number
0

Johnson Controls

Milwaukee, Cork, Ireland, IE, T12 X8N6
Last Update: 2025-11-21

At Johnson Controls, we transform the environments where people live, work, learn and play. As the global leader in smart, healthy and sustainable buildings, our mission is to reimagine the performance of buildings to serve people, places and the planet. Building on a proud history of 140 years of innovation, we deliver the blueprint of the future for industries such as healthcare, schools, data centers, airports, stadiums, manufacturing and beyond through OpenBlue, our comprehensive digital offering. Today, Johnson Controls offers the world`s largest portfolio of building technology and software as well as service solutions from some of the most trusted names in the industry. Visit www.johnsoncontrols.com for more information.

NAICS: 3332
NAICS Definition: Industrial Machinery Manufacturing
Employees: 65,242
Subsidiaries: 16
12-month incidents
1
Known data breaches
0
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/xylem-inc.jpeg
Xylem
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/johnson-controls.jpeg
Johnson Controls
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
Xylem
100%
Compliance Rate
0/4 Standards Verified
Johnson Controls
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Machinery Manufacturing Industry Average (This Year)

No incidents recorded for Xylem in 2025.

Incidents vs Industrial Machinery Manufacturing Industry Average (This Year)

Johnson Controls has 0.0% fewer incidents than the average of same-industry companies with at least one recorded incident.

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

Xylem cyber incidents detection timeline including parent company and subsidiaries

Incident History — Johnson Controls (X = Date, Y = Severity)

Johnson Controls cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/xylem-inc.jpeg
Xylem
Incidents

No Incident

https://images.rankiteo.com/companyimages/johnson-controls.jpeg
Johnson Controls
Incidents

Date Detected: 6/2025
Type:Vulnerability
Attack Vector: Publicly Accessible Devices, Default Credentials, Unpatched Software Vulnerabilities, Lack of Firewalls/Encryption
Blog: Blog

Date Detected: 09/2023
Type:Cyber Attack
Attack Vector: Denial of Service (DoS)
Blog: Blog

Date Detected: 09/2023
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

FAQ

Xylem company demonstrates a stronger AI Cybersecurity Score compared to Johnson Controls company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Johnson Controls company has historically faced a number of disclosed cyber incidents, whereas Xylem company has not reported any.

In the current year, Johnson Controls company has reported more cyber incidents than Xylem company.

Johnson Controls company has confirmed experiencing a ransomware attack, while Xylem company has not reported such incidents publicly.

Neither Johnson Controls company nor Xylem company has reported experiencing a data breach publicly.

Johnson Controls company has reported targeted cyberattacks, while Xylem company has not reported such incidents publicly.

Johnson Controls company has disclosed at least one vulnerability, while Xylem company has not reported such incidents publicly.

Neither Xylem nor Johnson Controls holds any compliance certifications.

Neither company holds any compliance certifications.

Xylem company has more subsidiaries worldwide compared to Johnson Controls company.

Johnson Controls company employs more people globally than Xylem company, reflecting its scale as a Industrial Machinery Manufacturing.

Neither Xylem nor Johnson Controls holds SOC 2 Type 1 certification.

Neither Xylem nor Johnson Controls holds SOC 2 Type 2 certification.

Neither Xylem nor Johnson Controls holds ISO 27001 certification.

Neither Xylem nor Johnson Controls holds PCI DSS certification.

Neither Xylem nor Johnson Controls holds HIPAA certification.

Neither Xylem nor Johnson Controls 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