Comparison Overview
Salesforce Data 360

Salesforce Data 360
N/A
Last Update: 09/03/2026
Data 360 puts all of your data to work for your customers. It is deeply embedded in the Agentforce Action Platform, which means any external data lake or warehouse can now drive actions and workflows inside of your CRM. Data 360 is about more than just bringing data tog...

ByteDance
China, 100098, CN
Last Update: 02/04/2026
ByteDance is a global incubator of platforms at the cutting edge of commerce, content, entertainment and enterprise services - over 2.5bn people interact with ByteDance products including TikTok. Creation is the core of ByteDance's purpose. Our products are built to he...
Compliance Ranges Comparison

Salesforce Data 360







ByteDance






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Salesforce Data 360 in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for ByteDance in 2026.
Incident History - Salesforce Data 360 (X = Date, Y = Severity)
Salesforce Data 360 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ByteDance (X = Date, Y = Severity)
ByteDance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Salesforce Data 360

ByteDance
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.