Comparison Overview
Doğuş Teknoloji
Doğuş Teknoloji
Büyükdere Caddesi, Maslak, 34485, TR
Last Update: 10/02/2026
Doğuş Teknoloji, bugün 10’un üzerinde sektörde pek çok firmaya hizmet veren, odağına insanı alan, hızlı, yenilikçi, proaktif ve derin analiz yetkinlikleriyle ihtiyaca özel teknoloji çözümleri sunan bir teknoloji şirketidir. Aynı zamanda Ar-Ge merkezi de bulunan Doğuş Te...
Persistent Systems
Bhageerath, 402 E, Senapati Bapat Road, Pune, Maharashtra, IN, 411016
Last Update: 02/04/2026
We are an AI-led, platform-driven Digital Engineering and Enterprise Modernization partner, combining deep technical expertise and industry experience to help our clients anticipate what’s next. Our offerings and proven solutions create a unique competitive advantage fo...
Compliance Ranges Comparison
Doğuş Teknoloji
Persistent Systems
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Doğuş Teknoloji in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Persistent Systems in 2026.
Incident History - Doğuş Teknoloji (X = Date, Y = Severity)
Doğuş Teknoloji cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Persistent Systems (X = Date, Y = Severity)
Persistent Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Doğuş Teknoloji
Persistent Systems
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.