Comparison Overview

WalkMe™

VS

Pitney Bowes

WalkMe™

71 Stevenson St floor 20, San Francisco, California, 94105, US
Last Update: 2025-05-06 (UTC)
Between 800 and 900

Strong

WalkMe pioneered the Digital Adoption Platform (DAP) to simplify user experiences by combining insights, engagement, guidance and automation capabilities. Founded in 2011, WalkMe’s mission is to make digital adoption for employees and customers simple, while increasing enterprise productivity. Our platform works as an invisible layer of visual cues and personalized content placed on top of your website or enterprise software. WalkMe’s DAP is used by thousands of enterprises worldwide spanning all industries and platforms for onboarding, training new and existing users on new processes, and improving overall productivity by providing contextual guidance in real-time.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 1,117
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Pitney Bowes

3001 Summer Street, None, Stamford, CT, US, 06926
Last Update: 2025-08-21 (UTC)

Strong

Pitney Bowes is a technology-driven products and services company that provides SaaS shipping solutions, mailing innovation, and financial services to clients around the world – including more than 90 percent of the Fortune 500. Small businesses to large enterprises, and government entities rely on Pitney Bowes to reduce the complexity of sending mail and parcels. For additional information, visit Pitney Bowes at www.pitneybowes.com.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 12,875
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/walkme.jpeg
WalkMe™
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/pitney-bowes.jpeg
Pitney Bowes
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
Compliance Summary
WalkMe™
100%
Compliance Rate
0/4 Standards Verified
Pitney Bowes
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for WalkMe™ in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Pitney Bowes in 2025.

Incident History — WalkMe™ (X = Date, Y = Severity)

WalkMe™ cyber incidents detection timeline including parent company and subsidiaries

Incident History — Pitney Bowes (X = Date, Y = Severity)

Pitney Bowes cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/walkme.jpeg
WalkMe™
Incidents

No Incident

https://images.rankiteo.com/companyimages/pitney-bowes.jpeg
Pitney Bowes
Incidents

Date Detected: 05/2020
Type:Ransomware
Motivation: Financial
Blog: Blog

Date Detected: 10/2019
Type:Malware
Blog: Blog

FAQ

Both WalkMe™ company and Pitney Bowes company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Pitney Bowes company has historically faced a number of disclosed cyber incidents, whereas WalkMe™ company has not reported any.

In the current year, Pitney Bowes company and WalkMe™ company have not reported any cyber incidents.

Pitney Bowes company has confirmed experiencing a ransomware attack, while WalkMe™ company has not reported such incidents publicly.

Neither Pitney Bowes company nor WalkMe™ company has reported experiencing a data breach publicly.

Neither Pitney Bowes company nor WalkMe™ company has reported experiencing targeted cyberattacks publicly.

Neither WalkMe™ company nor Pitney Bowes company has reported experiencing or disclosing vulnerabilities publicly.

Pitney Bowes company has more subsidiaries worldwide compared to WalkMe™ company.

Pitney Bowes company employs more people globally than WalkMe™ company, reflecting its scale as a Software Development.

Latest Global CVEs (Not Company-Specific)

Description

Improper Protection Against Voltage and Clock Glitches in FPGA devices, could allow an attacker with physical access to undervolt the platform resulting in a loss of confidentiality.

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

Malicious code was inserted into the Nx (build system) package and several related plugins. The tampered package was published to the npm software registry, via a supply-chain attack. Affected versions contain code that scans the file system, collects credentials, and posts them to GitHub as a repo under user's accounts.

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

Flag Forge is a Capture The Flag (CTF) platform. In versions from 2.1.0 to before 2.3.0, the API endpoint GET /api/problems/:id returns challenge hints in plaintext within the question object, regardless of whether the user has unlocked them via point deduction. Users can view all hints for free, undermining the business logic of the platform and reducing the integrity of the challenge system. This issue has been patched in version 2.3.0.

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

Flag Forge is a Capture The Flag (CTF) platform. In version 2.1.0, the /api/admin/assign-badge endpoint lacks proper access control, allowing any authenticated user to assign high-privilege badges (e.g., Staff) to themselves. This could lead to privilege escalation and impersonation of administrative roles. This issue has been patched in version 2.2.0.

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

parse is a package designed to parse JavaScript SDK. A Prototype Pollution vulnerability in the SingleInstanceStateController.initializeState function of parse version 5.3.0 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.