Abstract: Methods for securing an electronic communication is provided. Methods may, in a registration process, create and/or select an anti-phish, personalized, security token for a predetermined account on a computing device. Methods may generate a hash of the token, store the token and the hash in a secure storage location within the computing device. Methods may, in an in-use process, generate an electronic communication at a channel. The database may be interposed along the channel. Methods may forward the communication to a recipient associated with the account. Methods may intercept the communication at the database. Methods may select the hash from the database. Methods may generate an injected hash by injecting the hash into the communication. Methods may transmit the communication with the hash to the recipient. Methods may receive the electronic communication with the injected hash at the recipient. Methods may compare the injected hash to the stored hash.

Abstract: Methods for securing an electronic communication is provided. Methods may include, in a registration process, creating and/or selecting an anti-phish, personalized, security token for a predetermined account. Methods may include, in the registration process, storing the token in a database. Methods may include, in an in-use process, generating an electronic communication at a channel. The database may be interposed along the channel. Methods may include, in the in-use process, forwarding the communication to a recipient. The recipient may be associated with the account. Methods may include, in the in-use process, intercepting the communication at the database. Methods may include, in the in-use process, selecting, from the database, the anti-phish, personalized, security token that is associated with the account. Methods may include, in the in-use process, injecting the selected token into the communication.

Abstract: A double anti-phish, personalized, security token for use with electronic communications is provided. The security token may be embedded in each electronic communication transmitted from an entity to a recipient. A first part of the token may be embedded in a body of the communication. A second part of the token may be embedded in a header of the communication. The second part of the security token may validate that the electronic communication is indeed from the entity. Upon validation, the second part may instruct the first part to display a validation symbol. Upon failure to validate, the second part may instruct the first part to display an alert symbol. The recipient receiving the electronic communication may use the first part of the validation symbol as a visual aid to determine a level of confidence of whether the electronic communication has been validated as being transmitted by the entity.

Abstract: Apparatus, methods and systems for voice surveillance using enhanced metadata and geotagging capabilities are provided. Systems may monitor communications being transmitted from, and being received at, entity devices. The communications may be monitored for anomalies. The anomalies may be identified as communications outside of a regular pattern of communications. Various factors may be used to identify the anomalous communications. The factors may include a number of communications per predetermined time period, a geolocation of the communication, identification of a second communicative party of the communication and any other suitable factors. Stakeholders may be alerted regarding any anomalous communications. Additionally, once the communications have been labeled as anomalous or non-anomalous, the labeled communications may be used to create and/or update a set of labeled training data.

Abstract: Methods for securing an electronic communication is provided. Methods may include, in a registration process, creating and/or selecting an anti-phish, personalized, security token for a predetermined avatar. Methods may include, in the registration process, storing the token in a database. Methods may include, in an in-use process, generating an electronic communication at a virtual kiosk in a metaverse. Methods may include, in the in-use process, forwarding an electronic communication from the virtual kiosk to the avatar. The avatar may be associated with the account. Methods may include, in the in-use process, intercepting the communication at an edge interface. Methods may include, in the in-use process, selecting, from the database, the anti-phish, personalized, security token that is associated with the account. Methods may include, in the in-use process, injecting the selected token into the communication.

Abstract: Methods for securing an electronic communication is provided. In a registration process, an anti-phish, personalized, security token may be created and/or selected for a predetermined account. The token may be stored in a database at an enterprise location. An electronic communication may be generated at a third-party location on behalf of the enterprise. The communication may be forwarded from the third-party location to a recipient associated with the account. The communication may be intercepted at an edge server. The edge server may be located at the third-party location or the enterprise location. The edge server may be in communication with the database. The edge server may select, from the database, the anti-phish token that is associated with the account. The selected token may be injected into the communication. The communication with the token may be transmitted to the recipient.

Abstract: Methods for securing an electronic communication is provided. Methods may, in a registration process, create and/or select an anti-phish, personalized, security token for a predetermined account on a computing device. Methods may generate a hash of the token, store the token and the hash in a secure storage location within the computing device. Methods may, in an in-use process, generate an electronic communication at a channel. The database may be interposed along the channel. Methods may forward the communication to a recipient associated with the account. Methods may intercept the communication at the database. Methods may select the hash from the database. Methods may generate an injected hash by injecting the hash into the communication. Methods may transmit the communication with the hash to the recipient. Methods may receive the electronic communication with the injected hash at the recipient. Methods may compare the injected hash to the stored hash.

Abstract: Methods for securing an electronic communication is provided. Methods may include, in a registration process, creating and/or selecting an anti-phish, personalized, security token for a predetermined avatar. Methods may include, in the registration process, storing the token in a database. Methods may include, in an in-use process, generating an electronic communication at a virtual kiosk in a metaverse. Methods may include, in the in-use process, forwarding an electronic communication from the virtual kiosk to the avatar. The avatar may be associated with the account. Methods may include, in the in-use process, intercepting the communication at an edge interface. Methods may include, in the in-use process, selecting, from the database, the anti-phish, personalized, security token that is associated with the account. Methods may include, in the in-use process, injecting the selected token into the communication.

Abstract: A double anti-phish, personalized, security token for use with electronic communications is provided. The security token may be embedded in each electronic communication transmitted from an entity to a recipient. A first part of the token may be embedded in a body of the communication. A second part of the token may be embedded in a header of the communication. The second part of the security token may validate that the electronic communication is indeed from the entity. Upon validation, the second part may instruct the first part to display a validation symbol. Upon failure to validate, the second part may instruct the first part to display an alert symbol. The recipient receiving the electronic communication may use the first part of the validation symbol as a visual aid to determine a level of confidence of whether the electronic communication has been validated as being transmitted by the entity.

Abstract: Methods for securing an electronic communication is provided. Methods may include, in a registration process, creating and/or selecting an anti-phish, personalized, security token for a predetermined account. Methods may include, in the registration process, storing the token in a database. Methods may include, in an in-use process, generating an electronic communication at a channel. The database may be interposed along the channel. Methods may include, in the in-use process, forwarding the communication to a recipient. The recipient may be associated with the account. Methods may include, in the in-use process, intercepting the communication at the database. Methods may include, in the in-use process, selecting, from the database, the anti-phish, personalized, security token that is associated with the account. Methods may include, in the in-use process, injecting the selected token into the communication.

Abstract: Methods for increasing a data security of information shared and viewed within a social network platform is provided. Methods may include generating a social media impersonation score (“SMIS”) for a first user account on the social network platform. The SMIS may indicate a veracity of the user profile data associated with the first user account. Methods may include verifying the veracity of the user profile data by determining an authenticity of a corporate email address associated with the first user account. Methods may include determining that the corporate email address exists and verifying that a domain associated with the corporate email address is a trusted domain. Methods may include generating the SMIS based on results of the verifying and linking the SMIS to the first user account. Methods may further include displaying the first user account and the SMIS on a graphical user interface (“GUI”) of the social network platform.