Digital Watermarking for Automated Vishing Prevention

A computing platform may generate a digital watermark configured to verify an identity of an initiator of a communication session. The computing platform may send, to a first user device, a digital watermark signal, where the digital watermark signal indicates: a validated digital watermark comprising the digital watermark, and a first frequency at which the digital watermark is embedded. The computing platform may embed, into a request to initiate a communication session, the digital watermark. The computing platform may send, to the first user device, the request to initiate the communication session, where the first user device may be configured to: 1) identify, based on the first frequency, the digital watermark, 2) compare the digital watermark to the validated digital watermark, and 3) based on identifying that the digital watermark matches the validated digital watermark, output an authenticated communication session notification.

BACKGROUND

In some instances, enterprise organizations, such as financial institutions, merchants, service providers, and/or other enterprises, may provide service to their customers and/or clients. In some instances, these services may be provided through voice communication between individuals (e.g., customer service calls, or the like). Such communication may include confidential information, personal identifiable information, and/or other information that may be private to an individual on the call (e.g., a client, or the like). As lifelike chatbots, deepfakes, and/or other voice simulators become more prevalent and accurate, they may augment the problem of automated vishing. For example, such impersonation/simulation may result in the unintended sharing of private and/or other confidential information with unauthorized parties. Accordingly, it may be important to provide enhanced security mechanisms to detect and/or otherwise prevent vishing attacks.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, and convenient technical solutions that address and overcome the technical problems associated with authentication and impersonation detection. In one or more instances, a computing platform having at least one processor, a communication interface, and memory may generate a digital watermark configured to verify an identity of an initiator of a communication session. The computing platform may send, to a first user device, a digital watermark signal, which may indicate a validated digital watermark comprising the digital watermark, and a first frequency at which the digital watermark is embedded. The computing platform may embed, into a request to initiate a communication session, the digital watermark. The computing platform may send, to the first user device, the request to initiate the communication session, where the first user device may be configured to: identify, based on the first frequency, the digital watermark, compare the digital watermark to the validated digital watermark, and based on identifying that the digital watermark matches the validated digital watermark, output an authenticated communication session notification.

In one or more instances, the digital watermark may be one or more of: an audio signal, a number, or a hash value. In one or more instances, the digital watermark may be specific to a user of the first user device.

In one or more examples, the digital watermark may have a predetermined time to live (TTL). In one or more examples, the digital watermark may be configured for one time use.

In one or more instances, the digital watermark signal may further include a frequency band of the first frequency. In one or more instances, sending the request to initiate the communication session may include sending, via a plurality of intervening waypoints, the request to initiate the communication session, where a frequency at which the digital watermark is embedded may be modified at one or more of the plurality of intervening waypoints, and where the first frequency may correspond to a frequency at which the digital watermark is embedded at a final waypoint of the plurality of intervening waypoints.

In one or more examples, embedding the digital watermark may include embedding the digital watermark at the first frequency. In one or more examples, embedding the digital watermark may include embedding a first portion of the digital watermark at the first frequency and a second portion of the digital watermark at a second frequency, where the digital watermark signal further may include the second frequency.

In one or more instances, sending the request to initiate the communication session may include sending a first portion of the digital watermark at a first time and a second portion of the digital watermark at a second time, where the first user device may be configured to assemble the digital watermark, using the first portion of the digital watermark and the second portion of the digital watermark, once both portions of the digital watermark are received. In one or more instances, identifying the digital watermark may include performing frequency modulation at the first frequency and within a frequency band corresponding to the first frequency to detect the digital watermark.

In one or more examples, the computing platform may generate, after sending the request to initiate the communication session, a second digital watermark. The computing platform may replace the digital watermark with the second digital watermark.

