Comparison Overview

AmpUp

VS

DoorDash

AmpUp

1700 Wyatt Drive, Santa Clara, 95054, US
Last Update: 2026-01-24
Between 650 and 699

AmpUp makes EV charging simple, reliable, and ready wherever your people park. Our platform connects workplaces, communities, fleets, and public sites with charging that’s easy to manage and built to perform. Real-time controls, flexible access options, and 24/7 support come standard. For installers, AmpUp is easy to activate and even easier to oversee—no call centers, no delays. No matter where you’re starting, AmpUp fits right in. Compatible with 15+ trusted hardware brands, our platform makes it easy to launch at one site, or scale across many. ✓ 98.5% session success rate, 99.9% uptime. ✓ Easy activation, remote fixes, and full access control. ✓ Public, private, or paid charging options. ✓ Approved across 50+ utility incentive programs. ✓ We’re hiring! https://ampup.breezy.hr/

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

DoorDash

San Francisco, California, US
Last Update: 2026-01-17

At DoorDash, our mission to empower local economies shapes how our team members move quickly and always learn and reiterate to support merchants, Dashers and the communities we serve. We are a technology and logistics company that started with door-to-door delivery, and we are looking for team members who can help us go from a company that is known for delivering food to a company that people turn to for any and all goods. DoorDash is growing rapidly and changing constantly, which gives our team members the opportunity to share their unique perspectives, solve new challenges, and own their careers. Our leaders seek the truth and welcome big, hairy, audacious questions. We are grounded in our company values, and we make intentional decisions that are both logical and display empathy for our range of users—from Dashers to Merchants to Customers.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ampup-charging.jpeg
AmpUp
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/doordash.jpeg
DoorDash
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
AmpUp
100%
Compliance Rate
0/4 Standards Verified
DoorDash
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for AmpUp in 2026.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for DoorDash in 2026.

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

AmpUp cyber incidents detection timeline including parent company and subsidiaries

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

DoorDash cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ampup-charging.jpeg
AmpUp
Incidents

Date Detected: 10/2025
Type:Breach
Attack Vector: API Key Compromise
Motivation: Financial fraud
Blog: Blog
https://images.rankiteo.com/companyimages/doordash.jpeg
DoorDash
Incidents

Date Detected: 11/2025
Type:Breach
Attack Vector: Third-Party Vendor Compromise, Credential Theft, Social Engineering
Motivation: Data Theft, Potential Fraud Enablement
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Social Engineering (Employee Targeted)
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Social Engineering, Phishing (Spear Phishing/Vishing), Compromised Credentials
Motivation: Data Theft for Follow-on Attacks (e.g., Spear Phishing, Vishing), Potential Financial Gain via Stolen Data
Blog: Blog

FAQ

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

DoorDash company has faced a higher number of disclosed cyber incidents historically compared to AmpUp company.

In the current year, DoorDash company and AmpUp company have not reported any cyber incidents.

Neither DoorDash company nor AmpUp company has reported experiencing a ransomware attack publicly.

Both DoorDash company and AmpUp company have disclosed experiencing at least one data breach.

Neither DoorDash company nor AmpUp company has reported experiencing targeted cyberattacks publicly.

DoorDash company has disclosed at least one vulnerability, while AmpUp company has not reported such incidents publicly.

Neither AmpUp nor DoorDash holds any compliance certifications.

Neither company holds any compliance certifications.

DoorDash company has more subsidiaries worldwide compared to AmpUp company.

DoorDash company employs more people globally than AmpUp company, reflecting its scale as a Software Development.

Neither AmpUp nor DoorDash holds SOC 2 Type 1 certification.

Neither AmpUp nor DoorDash holds SOC 2 Type 2 certification.

Neither AmpUp nor DoorDash holds ISO 27001 certification.

Neither AmpUp nor DoorDash holds PCI DSS certification.

Neither AmpUp nor DoorDash holds HIPAA certification.

Neither AmpUp nor DoorDash holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

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

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.