Comparison Overview

Amazon Fulfillment Technologies & Robotics

VS

Upwork

Amazon Fulfillment Technologies & Robotics

300 Riverpark Drive, North Reading, MA, US, 01864
Last Update: 2025-12-09

On the Fulfillment Technologies & Robotics Team, we build dynamic partnerships between people and intelligent machines. This intricate collaboration helps Amazon fulfill orders with unmatched accuracy. Since we began working with robotics, we've added over a million new jobs worldwide. Working in symphony with our robotic technology, employees have the opportunity to extend their technical capabilities by working alongside some of the industry’s most advanced technologies. This includes our fleet of autonomous mobile robots, sophisticated control software, and technologies like language perception, machine learning, object recognition, and semantic understanding of commands. These technologies help employees deliver an ever-improving customer and employee experience, as well as improve the safety of our facilities. Explore opportunities across the entire Fulfillment Technologies & Robotics team to find the right fit for you.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 14,418
Subsidiaries: 88
12-month incidents
0
Known data breaches
4
Attack type number
5

Upwork

475 Brannan St, San Francisco, California, 94107, US
Last Update: 2025-12-09
Between 800 and 849

Upwork is the world’s work marketplace that connects businesses with independent talent from across the globe. We serve everyone from one-person startups to large, Fortune 100 enterprises with a powerful, trust-driven platform that enables companies and talent to work together in new ways that unlock their potential. Our talent community on Upwork encompasses more than 10,000 skills in categories including website & app development, creative & design, customer support, finance & accounting, consulting, and operations.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/amazon-fulfillment-technologies-robotics.jpeg
Amazon Fulfillment Technologies & Robotics
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/upwork.jpeg
Upwork
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
Amazon Fulfillment Technologies & Robotics
100%
Compliance Rate
0/4 Standards Verified
Upwork
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Amazon Fulfillment Technologies & Robotics in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Upwork in 2025.

Incident History — Amazon Fulfillment Technologies & Robotics (X = Date, Y = Severity)

Amazon Fulfillment Technologies & Robotics cyber incidents detection timeline including parent company and subsidiaries

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

Upwork cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/amazon-fulfillment-technologies-robotics.jpeg
Amazon Fulfillment Technologies & Robotics
Incidents

Date Detected: 12/2025
Type:Vulnerability
Attack Vector: Remote Code Execution (RCE)
Motivation: State-sponsored cyber operations
Blog: Blog

Date Detected: 10/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 9/2025
Type:Cyber Attack
Attack Vector: Exposed Docker API, Misconfigured AWS EC2 Instances, Python Docker SDK
Motivation: Financial Gain, Disruption, Cybercrime-as-a-Service
Blog: Blog
https://images.rankiteo.com/companyimages/upwork.jpeg
Upwork
Incidents

No Incident

FAQ

Upwork company demonstrates a stronger AI Cybersecurity Score compared to Amazon Fulfillment Technologies & Robotics company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Amazon Fulfillment Technologies & Robotics company has historically faced a number of disclosed cyber incidents, whereas Upwork company has not reported any.

In the current year, Amazon Fulfillment Technologies & Robotics company has reported more cyber incidents than Upwork company.

Amazon Fulfillment Technologies & Robotics company has confirmed experiencing a ransomware attack, while Upwork company has not reported such incidents publicly.

Amazon Fulfillment Technologies & Robotics company has disclosed at least one data breach, while the other Upwork company has not reported such incidents publicly.

Amazon Fulfillment Technologies & Robotics company has reported targeted cyberattacks, while Upwork company has not reported such incidents publicly.

Amazon Fulfillment Technologies & Robotics company has disclosed at least one vulnerability, while Upwork company has not reported such incidents publicly.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds any compliance certifications.

Neither company holds any compliance certifications.

Amazon Fulfillment Technologies & Robotics company has more subsidiaries worldwide compared to Upwork company.

Upwork company employs more people globally than Amazon Fulfillment Technologies & Robotics company, reflecting its scale as a Software Development.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds SOC 2 Type 1 certification.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds SOC 2 Type 2 certification.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds ISO 27001 certification.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds PCI DSS certification.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds HIPAA certification.

Neither Amazon Fulfillment Technologies & Robotics nor Upwork holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N