In one or more instances, the first user device may be configured to: 1) receive, from a second user device, a request to initiate a second communication session, 2) identify that the request to initiate the second communication session does not include the digital watermark, and 3) based on identifying that the request to initiate the second communication session does not include the digital watermark, trigger presentation of an unauthenticated communication session notification. In one or more instances, triggering presentation of the unauthenticated communication notification may include triggering the first user device to perform one or more of: initiate haptic feedback, or modify a color of a display screen of the first user device. These features, along with many others, are discussed in greater detail below.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown, by way of illustration, various embodiments in which aspects of the disclosure may be practiced. In some instances, other embodiments may be utilized, and structural and functional modifications may be made, without departing from the scope of the present disclosure.

As a brief introduction of the concepts described in further detail below, systems and methods for embedding digital watermarks for automated vishing prevention are described herein. For example, digital audio watermarks may be embedded within voice calls. These watermarks may be created by high frequency signals (e.g., 30-50 KHz, or the like), that may be transmitted through regular land networks, mobile networks, or the like, but might not be perceptible to human ears. These watermarks may be created by a pattern of such frequencies, and may be recognized by using digital signal processing at the receiving end, by a phone company, or the like. In some instances, conversations may be end to end encrypted so that some listeners might not be able to determine the watermarks by frequency filtering. In some instances, voice calls lacking a watermark may be automatically blocked. In some instances, the frequencies may hop within the system.

FIGS.1A-1Bdepict an illustrative computing environment for embedding digital watermarks for automated vishing prevention in accordance with one or more example embodiments. Referring toFIG.1A, computing environment100may include one or more computer systems. For example, computing environment100may include digital watermarking platform102, first user device103, and second user device104.

As described further below, digital watermarking platform102may be a computer system that includes one or more computing devices (e.g., servers, server blades, or the like) and/or other computer components (e.g., processors, memories, communication interfaces) that may be used to provide automated vishing prevention services. For example, digital watermarking platform102may be configured to generate and embed digital watermarks into voice communication requests/sessions, which may be used to validate an identity of a caller.

First user device103may be and/or otherwise include a laptop computer, desktop computer, mobile device, tablet, smartphone, and/or other device that may be used by an individual (such as a client/customer of an enterprise organization). In some instances, the first user device103may be configured with an application (e.g., corresponding to the enterprise organization, or another enterprise organization), which may be configured to verify digital watermarks in received communication requests and/or established communication sessions. In some instances, first user device103may be configured to display one or more user interfaces (e.g., authenticated call notifications, unauthenticated call notifications, or the like).

Second user device104may be and/or otherwise include a laptop computer, desktop computer, mobile device, tablet, smartphone, and/or other device that may be used by an individual (who, for illustrative purposes, may be using a chatbot, deepfake, and/or otherwise simulating/impersonating a legitimate employee of an enterprise organization).

Although a single digital watermarking platform102and two user devices (first user device103and second user device104) are shown, any number of such devices may be deployed in the systems/methods described below without departing from the scope of the disclosure.

Computing environment100also may include one or more networks, which may interconnect digital watermarking platform102, first user device103, second user device104, or the like. For example, computing environment100may include a network101(which may interconnect, e.g., digital watermarking platform102, first user device103, second user device104, or the like).

In one or more arrangements, digital watermarking platform102, first user device103, second user device104may be any type of computing device capable of sending and/or receiving requests and processing the requests accordingly. For example, digital watermarking platform102, first user device103, second user device104, and/or the other systems included in computing environment100may, in some instances, be and/or include server computers, desktop computers, laptop computers, tablet computers, smart phones, or the like that may include one or more processors, memories, communication interfaces, storage devices, and/or other components. As noted above, and as illustrated in greater detail below, any and/or all of digital watermarking platform102, first user device103, second user device104may, in some instances, be special-purpose computing devices configured to perform specific functions.

