Comparison Overview
Coutts
Coutts
440 Strand, London, GB
Last Update: 01/12/2025
Coutts has a world-renowned reputation for growth and guidance through personalised private banking and wealth management. We work as our clients’ trusted partners, providing specialist expertise to realise their personal and commercial ambitions in the UK and globally....
VakıfBank
İstanbul, 34415, TR
Last Update: 02/04/2026
1954 yılında, vakıf kaynaklarını ekonomik kalkınmanın gereksinimleri doğrultusunda en iyi biçimde değerlendirmek amacıyla kurulan VakıfBank, o günden bu yana çağdaş bankacılık yöntemleri ve uygulamalarıyla Türkiye’nin tasarruf düzeyinin gelişim sürecine katkıda bulunmak...
Compliance Ranges Comparison
Coutts
VakıfBank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Coutts in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for VakıfBank in 2026.
Incident History - Coutts (X = Date, Y = Severity)
Coutts cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VakıfBank (X = Date, Y = Severity)
VakıfBank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Coutts
VakıfBank
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.