Abstract: A method may include: receiving a registration of a mobile device for a user; adding the mobile device to a user profile associated with the user; establishing a first trust level based on activity with a mobile application, wherein the first trust level allows the user to execute a first action that requires the first trust level without additional authentication; receiving user identity verification from the mobile application; establishing a second trust level for the first mobile device based on the user identity verification, wherein the second trust level allows the user to execute a second action that requires the second or the first trust level without additional authentication; receiving a removal of the first mobile device from the user profile; and revoking the second trust level and the first trust level from the first mobile device.

Abstract: Methods and systems consistent with the disclosure include a method for secure transfer using digital channels, comprising: receiving, by a platform executed by one or more processors of a server, a notification of a customer call, wherein the notification comprises an incoming phone call from a user; initiating a customer assist instance responsive to the notification; determining whether to ask the user for a document scan based on whether a user's device is known by the platform; sending, based on a determination that authorization is required, an event to the user's device with a unique scan session; receiving a scanned document from a user's device via use of the unique scan session; and determining, based on the scanned document, to allow a transaction.

Abstract: A method may include: receiving, by a backend computer program and from a service provider system, a message for customer; storing, by the backend computer program, the message with a message identifier for the message; marking, by the backend computer program, a customer electronic device associated with the customer to receive the message on a next customer login on the customer electronic device; receiving, by the backend computer program and from a mobile application or a browser executed by the customer electronic device, a login from the customer; authenticating, by the backend computer program, the customer; confirming, by the backend computer program, that the customer electronic device is marked; and providing, by the backend computer program, the message identifier to the mobile application or the browser; wherein the mobile application or the browser may be configured to retrieve the message using the message identifier and to display the message.

Abstract: A method for generating keys in a multi-cloud environment that minimizes the impact of a breach may include: generating and storing a first key encryption key (KEK) in a first environment key management service (KMS); generating a first data encryption key (DEK) using the first KMS; generating a second DEK for a second environment using the first KMS; encrypting the first DEK with the first KEK and the second DEK with the first KEK; storing the encrypted first DEK and the encrypted second DEK in a database; generating a second KEK and storing the second KEK in a second environment KMS; encrypting the first DEK with the second KEK and the second DEK with the second KEK; and storing the encrypted first DEK and the encrypted second DEK in the database.

Abstract: A method for facilitating application authentication bypass based on proximate with time using device authentication is disclosed. The method includes receiving a request from a user to access an application on a user device, the request including an application authentication request; accessing the user device via a device application programming interface; retrieving, via the device application programming interface, device authentication data, the device authentication data including a timeline of successful device authentications; determining whether the device authentication data is within a predetermined threshold; authenticating the request by using the device authentication data when the device authentication data is within the predetermined threshold; and permitting access to the application based on a result of the authenticating.

Abstract: In some aspects, the techniques described herein relate to a method including: receiving, at a threat mitigation platform, payment information from a payment product application; providing the payment information to a threat analysis engine of the threat mitigation platform as input to the threat analysis engine; generating, as output of the threat analysis engine and based on the payment information, a threat identifier; querying, by an authorization engine, a threat repository using the threat identifier as a lookup key; receiving, by the authorization engine and from the threat repository, information associated with the threat identifier; and communicating the information associated with the threat identifier to the payment product application.

Abstract: A method for extended authentication sessions on an electronic device may include an authentication service computer program executed by an authentication service electronic device: receiving a customer identifier for a customer and a unique identifier for a mobile electronic device; authenticating the customer based on the customer identifier and the unique identifier for the mobile electronic device; setting a device cookie that is specific to the mobile electronic device on the mobile electronic device; and providing the device cookie and a client secret to an OAuth services backend, wherein the OAuth services backend validates the customer identifier and client secret and generates a first token and a second token, the first token having an expiration that is shorter than that of the second token. The mobile electronic device is configured to receive and store the first token and the second token.

Abstract: A method for dynamic risk-assessed serialization of user challenges may include a computer program: receiving, from a requesting system, a challenge request for a user action; identifying a first challenge type to present based on the user action; presenting a first challenge for the first challenge type to a user electronic device; receiving, from the user electronic device, a response to the first challenge; verifying the response to the first challenge; determining that a second challenge is necessary based on the response to the first challenge; identifying a second challenge type to present based on the response to the first challenge; presenting a second challenge for the second challenge type to the user electronic device; receiving, from the user electronic device, a response to the second challenge; verifying the response to the second challenge; and returning, to the requesting system, a notification that the challenge request was successful.

Abstract: A method for generating keys in a multi-cloud environment that minimizes the impact of a breach may include: generating and storing a first key encryption key (KEK) in a first environment key management service (KMS); generating a first data encryption key (DEK) using the first KMS; generating a second DEK for a second environment using the first KMS; encrypting the first DEK with the first KEK and the second DEK with the first KEK; storing the encrypted first DEK and the encrypted second DEK in a database; generating a second KEK and storing the second KEK in a second environment KMS; encrypting the first DEK with the second KEK and the second DEK with the second KEK; and storing the encrypted first DEK and the encrypted second DEK in the database.

Abstract: Systems and methods for key synchronization in multi-cloud environments are disclosed. A method may include: (1) generating, by a synching computer application and using a first key management service in a first cloud environment, a data encryption key and storing the data encryption key in the first key management service; (2) generating, by the synching computer application and using a second key management service in a second cloud environment, a key encryption key pair comprising a private key and a public key and storing the key encryption key pair in the second key management service; (3) fetching, by the synching computer application, the public key from the second key management service; (4) encrypting, by the synching computer application, the data encryption key with the public key; and (5) storing, by the synching computer application, the encrypted data encryption key in a database in the second cloud environment.

Abstract: A method for facilitating application authentication bypass based on proximate with time using device authentication is disclosed. The method includes receiving a request from a user to access an application on a user device, the request including an application authentication request; accessing the user device via a device application programming interface; retrieving, via the device application programming interface, device authentication data, the device authentication data including a timeline of successful device authentications; determining whether the device authentication data is within a predetermined threshold; authenticating the request by using the device authentication data when the device authentication data is within the predetermined threshold; and permitting access to the application based on a result of the authenticating.

Abstract: A method for extended authentication sessions on an electronic device may include an authentication service computer program executed by an authentication service electronic device: receiving a customer identifier for a customer and a unique identifier for a mobile electronic device; authenticating the customer based on the customer identifier and the unique identifier for the mobile electronic device; setting a device cookie that is specific to the mobile electronic device on the mobile electronic device; and providing the device cookie and a client secret to an OAuth services backend, wherein the OAuth services backend validates the customer identifier and client secret and generates a first token and a second token, the first token having an expiration that is shorter than that of the second token. The mobile electronic device is configured to receive and store the first token and the second token.