System and method for automatically detecting and then self-repairing corrupt, modified or non-existent files via a communication medium

• US 9,842,230 B1
• Filed: 12/14/2015
• Issued: 12/12/2017
• Est. Priority Date: 12/18/2000
• Status: Expired due to Term

• Current Assignee: Citibank NA (Citigroup Incorporated)
• Original Assignee: Citibank NA (Citigroup Incorporated)
• Inventors: Vlcan, Steve, Bakshi, Bikram Singh
• Primary Examiner(s): Moorthy, Aravind
• Application Number:
  US14/968,244
• Time in Patent Office: 729 Days
• Field of Search: 726 7, 726 22, 726 26, 713161, 713165, 713168, 713176, 713187
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/565 by checking file integrity
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: G06F 2221/034 Test or assess a computer or a system
• CPC Class Codes: H04L 63/0245 Filtering by information in the payload
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: Y04S 40/20 Information technology specific aspects, e.g. CAD, simulation, modelling, system security

Abstract

A system and method of guaranteeing the presence of secure and tamper-proof remote files over a distributed communication medium, such as the Internet, is provided. The system and method automatically detects, and then self-repairs corrupt, modified or non-existent remote files. The method first performs an integrity check on a remote file and then determines whether the integrity check passed. If the integrity check passed, then the user goes through the authentication process as normal. If the integrity check fails, then the present invention redirects to an install module in order to prepare to reinstall the remote file. Via the install module, the present invention then reinstalls the remote file and the user is then taken through the authentication process as normal.

Claims

1. A computer-implemented method of filtering a request from a client device comprising:

receiving, by a filter, a message transmitted from a web browser of the client device;

determining, by a redirect module of the filter, whether the message comprises a request for authentication for a website hosted by an application server;

routing, by the redirect module of the filter, the message to the authentication server when the message comprises the request for authentication;

determining, by an integrity module of the authentication server, whether a remote file or module at an authentication control component passes an integrity check;

when the remote file or module passes the integrity check, authenticating, by the authentication server, the client device; and

when the remote file or module does not pass the integrity check, routing, by the redirect module of the filter, a request to an install module of the application server to reinstall the remote file or module.

2. The method according to claim 1, further comprising capturing, by the authentication control component, user credentials and communicating the captured credentials to the authentication server.

3. The method according to claim 2, wherein the captured credentials are transmitted from the authentication control component to the filter to the authentication server.

4. The method according to claim 1, wherein upon installation of the remote file or module, authenticating, by the authentication server, the client device.

5. The method according to claim 1, further comprising generating, by the authentication control component, a remote hash value of the remote file or module.

6. The method according to claim 5, further comprising transmitting, by the authentication control component, the remote hash value to the authentication server.

7. The method according to claim 6, further comprising generating a secure hash value on a mirror file in a mirror image directory, where the mirror file is a copy of a valid remote file.

8. The method according to claim 7, wherein:

when the secure hash value is the same as the remote hash value, then the remote file or module has passed the integrity check, and

when the secure hash value is different from the remote hash value, then the remote file or module has not passed the integrity check.

9. The method according to claim 1, further comprising modifying, by the redirect module, an address of the install module to include a parameter indicating a location of the remote file, and transmitting, by the redirect module, the modified address to the authentication control component.

10. The method according to claim 9, further comprising:

receiving, by the install module, the request to reinstall the remote file or module, and

generating, by the application server, a reinstallation web page.

11. The method according to claim 10, further comprising installing, by a tag module of the authentication control component, a new copy of the remote file or module using the reinstallation web page.