Comparison Overview
SEE Digital d.o.o.

SEE Digital d.o.o.
Bulevar Milutina Milankovića 134g, Belgrade, 11070, RS
Last Update: 28/01/2026
SEE Digital was founded as sTECH in 2012. with the aim to become a reliable partner and service provider to UNIQA insurance companies in the region of Southeast Europe. With its’ team, SEE Digital has become a designer and carrier of IT strategy in the region of Southea...

Sogeti
145-151 Quai du Président Roosevelt,, 92 130 Issy-les-Moulineaux , Paris, Paris - Issy-les-Moulineaux, FR, 92130
Last Update: 04/04/2026
Part of the Capgemini Group, Sogeti makes business value through technology for organizations that need to implement innovation at speed and want a local partner with global scale. With a hands-on culture and close proximity to its clients, Sogeti implements solutions t...
Compliance Ranges Comparison

SEE Digital d.o.o.







Sogeti






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for SEE Digital d.o.o. in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Sogeti in 2026.
Incident History - SEE Digital d.o.o. (X = Date, Y = Severity)
SEE Digital d.o.o. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sogeti (X = Date, Y = Severity)
Sogeti cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SEE Digital d.o.o.

Sogeti
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.