# US 2019/0318110 A1 · System and method for automatically securing sensitive data in public cloud using a serverless architecture > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0318110 A1 - Document ID: US20190318110A1 - Status: Published application - Kind: A1 - Application number: 16/265,847 - Filed: 2019-02-01 - Published: 2019-10-17 - Earliest claimed: 2018-04-11 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC. - Inventors: Nathal L. Fonseka; Ankit Pansari - Web page: https://patentgrep.com/patent/US20190318110A1 ## CPC - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - G06F 16/162: {Delete operations (erasing in storage systems G06F3/0652)} - G06F 21/602: {Providing cryptographic facilities or services} - G06F 21/604: {Tools and structures for managing or administering access control systems} - G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes} - G06F 2221/2115: Third party - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems and methods are provided executing jobs immediately upon receipt of a notification. The systems and methods may include receiving, at a cloud compute service, a notification that a sensitive file comprising sensitive data has been received at a file receipt location, the sensitive file being sent by a client device; generating, by the cloud compute service, a container instance in response to the notification; retrieving, by the container instance, the sensitive file from the file receipt location; generating, by the container instance, a stripped file by stripping the sensitive data from the sensitive file based on a configuration file; transmitting, by the container instance, the stripped file to a storage location; deleting the sensitive file and associated file pointers from the file receipt location; and terminating the container instance, wherein terminating the container instance comprises deleting files comprising sensitive data and associated file pointers. ## Claims ### Claim at position 1 1-20. (canceled) ### Claim 21 A file receipt location system, comprising: a first set of one or more memory units for storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving an incoming file from a client device, the incoming file comprising sensitive information; transmitting a notification to a cloud compute service indicating that the incoming file has been received at a file receipt location system, the cloud compute service configured to allocate a container instance which strips the sensitive information from the tagged file; tagging the incoming file with a tag identifying one of a vendor or service provider to create a tagged file; based only on completion of the tagging, transmitting the tagged file to the cloud compute service; and destroying the tagged file. ### Claim 22 (depends on 21) The system of claim 21, wherein receiving an incoming file comprises receiving an incoming file which was manually transmitted from the client device by a user of the client device. ### Claim 23 (depends on 22) The system of claim 22, wherein receiving an incoming file comprises receiving an incoming file originated externally from the client device. ### Claim 24 (depends on 21) The system of claim 21, wherein destroying the tagged file comprises: permanently deleting the tagged file; and permanently deleting a file pointer associated with the tagged file. ### Claim 25 (depends on 24) The system of claim 24, wherein permanently deleting the tagged file comprises wiping data by overwriting memory associated with the tagged file. ### Claim 26 (depends on 24) The system of claim 24, wherein permanently deleting the tagged file comprises marking the tagged file for permanent deletion at a later time. ### Claim 27 (depends on 21) The system of claim 21, wherein: the operations further comprise receiving, from the cloud compute service, an instruction to destroy the tagged file; and destroying the tagged file comprises destroying the tagged file based on the instruction. ### Claim 28 (depends on 21) The system of claim 21, wherein: the operations further comprise generating, by programs of the file container location system, an instruction to destroy the tagged file; and destroying the tagged file comprises destroying the tagged file based on the instruction. ### Claim 29 (depends on 21) The system of claim 21, wherein the tagging further comprises at least one of tagging as restricted, tagging for aggregation, tagging for encryption, tagging as relating to a configuration file, or tagging as belonging to a file class. ### Claim 30 (depends on 21) The system of claim 21, the operations further comprising: storing the incoming file using a method of encryption prior to tagging the incoming file. ### Claim 31 (depends on 21) The system of claim 21, the operations further comprising transmitting a notification to the cloud compute service indicating that the incoming file has been received at file receipt location system. ### Claim 32 (depends on 31) The system of claim 31, wherein transmitting the notification comprises transmitting a notification which causes the cloud compute service to select a warm container instance to strip the sensitive information from the tagged file. ### Claim 33 (depends on 31) The system of claim 31, wherein transmitting the tagged file causes the cloud compute service to generate the container instance to strip the sensitive information from the tagged file. ### Claim 34 (depends on 31) The system of claim 31, wherein transmitting the notification comprises transmitting a notification comprising a file identifier associated with the incoming file. ### Claim 35 (depends on 21) The system of claim 21, comprising a distributed computer system. ### Claim 36 (depends on 21) The system of claim 21, further comprising a second set of one or more memory units residing on a plurality of physical facilities separated by a distance; and wherein the operations further comprise storing at least one of the incoming file or the tagged file on the second set of one or more memory units. ### Claim 37 (depends on 21) The system of claim 21 further comprising monitoring functions to detect data anomalies in the file receipt location. ### Claim 38 (depends on 21) The system of claim 21, wherein receiving an incoming file comprises receiving an incoming file comprising information associated with a transaction. ### Claim 39 A method for processing a job, comprising: receiving an incoming file from a client device, the incoming file comprising sensitive information; transmitting a notification to a cloud compute service indicating that the incoming file has been received at a file receipt location system, the cloud compute service configured to allocate a container instance which strips the sensitive information from the tagged file; tagging the incoming file with a tag identifying one of a vendor or service provider; transmitting the tagged file automatically to the cloud compute service; and destroying the tagged file. ### Claim 40 A file receipt location system, comprising: one or more memory units for storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving an incoming file from a client device, the incoming file comprising sensitive information; transmitting a notification to a cloud compute service indicating that the incoming file has been received at a file receipt location system, the cloud compute service configured to allocate a container instance which strips the sensitive information from the tagged file; transmitting the incoming file to the cloud compute service; and executing an instruction, from a computer program running in the one or more memory units, to destroy the incoming file; and destroying the tagged file.