Comparison Overview

VivoSecurity Inc.

VS

Capgemini

VivoSecurity Inc.

1247 Russell Ave, Los Altos, 94024, US
Last Update: 2025-12-11
View Profile
Between 550 and 599
http://VivoSecurity.com

VivoSecurity develops rigorous statistical and AI models, that meet the Federal Reserves and office of the controller guidance for model risk management (SR11-7), to forecast the cost and probability of data breach. The vivo team has PhD level scientists and statisticians who have developed novel, yet rigorous methods to leverage from the numerous state and federal reporting requirements regarding data breach.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 2
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1
View Profile

Capgemini

Place de l'Étoile, Paris, France, 75017, FR
Last Update: 2025-12-09
Between 750 and 799
https://www.capgemini.com

Capgemini is a global business and technology transformation partner, helping organizations to accelerate their dual transition to a digital and sustainable world, while creating tangible impact for enterprises and society. It is a responsible and diverse group of 340,000 team members in more than 50 countries. With its strong over 55-year heritage, Capgemini is trusted by its clients to unlock the value of technology to address the entire breadth of their business needs. It delivers end-to-end services and solutions leveraging strengths from strategy and design to engineering, all fueled by its market leading capabilities in AI, cloud and data, combined with its deep industry expertise and partner ecosystem. The Group reported 2023 global revenues of €22.5 billion. Get The Future You Want | www.capgemini.com

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 307,934
Subsidiaries: 37
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/vivosecurity-inc-.jpeg
VivoSecurity Inc.
—
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/capgemini.jpeg
Capgemini
—
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
VivoSecurity Inc.
100%
Compliance Rate
0/4 Standards Verified
Capgemini
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs IT Services and IT Consulting Industry Average (This Year)

VivoSecurity Inc. has 36.99% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for Capgemini in 2025.

Incident History — VivoSecurity Inc. (X = Date, Y = Severity)

VivoSecurity Inc. cyber incidents detection timeline including parent company and subsidiaries

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

Capgemini cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/vivosecurity-inc-.jpeg
VivoSecurity Inc.
Incidents

Date Detected: 12/2025
Type:Breach
Attack Vector: Exploiting vulnerabilities in security frameworks
Motivation: Financial gain (selling data on dark web)
Blog: Blog
https://images.rankiteo.com/companyimages/capgemini.jpeg
Capgemini
Incidents

No Incident

FAQ

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

VivoSecurity Inc. company has historically faced a number of disclosed cyber incidents, whereas Capgemini company has not reported any.

In the current year, VivoSecurity Inc. company has reported more cyber incidents than Capgemini company.

Neither Capgemini company nor VivoSecurity Inc. company has reported experiencing a ransomware attack publicly.

VivoSecurity Inc. company has disclosed at least one data breach, while the other Capgemini company has not reported such incidents publicly.

Neither Capgemini company nor VivoSecurity Inc. company has reported experiencing targeted cyberattacks publicly.

Neither VivoSecurity Inc. company nor Capgemini company has reported experiencing or disclosing vulnerabilities publicly.

Neither VivoSecurity Inc. nor Capgemini holds any compliance certifications.

Neither company holds any compliance certifications.

Capgemini company has more subsidiaries worldwide compared to VivoSecurity Inc. company.

Capgemini company employs more people globally than VivoSecurity Inc. company, reflecting its scale as a IT Services and IT Consulting.

Neither VivoSecurity Inc. nor Capgemini holds SOC 2 Type 1 certification.

Neither VivoSecurity Inc. nor Capgemini holds SOC 2 Type 2 certification.

Neither VivoSecurity Inc. nor Capgemini holds ISO 27001 certification.

Neither VivoSecurity Inc. nor Capgemini holds PCI DSS certification.

Neither VivoSecurity Inc. nor Capgemini holds HIPAA certification.

Neither VivoSecurity Inc. nor Capgemini 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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
Description

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

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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."

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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).

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References