Referring toFIG.1B, digital watermarking platform102may include one or more processors111, memory112, and communication interface113. A data bus may interconnect processor111, memory112, and communication interface113. Communication interface113may be a network interface configured to support communication between digital watermarking platform102and one or more networks (e.g., network101, or the like). Memory112may include one or more program modules having instructions that when executed by processor111cause digital watermarking platform102to perform one or more functions described herein and/or one or more databases that may store and/or otherwise maintain information which may be used by such program modules and/or processor111. In some instances, the one or more program modules and/or databases may be stored by and/or maintained in different memory units of digital watermarking platform102and/or by different computing devices that may form and/or otherwise make up digital watermarking platform102. For example, memory112may have, host, store, and/or include digital watermarking module112aand/or digital watermarking database112b.

Digital watermarking module112amay have instructions that direct and/or cause digital watermarking platform102to provide improved vishing prevention techniques, as discussed in greater detail below. Digital watermarking database112bmay store information used by digital watermarking module112aand/or digital watermarking platform102in application of advanced techniques to provide improved vishing prevention services, and/or in performing other functions.

FIGS.2A-2Cdepict an illustrative event sequence for embedding digital watermarks for automated vishing prevention in accordance with one or more example embodiments. Referring toFIG.2A, at step201, the digital watermarking platform102may generate a digital watermark. For example, the digital watermarking platform102may generate an audio signal, numeric value, hash value, and/or other watermark that may be embedded into communication sessions and/or requests to establish such sessions (e.g., at a particular frequency, within a particular frequency band, or the like). In some instances, in generating the digital watermark, the digital watermarking platform102may generate high frequency signals (e.g., 30-50 KHz, or the like), which might not be perceptible to human ears. In some instances, the digital watermarking platform102may generate digital watermarks on a user by user basis, such that a digital watermark transmitted to a first user might not match a digital watermark transmitted to a second user. This may, for example, prevent the use of the digital watermark, received by a malicious user, in deceiving a second user (e.g., by embedding the digital watermark in communications between the malicious user and the second user, or the like). In some instances, the digital watermarking platform102may associate a time to live (TTL) with a digital watermark, which may define a period of time after which the digital watermark expires and may be replaced by a subsequently generated digital watermark. Additionally or alternatively, the digital watermark may be configured for single use, and may expire/be replaced after a single transmission of the digital watermark. In some instances, the digital watermark may be representative of a valid identity of an individual or chatbot of an enterprise organization corresponding to the digital watermarking platform102, or the like (e.g., represent a valid employee or bot identity, or the like).

At step202, the digital watermarking platform102may establish a connection with the first user device103. For example, the digital watermarking platform102may establish a first wireless data connection with the first user device103to link the digital watermarking platform102with the first user device103(e.g., in preparation for sending watermark notification signals and/or otherwise communicating). In some instances, the digital watermarking platform102may identify whether or not a connection is already established with the first user device103. If a connection is already established with the first user device103, the digital watermarking platform102might not re-establish the connection. Otherwise, if a connection is not yet established with the first user device103, the digital watermarking platform102may establish the first wireless data connection as described herein.

At step203, the digital watermarking platform102may send a watermark notification signal to the first user device103. For example, the digital watermarking platform102may send a wake up and/or other signal to the first user device103, which may include a verified version of the digital watermark, a frequency at which the verified version of the digital watermark is embedded, a frequency band of the frequency, and/or other information. In doing so, the digital watermarking platform102may configure an application at the first user device103to identify and validate the digital watermark once received. For example, the digital watermarking platform102may send the watermark notification signal to the first user device103via the communication interface113and while the first wireless data connection is established.

At step204, the first user device103may receive the watermark notification signal sent at step203. For example, the digital watermarking platform102may receive the watermark notification signal while the first wireless data connection is established. In these instances, the first user device103may store information from the watermark notification signal such as a verified version of the digital watermark, a frequency at which the verified version of the digital watermark is embedded, a frequency band of the frequency, and/or other information.

