Comparison Overview

Standup

VS

iFood

Standup

Houston, Texas 77046, US
Last Update: 2025-05-01 (UTC)
Between 800 and 900

Strong

Standup automates federal revenue growth for government contractors.

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

iFood

Avenida dos Autonomistas, Osasco, São Paulo, 06020-010, BR
Last Update: 2025-03-04 (UTC)

Strong

O iFood é uma empresa brasileira de tecnologia, que aproxima clientes, restaurantes e entregadores de forma simples e prática. O iFood tem o propósito de alimentar o futuro do Brasil e do mundo, transformando a sociedade por meio da educação e da tecnologia, da segurança alimentar, da inclusão e com um impacto socioambiental positivo. Com mais de 80 milhões de pedidos mensais, o iFood atua com inteligência de negócio e soluções de gestão para promover e desenvolver um ecossistema de mais de 330 mil estabelecimentos cadastrados, 250 mil entregadores conectados em mais de 1700 cidades em todo o Brasil. Há 12 anos no mercado, a empresa vai além do food delivery e cresce também em negócios de Mercado, iFood Pago, unindo tecnologia e conveniência na entrega de soluções aos parceiros. Para mais informações sobre o iFood, suas novidades e a nossa fome de alimentar o mundo, acesse: https://www.news.ifood.com.br/

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 19,092
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/standup.jpeg
Standup
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/ifood-.jpeg
iFood
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
Compliance Summary
Standup
100%
Compliance Rate
0/4 Standards Verified
iFood
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Standup in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for iFood in 2025.

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

Standup cyber incidents detection timeline including parent company and subsidiaries

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

iFood cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/standup.jpeg
Standup
Incidents

No Incident

https://images.rankiteo.com/companyimages/ifood-.jpeg
iFood
Incidents

No Incident

FAQ

Both Standup company and iFood company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Historically, iFood company has disclosed a higher number of cyber incidents compared to Standup company.

In the current year, iFood company and Standup company have not reported any cyber incidents.

Neither iFood company nor Standup company has reported experiencing a ransomware attack publicly.

Neither iFood company nor Standup company has reported experiencing a data breach publicly.

Neither iFood company nor Standup company has reported experiencing targeted cyberattacks publicly.

Neither Standup company nor iFood company has reported experiencing or disclosing vulnerabilities publicly.

iFood company has more subsidiaries worldwide compared to Standup company.

iFood company employs more people globally than Standup company, reflecting its scale as a Software Development.

Latest Global CVEs (Not Company-Specific)

Description

Quadient DS-700 iQ devices through 2025-09-30 might have a race condition during the quick clicking of (in order) the Question Mark button, the Help Button, the About button, and the Help Button, leading to a transition out of kiosk mode into local administrative access. NOTE: the reporter indicates that the "behavior was observed sporadically" during "limited time on the client site," making it not "possible to gain more information about the specific kiosk mode crashing issue," and the only conclusion was "there appears to be some form of race condition." Accordingly, there can be doubt that a reproducible cybersecurity vulnerability was identified; sporadic software crashes can also be caused by a hardware fault on a single device (for example, transient RAM errors). The reporter also describes a variety of other issues, including initial access via USB because of the absence of a "lock-pick resistant locking solution for the External Controller PC cabinet," which is not a cybersecurity vulnerability (section 4.1.5 of the CNA Operational Rules). Finally, it is unclear whether the device or OS configuration was inappropriate, given that the risks are typically limited to insider threats within the mail operations room of a large company.

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

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions between 2.1.0 and 2.14.19, 3.2.0-rc1, 3.1.0-rc1 through 3.1.7, and 3.0.0-rc1 through 3.0.18 contain a race condition in the repository credentials handler that can cause the Argo CD server to panic and crash when concurrent operations are performed on the same repository URL. The vulnerability is located in numerous repository related handlers in the util/db/repository_secrets.go file. A valid API token with repositories resource permissions (create, update, or delete actions) is required to trigger the race condition. This vulnerability causes the entire Argo CD server to crash and become unavailable. Attackers can repeatedly and continuously trigger the race condition to maintain a denial-of-service state, disrupting all GitOps operations. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.

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

Stored cross-site scripting (XSS) vulnerabilities in Web Content translation in Liferay Portal 7.4.0 through 7.4.3.112, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions allow remote attackers to inject arbitrary web script or HTML via any rich text field in a web content article.

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

Keysight Ixia Vision has an issue with hardcoded cryptographic material which may allow an attacker to intercept or decrypt payloads sent to the device via API calls or user authentication if the end user does not replace the TLS certificate that shipped with the device. Remediation is available in Version 6.9.1, released on September 23, 2025.

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
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/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 Insecure Direct Object Reference (IDOR) in the /dashboard/notes endpoint of Syaqui Collegetivity v1.0.0 allows attackers to impersonate other users and perform arbitrary operations via a crafted POST request.