Our compliance consultant recently sent out a lengthy notice focusing on the need for enhanced security protocols around outbound cash transfers. From the notice - emphasis in bold is my edit.
SEC Focus on Client Verification and Safeguards: Beyond the inherent risks, how firms are establishing controls and safeguards to protect clients from SI-enabled attacks is a clear SEC Priority. The SEC has stated that examiners will review how firms detect and respond to red flags during account takeovers and fraudulent transfers. They will also assess whether firms are updating their Identity Theft Prevention Program for emerging risks, including SI and stolen credentials. As an example, a cloned voice defeats one of the most common controls in our industry: "I called the client and recognized their voice."
While there are other steps we are have implemented and are adding, verification still ultimately relies on voice verification. Voices can now be cloned, which creates a potential gap. And confirming data like SSN or DOB, while useful, seems insufficient given the amount of personal information that has been compromised over the years. Presently, we have an escalating series of factors we use to review transfers and more closely review those that present potential issues.
We have begun adding a text verification step for any transfer that has these flags (wire, new bank, non standard distribution request, urgency, etc.). However, I would prefer we have an MFA tool to generate the text.
Is anyone using an MFA tool that generates a code to verify that the client you are ostensibly speaking with is real and has their device (phone, tablet) with them?