At step205, the digital watermarking platform102may embed a digital watermark into a communication (e.g., requesting to initiate a communication session, as part of an existing communication session, or the like) between the digital watermarking platform102and the first user device103. In some instances, this communication may have originated at another device (e.g., another user device, or the like) and may be routed to the first user device103via the digital watermarking platform102. In some instances, in embedding the digital watermark in the communication, the digital watermarking platform102may embed the digital watermark at a first frequency. In some instances, each time a new or different digital watermark is embedded, it may be embedded the same or a different frequency. In some instances, the digital watermarking platform102may embed the digital watermark using frequency domain multiplexing. For example, the digital watermarking platform102may embed portions of the digital watermark at different frequencies, which may then be re-assembled on the client side. Additionally or alternatively, the digital watermarking platform102may embed the digital watermark using time domain multiplexing. For example, the digital watermarking platform102may embed portions of the digital watermark for communication to the first user device103at different times, which may then be re-assembled on the client side.

Referring toFIG.2B, at step206, once the digital watermark is embedded into the request for the communication session (or the communication session itself), the corresponding request/communication may be sent to the first user device103. For example, the corresponding request/communication including the embedded digital watermark may be sent to the first user device103via the communication interface113and while the first wireless data connection is established. In some instances, as described above at step205, the digital watermark may be sent using time and/or frequency domain multiplexing. In some instances, the digital watermark may be sent along a path to the first user device103that includes one or more intervening waypoints. In these instances, at least one of these intervening waypoints may modify the digital watermark, a frequency at which the digital watermark is embedded, modify the time and/or frequency domain multiplexing, and/or perform other actions with regard to the digital watermark. In such instances, these modifications may be previously known to the digital watermarking platform102, and the digital watermarking platform102may have included information of such modifications in the watermark notification signal sent at step203. Accordingly, the first user device103may be informed of a final digital watermark and/or location thereof (e.g., as transmitted to the first user device103by a final waypoint), despite the final digital watermark and/or location thereof being different than the digital watermark embedded at step205and/or the corresponding location. This may, e.g., enable the first user device103to access the digital watermark despite any modifications. In some instances, rather than communicating these modifications using the watermark notification signal sent at step203, the modifications may be communicated to the first user device103by the waypoints themselves. In some instances, the digital watermarking platform102may send the digital watermark to the first user device103via the communication interface113and while the first wireless data connection is established. In some instances, in sending the digital watermark, the digital watermarking platform102may encrypt the digital watermark for enhanced security.

At step207, the first user device103may receive and extract the digital watermark. For example, the first user device103may access a location of the digital watermark (e.g., a single frequency, multiple frequencies, multiple times, and/or other information), which may e.g., be stored at the first user device103based on the watermark notification signal and/or other signals from intervening waypoints. For any identified frequencies, the first user device103may perform frequency modulation within a frequency band corresponding to the identified frequencies to identify and subsequently extract the corresponding digital watermark (or a portion thereof). In instances where the digital watermark is distributed across the frequency and/or time domain, the first user device103may assemble the digital watermark accordingly. In instances where the digital watermark was encrypted by the digital watermarking platform102, the first user device103may decrypt the digital watermark accordingly.

At step208, the first user device103may compare the extracted and/or otherwise assembled digital watermark to the verified digital watermark received in the watermark notification signal. If the first user device103identifies that the extracted digital watermark matches the verified digital watermark, the first user device103may proceed to step209. Otherwise, if the first user device103identifies that the extracted digital watermark does not match the verified digital watermark, the first user device103may proceed to step213

At step209, based on identifying that the extracted digital watermark matches the verified digital watermark, the first user device103may present an authenticated call notification. For example, the first user device103may cause display of a graphical user interface similar to graphical user interface505, which is illustrated inFIG.5. Additionally or alternatively, the identification that the extracted digital watermark matches the verified digital watermark may trigger the first user device103to modify a color of its interface (e.g., change to green, or the like), present haptic feedback, and/or otherwise indicate that the requested communication is authenticated.

