Comparison Overview
The Piedmont Group
The Piedmont Group
1050 Crown Pointe Parkway, Suite 1800, Atlanta, 30338, US
Last Update: 31/01/2026
At The Piedmont Group, we help you achieve your financial goals. We learn what is important to you, design financial solutions to help get you to where you want to be, and help you implement those strategies. We also keep a watchful eye as life unfolds to help make sure...
Banco Davivienda
Avenida Calle 26 68C-61, Bogota, 110931, CO
Last Update: 02/04/2026
En Davivienda creemos en un mundo financiero sin barreras que facilite la vida a las personas, las empresas, las ciudades y municipios. Por esta razón hoy somos más de 19.000 personas innovando y creando cada día soluciones y ofertas exclusivas para 10 millones de clien...
Compliance Ranges Comparison
The Piedmont Group
Banco Davivienda
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for The Piedmont Group in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Banco Davivienda in 2026.
Incident History - The Piedmont Group (X = Date, Y = Severity)
The Piedmont Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Davivienda (X = Date, Y = Severity)
Banco Davivienda cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The Piedmont Group
Banco Davivienda
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: *.*.