Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
SWIFT Proposes New Measures For Bolstering Its Security
Oldest First  |  Newest First  |  Threaded View
RyanSepe
RyanSepe,
User Rank: Ninja
5/29/2016 | 12:29:56 PM
2FA
At this point in time its astonishing that banks do not incorporate 2FA.
Jdamon
Jdamon,
User Rank: Apprentice
5/30/2016 | 4:12:18 PM
Re: 2FA
Thanks for this interesting point of view about these new measures
dritchie
dritchie,
User Rank: Strategist
5/31/2016 | 9:40:17 AM
Re: 2FA
I believe that the article says that "in addition to 2FA" they are looking at implementing additional safety protocols.  3FA anyone?
RyanSepe
RyanSepe,
User Rank: Ninja
5/31/2016 | 10:44:50 AM
Re: 2FA
Yes, you are correct I misread that line. However, outside of organizations that incorporate SWIFT messages there are many that still use single factor authentication as a security measure for internet facing apps.
Natasha_D_G
Natasha_D_G,
User Rank: Apprentice
5/31/2016 | 2:42:06 PM
Sock draw safer than banks?
It's disturbing that we had to wait for 12 banks to be breached to make changes. As well as it's scary how easy it is to breach our banking systems. With technology we've opened a whole new world of opportunities for citizens but also for cyber criminals. The only way we can counter and mitigate threats on our banking systems and networks as a whole is to know and understand the motivations of threat actors so that we can stay ahead of them. We must stay on the offensive and I hope we rectify these flaws in our cyber security before another spate of attacks.  If not my sock draw is not looking sp bad for my pennies.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-4194
PUBLISHED: 2022-11-30
Use after free in Accessibility in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
CVE-2022-4195
PUBLISHED: 2022-11-30
Insufficient policy enforcement in Safe Browsing in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to bypass Safe Browsing warnings via a malicious file. (Chromium security severity: Medium)
CVE-2022-4175
PUBLISHED: 2022-11-30
Use after free in Camera Capture in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVE-2022-4176
PUBLISHED: 2022-11-30
Out of bounds write in Lacros Graphics in Google Chrome on Chrome OS and Lacros prior to 108.0.5359.71 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via UI interactions. (Chromium security severity: High)
CVE-2022-4177
PUBLISHED: 2022-11-30
Use after free in Extensions in Google Chrome prior to 108.0.5359.71 allowed an attacker who convinced a user to install an extension to potentially exploit heap corruption via a crafted Chrome Extension and UI interaction. (Chromium security severity: High)