Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A system for verifying data files prior to communicating the data file, via a data channel, to an external recipient, the system comprising: a computing platform including a memory and at least one processor in communication with the memory; a data file registration repository stored in the memory, executable by the processor and configured to register, proximate in time to when the data file is created, information associated with the data file, wherein the registered information includes, at least, contents of the data file, wherein the contents of the data file include a line item quantity and a secured data element quantity; and a data file interrogation and verification module stored in the memory, executable by the processor that is configured to receive the data file prior to data channel submission, access the data file registration repository to identify the registered information associated with the data file, interrogate a payload of the data file to determine difference between actual contents of the data file and the registered information by: determining actual line item quantity and actual secured data element quantity; and comparing the actual line item quantity and the actual secured data element quantity to the registered line item quantity and the registered secured data element quantity to determine a difference between either one of the actual line item quantity and the registered line item quantity or the actual secured data element quantity and the registered secured data element quantity.
The system validates data files before sending them externally. It includes a computer with memory and a processor. A data file registration repository, stored in memory, registers information about data files soon after they're created, including the file's contents (line item quantity and secured data element quantity). A data file interrogation module, also in memory, checks files before external submission. It accesses the repository to get the registered information, then examines the file's payload to determine if there are differences in the actual and registered line item and secure data element quantities. It compares these quantities to determine any discrepancies.
2. The system of claim 1 , wherein the data interrogation and verification module is further configured to determine a type of the difference and based on the type of the difference perform one of (1) prohibit the data file from being communicated to the external recipient, (2) request approval for the data file to be communicated to the external recipient or (3) communicate the data file to the external recipient and alert predetermined internal entities.
The data file validation system from the previous description can also determine the *type* of difference found between the registered and actual data file contents. Based on this difference type, the system can either: (1) block the file from being sent, (2) request approval before sending, or (3) send the file but alert internal teams. So, if there's a small, acceptable discrepancy, it might alert internal teams. But, if there's a large or critical difference, it might block the data file completely.
3. The system of claim 1 , wherein the data file registration repository is further configured to automatically register the information associated with the data file based on receipt, upon creation of the data file, file header metadata that includes the information to be registered.
In the data file validation system described earlier, the data file registration repository automatically registers file information when the data file is created. It does this by capturing file header metadata, which contains the relevant information to be registered. Therefore, as soon as the data file is created, its header information is automatically used to register it in the repository.
4. The system of claim 3 , wherein the data registration repository is further configured to receive the file header metadata that includes the information to be registered, wherein the information includes one or more of filename, file size, file type, checksum, identity of file creator, identity of one or more file revisers, dates of one or more revisions to the data file, quantity of line items, and quantity of secure data elements.
In the data file validation system where the data file registration repository automatically registers file information, the file header metadata that is received includes information such as filename, file size, file type, checksum, who created the file, who revised it, revision dates, quantity of line items, and quantity of secure data elements. Therefore, the repository has a wide range of information about each file registered automatically.
5. The system of claim 1 , wherein the data file registration repository is further configured to register the information associated with the data file, wherein the registered information includes a first checksum resulting from creation of the data file.
The data file validation system also registers a first checksum value, generated when the data file is created, within the data file registration repository. This initial checksum acts as a baseline for later comparison to ensure the file hasn't been tampered with since its creation.
6. The system of claim 5 , wherein the data file interrogation and verification module is further configured to create a second checksum of the received data file and compare the second checksum to the first checksum to determine a difference between the first and second checksums.
The data file validation system with the checksum feature calculates a second checksum on the data file just before it is sent externally. It then compares this second checksum to the first checksum (registered at creation) to check for any differences. If the checksums don't match, it indicates that the file has been modified.
7. The system of claim 1 , wherein the data file registration repository is further configured to register the information associated with the data file, wherein the registered information includes identity of the external recipient.
The data file validation system also registers the identity of the intended external recipient in the data file registration repository. This allows the system to verify that the file is being sent to the correct recipient, preventing accidental or malicious data leaks.
8. The system of claim 7 , wherein the data file interrogation and verification module is further configured to receive an intended external recipient of the data file, and compare the intended external recipient to the identity of the external recipient in the registered information to determine a difference between the intended external recipient and the identity of the external recipient in the registered information.
The data file validation system from the previous description takes the intended external recipient of the data file as input. It compares this intended recipient against the registered external recipient in the repository. If there's a mismatch, it flags the discrepancy, indicating a potential problem with the transmission.
9. The system of claim 7 , wherein the data file registration repository is further configured to register the information associated with the data file, wherein the registered information includes a security status of the contents of the data file.
The data file validation system also registers a security status for the contents of the data file in the data file registration repository. This could indicate the sensitivity or classification level of the data within the file, enabling security-based routing and authorization decisions.
10. The system of claim 9 , further comprising an external recipient security rating repository, stored in the memory, executable by the processor and configured to store security ratings for a plurality of external recipients, wherein the security ratings define a type of data that each external recipient is authorized to receive and wherein the data file interrogation and verification module is further configured to access the external recipient security rating repository to determine the security rating for the intended external recipient and compare the security rating to the security status of the contents of the data file to determine if the security rating is noncompliant with the security status of the contents of the data file.
The data file validation system includes an external recipient security rating repository, which stores security ratings for external recipients. These ratings define the type of data each recipient is allowed to receive. The data file interrogation module checks the intended recipient's rating against the data file's security status. If the rating isn't high enough for the data's status (noncompliant), the system can block or flag the transmission.
11. The system of claim 1 , further comprising an alert module stored in the memory, executable by the processor and configured to receive notification from the data file interrogation and verification module that the comparison resulted in a difference between the actual contents and the registered information and generate and initiate communication of an alert, to one or more predetermined internal recipients, that is configured to notify the internal recipients that the data file is prohibited from being communicated to the external recipient.
The data file validation system has an alert module. If the data file interrogation module finds a difference between the actual and registered content, it notifies the alert module. The alert module then sends a notification to predetermined internal recipients, informing them that the data file cannot be sent externally.
12. A method for verifying data files prior to communicating the data file, via a data channel, to an external recipient, the method comprising: registering, in a data file registration repository, proximate in time to when the data file is created, information associated with the data file, wherein the registered information includes, at least, contents of the data file; wherein the contents of the data file include at least a line item quantity and a secured data element quantity; accessing the data file registration repository to identify the registered information associated with the data file; and interrogating prior to the data file entering the data channel, by a computing device processor, a payload of the data file to determine difference between actual contents of the data file and the registered information by: determining actual line item quantity and actual secured data element quantity; and comparing the actual line item quantity and the actual secured data element quantity to the registered line item quantity and the registered secured data element quantity to determine a difference between either one of the actual line item quantity and the registered line item quantity or the actual secured data element quantity and the registered secured data element quantity.
This is a method for validating data files before external communication. First, register information about the data file in a repository soon after its creation. This information includes the file's contents, specifically line item and secured data element quantities. Before the file is sent externally, access the repository to retrieve the registered information. Then, examine the file's payload to determine if there are discrepancies in the line item and secure data element quantities compared to what was registered. Any differences are flagged.
13. The method of claim 12 , further comprising: determining, by a computing device processor, a type of the difference between the actual contents and the registered information; and based on the type of the difference, performing one of (1) prohibit the data file from being communicated to the external recipient, (2) request approval for the data file to be communicated to the external recipient or (3) communicate the data file to the external recipient and alert predetermined internal entities.
The data file validation method from the previous description includes determining the *type* of difference found between the registered and actual data file contents. Based on this difference type, the method can either: (1) block the file from being sent, (2) request approval before sending, or (3) send the file but alert internal teams. The response is contingent on the severity of the detected discrepancy.
14. The method of claim 12 , wherein registering the information associated with the file further comprises automatically registering the information associated with the data file based on receiving, upon creation of the data file, file header metadata that includes the information to be registered.
In the data file validation method, registering file information is done automatically when the data file is created. This automatic registration occurs when the system receives the file's header metadata, which contains the relevant information to be registered, upon creation of the data file.
15. The method of claim 14 , wherein receiving the file header metadata further comprises receiving the file header metadata that includes the information to be registered, wherein the information includes one or more of filename, file size, file type, checksum, identity of file creator, identity of one or more file revisers, dates of one or more revisions to the data file, quantity of line items, and quantity of secure data elements.
When automatically registering a data file, the file header metadata includes: filename, file size, file type, checksum, who created the file, who revised it, revision dates, quantity of line items, and quantity of secure data elements. This comprehensive information set is automatically extracted from the file header upon creation.
16. A computer program product comprising: a non-transitory computer-readable medium comprising: a first set of codes for causing a computer to register, in a data file registration repository, proximate in time to when a data file is created, information associated with the data file, wherein the registered information includes, at least, contents of the data file, wherein the contents of the data file include at least a line item quantity and a secured data element quantity; a second set of codes for causing a computer to access the data file registration repository to identify the registered information associated with the data file, a third set of codes for causing a computer to interrogate, prior to the data file entering a data channel, a payload of the data file to determine difference between actual contents of the data file and the registered information by: determining actual line item quantity and actual secured data element quantity; and comparing the actual line item quantity and the actual secured data element quantity to the registered line item quantity and the registered secured data element quantity to determine a difference between either one of the actual line item quantity and the registered line item quantity or the actual secured data element quantity and the registered secured data element quantity.
This is a computer program product for validating data files. It has a non-transitory computer-readable medium storing instructions. These instructions cause the computer to: register information about the data file in a repository shortly after its creation, including line item and secure data element quantities. Before external transmission, the instructions cause the computer to access the repository to get the registered information and examine the file's payload, determining discrepancies between actual and registered line item and secure data element quantities.
17. The computer-program product of claim 16 , wherein the computer-readable medium further comprises a fourth set of codes configured to cause a computer to determine a type of the difference between the actual contents and the registered information and based on the type of the difference, perform one of (1) prohibit the data file from being communicated to the external recipient, (2) request approval for the data file to be communicated to the external recipient or (3) communicate the data file to the external recipient and alert predetermined internal entities.
The data file validation computer program product from the previous description also includes instructions to determine the *type* of difference found. Based on this difference type, the computer can (1) block the file, (2) request approval, or (3) send the file but alert internal teams. The action taken is decided by the severity of difference between the actual and registered data file contents.
18. The computer-program product of claim 16 , wherein the computer-readable medium further comprises a fourth set of codes configured to cause a computer to configure the data file registration repository to automatically register the information associated with the data file based on receipt, upon creation of the data file, file header metadata that includes the information to be registered.
The data file validation computer program product has instructions to automatically register file information when the data file is created. This involves automatically configuring the data file registration repository based on the file's header metadata. Upon file creation, the repository is configured with the received header metadata information.
19. The computer-program product of claim 18 , wherein the computer-readable medium further comprises a fourth set of codes configured to cause a computer to configure the data file registration repository to receive the file header metadata that includes the information to be registered, wherein the information includes one or more of filename, file size, file type, checksum, identity of file creator, identity of one or more file revisers, dates of one or more revisions to the data file, quantity of line items, and quantity of secure data elements.
Within the data file validation computer program product, the file header metadata that is automatically received by the data file registration repository includes information such as filename, file size, file type, checksum, file creator identity, reviser identities, revision dates, quantity of line items, and quantity of secure data elements. All of this data is automatically extracted and used for repository configuration.
Unknown
October 31, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.