Comparison Overview
Touchstone Wealth
Touchstone Wealth
6263 N Scottsdale Rd, Scottsdale, Arizona, 85250, US
Last Update: 29/04/2026
Touchstone Wealth is a fee-based financial advisory firm that provides guidance to help individuals, families, and businesses reach their goals and live their dreams. With more than 100 employees and advisors licensed in all 50 states, we bring broad and deep professio...
Westpac Group
275 Kent St, Sydney, 2000, AU
Last Update: 31/03/2026
From rescue helicopters to signing the Equator Principles, from paying super during parental leave to adding 'Touch ID' biometric technology to our banking apps and being first on the scene with a helping hand in times of crisis... we have a proud history of stepping u...
Compliance Ranges Comparison
Touchstone Wealth
Westpac Group
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Touchstone Wealth in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Westpac Group in 2026.
Incident History - Touchstone Wealth (X = Date, Y = Severity)
Touchstone Wealth cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Westpac Group (X = Date, Y = Severity)
Westpac Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Touchstone Wealth
Westpac Group
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: *.*.