While steps201-209refer to communications intercepted by and/or otherwise routed through the digital watermarking platform102, steps210-213refer to communications between user devices that might not be intercepted by and/or otherwise routed through the digital watermarking platform102, and thus might not include the watermark described above.

At step210, the second user device104may establish a connection with the first user device103. For example, the second user device104may establish a second wireless data connection with the first user device103to link the second user device104with the first user device103(e.g., in preparation for initiating communications). In some instances, the second user device104may identify whether a connection is already established with the first user device103.

If a connection is already established with the first user device103, the second user device104might not re-establish the connection. Otherwise, if a connection is not yet established with the first user device103, the second user device104may establish the second wireless data connection as described herein.

Referring toFIG.2C, at step211, the second user device104may send a request to initiate a communication session with the first user device103. For example, the second user device104may send the request to initiate the communication session while the second wireless data connection is established.

At step212, the first user device103may fail to validate any digital watermark. For example, the first user device103may fail to identify the digital watermark because it might not have been instructed (e.g., by the digital watermarking platform102) on where to find the digital watermark (e.g., at what frequency or the like). Additionally or alternatively, because the request to initiate the communication session was not routed through the digital watermarking platform102, no digital watermark may have even been embedded into the request. In some instances, the first user device103may attempt to identify and/or otherwise validate a digital watermark in response to detecting language associated with activities of the digital watermarking platform102(e.g., language related to finance, banking, or the like).

At step213, based on a failure to identify and/or otherwise validate a digital watermark, the first user device103may present an unauthenticated call notification. For example, the first user device103may cause display of a graphical user interface similar to graphical user interface605, which is illustrated inFIG.6. Additionally or alternatively, the failure to identify and/or otherwise validate the digital watermark may trigger the first user device103to modify a color of its interface (e.g., change to red, or the like), present haptic feedback, and/or otherwise indicate that the requested communication is not authenticated. In some instances, the first user device103may additionally or alternatively automatically block the request for the communication session.

Although steps201-213describe the use of the digital watermarking on behalf of a particular enterprise, such techniques may be applied on behalf of any number of enterprises and/or individuals who may opt in to a watermarking service without departing from the scope of the disclosure.

FIG.3depicts an illustrative method for embedding digital watermarks for automated vishing prevention in accordance with one or more example embodiments. At step305, a computing platform having at least one processor, a communication interface, and memory may generate a digital watermark configured to validate an identity of a call initiator. At step310, the computing platform may send a watermark notification signal, including a verified version of the digital watermark and a frequency at which the digital watermark will be embedded in a communication session and/or request, to a user device of a call recipient. At step315, the computing platform may embed, into the communication session and/or request, the digital watermark, and may establish the session and/or send the request accordingly.

FIG.4depicts an illustrative method for embedding digital watermarks for automated vishing prevention in accordance with one or more example embodiments. At step405, a computing device having at least one processor, a communication interface, and memory may receive a watermark notification signal. For example, the computing device may receive the watermark notification signal from a digital watermarking platform associated with validating call initiators. At step410, the computing device may detect a communication request. As shown, in some instances, the computing device may receive a watermark notification signal in advance of the communication request. However, in other instances, the computing device might not receive such a signal. For example, in some instances, a user device and/or other device operated by an impersonator, implementing a deepfake, implementing a fraudulent chatbot, and/or otherwise may send the communication request, and accordingly, a watermark notification signal might not be received, as a watermark might not be embedded in the communication request. At step415, the computing device may attempt to verify the digital watermark. If the computing device successfully verifies the digital watermark, the computing device may proceed to step420. At step420, the computing device may present an authorized communication notification.

Returning to step415, if the computing device is unable to verify and/or otherwise identify the digital watermark, the computing device may proceed to step425. At step425, the computing device may present an unauthorized communication notification.