Comparison Overview

ASSA ABLOY Group

VS

Owens Corning

ASSA ABLOY Group

Klarabergsviadukten 90, Stockholm, undefined, SE-10723, SE
Last Update: 2025-11-23

Let’s create a safer and more open world – together! ASSA ABLOY is the global leader in access solutions with sales of SEK 150 billion and 63,000 employees. The Group has operations in over 70 countries and sales worldwide. ASSA ABLOY’s innovations enable safe, secure and convenient access to physical and digital places. Every day, we help billions of people experience a more open world. We have a feeling of discovery and urge to innovate by working together and telling it like it is, enabling us to be always growing, never boring and leading right. Do you want to be encouraged to act, have responsibilities to grow with and opportunities to explore? Join us!

NAICS: 4233
NAICS Definition: Lumber and Other Construction Materials Merchant Wholesalers
Employees: 10,752
Subsidiaries: 27
12-month incidents
0
Known data breaches
0
Attack type number
0

Owens Corning

World Headquarters, Toledo, 43659, US
Last Update: 2025-11-21
Between 750 and 799

Owens Corning is a building products leader committed to building a sustainable future through material innovation. Our products provide durable, sustainable, energy-efficient solutions that leverage our unique capabilities and market-leading positions to help our customers win and grow. We are global in scope, human in scale with more than 25,000 employees in 31 countries dedicated to generating value for our customers and shareholders and making a difference in the communities where we work and live. Founded in 1938 and based in Toledo, Ohio, USA, Owens Corning posted 2024 sales of $11.0 billion. For more information, visit www.owenscorning.com.

NAICS: 4233
NAICS Definition: Lumber and Other Construction Materials Merchant Wholesalers
Employees: 11,180
Subsidiaries: 8
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/assaabloy.jpeg
ASSA ABLOY Group
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/owens-corning.jpeg
Owens Corning
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
ASSA ABLOY Group
100%
Compliance Rate
0/4 Standards Verified
Owens Corning
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Wholesale Building Materials Industry Average (This Year)

No incidents recorded for ASSA ABLOY Group in 2025.

Incidents vs Wholesale Building Materials Industry Average (This Year)

No incidents recorded for Owens Corning in 2025.

Incident History — ASSA ABLOY Group (X = Date, Y = Severity)

ASSA ABLOY Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — Owens Corning (X = Date, Y = Severity)

Owens Corning cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/assaabloy.jpeg
ASSA ABLOY Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/owens-corning.jpeg
Owens Corning
Incidents

No Incident

FAQ

ASSA ABLOY Group company demonstrates a stronger AI Cybersecurity Score compared to Owens Corning company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Owens Corning company has disclosed a higher number of cyber incidents compared to ASSA ABLOY Group company.

In the current year, Owens Corning company and ASSA ABLOY Group company have not reported any cyber incidents.

Neither Owens Corning company nor ASSA ABLOY Group company has reported experiencing a ransomware attack publicly.

Neither Owens Corning company nor ASSA ABLOY Group company has reported experiencing a data breach publicly.

Neither Owens Corning company nor ASSA ABLOY Group company has reported experiencing targeted cyberattacks publicly.

Neither ASSA ABLOY Group company nor Owens Corning company has reported experiencing or disclosing vulnerabilities publicly.

Neither ASSA ABLOY Group nor Owens Corning holds any compliance certifications.

Neither company holds any compliance certifications.

ASSA ABLOY Group company has more subsidiaries worldwide compared to Owens Corning company.

Owens Corning company employs more people globally than ASSA ABLOY Group company, reflecting its scale as a Wholesale Building Materials.

Neither ASSA ABLOY Group nor Owens Corning holds SOC 2 Type 1 certification.

Neither ASSA ABLOY Group nor Owens Corning holds SOC 2 Type 2 certification.

Neither ASSA ABLOY Group nor Owens Corning holds ISO 27001 certification.

Neither ASSA ABLOY Group nor Owens Corning holds PCI DSS certification.

Neither ASSA ABLOY Group nor Owens Corning holds HIPAA certification.

Neither ASSA ABLOY Group nor Owens Corning 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