Comparison Overview

Klaviyo

VS

RR Donnelley

Klaviyo

125 Summer St, Floor 7, Boston, Massachusetts, US, 02110
Last Update: 2025-12-18

Klaviyo (NYSE: KVYO) is the B2C CRM. Powered by its built-in data platform and AI, Klaviyo combines marketing automation, analytics, and customer service into one unified solution, making it easy for businesses to know their customers and grow faster. Klaviyo (CLAY-vee-oh) helps over 176,000 brands like Mattel, Glossier, Daily Harvest, and Liquid Death deliver 1:1 experiences at scale, improve efficiency, and drive revenue.

NAICS: 5418
NAICS Definition: Advertising, Public Relations, and Related Services
Employees: 2,869
Subsidiaries: 1
12-month incidents
0
Known data breaches
1
Attack type number
1

RR Donnelley

227 W Monroe St, Suite 500, Chicago, Illinois, US, 60606
Last Update: 2025-12-19
Between 700 and 749

RRD provides a complete portfolio of marketing, packaging, print and business services to the world’s most respected brands, including 91% of the Fortune 100. Our proprietary technology, advanced data analytics and established expertise fuel organizational decision-making, from strategy through execution. With operations in 30 countries, global organizations and regulated industries trust RRD to reduce complexity and drive audience connections across the entire customer journey.

NAICS: 5418
NAICS Definition: Advertising, Public Relations, and Related Services
Employees: 39,291
Subsidiaries: 8
12-month incidents
0
Known data breaches
2
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/klaviyo.jpeg
Klaviyo
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/rr-donnelley.jpeg
RR Donnelley
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
Klaviyo
100%
Compliance Rate
0/4 Standards Verified
RR Donnelley
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Marketing Services Industry Average (This Year)

No incidents recorded for Klaviyo in 2025.

Incidents vs Marketing Services Industry Average (This Year)

No incidents recorded for RR Donnelley in 2025.

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

Klaviyo cyber incidents detection timeline including parent company and subsidiaries

Incident History — RR Donnelley (X = Date, Y = Severity)

RR Donnelley cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/klaviyo.jpeg
Klaviyo
Incidents

Date Detected: 8/2022
Type:Breach
Attack Vector: Phishing
Blog: Blog
https://images.rankiteo.com/companyimages/rr-donnelley.jpeg
RR Donnelley
Incidents

Date Detected: 11/2021
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 12/2020
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

Date Detected: 10/2020
Type:Breach
Blog: Blog

FAQ

Klaviyo company demonstrates a stronger AI Cybersecurity Score compared to RR Donnelley company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

RR Donnelley company has faced a higher number of disclosed cyber incidents historically compared to Klaviyo company.

In the current year, RR Donnelley company and Klaviyo company have not reported any cyber incidents.

RR Donnelley company has confirmed experiencing a ransomware attack, while Klaviyo company has not reported such incidents publicly.

Both RR Donnelley company and Klaviyo company have disclosed experiencing at least one data breach.

Neither RR Donnelley company nor Klaviyo company has reported experiencing targeted cyberattacks publicly.

Neither Klaviyo company nor RR Donnelley company has reported experiencing or disclosing vulnerabilities publicly.

Neither Klaviyo nor RR Donnelley holds any compliance certifications.

Neither company holds any compliance certifications.

RR Donnelley company has more subsidiaries worldwide compared to Klaviyo company.

RR Donnelley company employs more people globally than Klaviyo company, reflecting its scale as a Marketing Services.

Neither Klaviyo nor RR Donnelley holds SOC 2 Type 1 certification.

Neither Klaviyo nor RR Donnelley holds SOC 2 Type 2 certification.

Neither Klaviyo nor RR Donnelley holds ISO 27001 certification.

Neither Klaviyo nor RR Donnelley holds PCI DSS certification.

Neither Klaviyo nor RR Donnelley holds HIPAA certification.

Neither Klaviyo nor RR Donnelley holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

Risk Information
cvss3
Base: 9.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N