Systems and methods for performing or creating simulated phishing attacks and phishing attack campaigns
US-9894092-B2 · Feb 13, 2018 · US
US10657248B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10657248-B2 |
| Application number | US-201816047833-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 27, 2018 |
| Priority date | Jul 31, 2017 |
| Publication date | May 19, 2020 |
| Grant date | May 19, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure describes a system for saving metadata on files and using attribute data files inside a computing system to enhance the ability to provide user interfaces based on actions associated with non-executable attachments like text and document files from untrusted emails, to block execution of potentially harmful executable object downloads and files based on geographic location, and to a create a prompt for users to decide whether to continue execution of potentially harmful executable object downloads and files. The system also records user behavior on reactions to suspicious applications and documents by transmitting a set of attribute data in an attribute data file corresponding to suspicious applications or documents to a server. The system interrupts execution of actions related to untrusted phishing emails in order to give users a choice on whether to proceed with actions.
Opening claim text (preview).
We claim: 1. A method for creating attribute data for a file of an application, the method comprising: (a) registering, by a service executing on a device, a driver into an operating system of the device to monitor processes, the driver configured to receive notifications from the operating system of processes started or terminated on the device; (b) executing, an attribute data writer on the device, the attribute data writer in communication with the driver to receive notifications from the driver of processes started on the device; (c) receiving, by the attribute data writer, a process id from the driver for a process of an application detected by the driver as starting on the device; (d) injecting, by an injector program launched by the attribute data writer, an attribute data writer library into the process of the application corresponding to the process id; (e) classifying, by the attribute data writer library, the application into a class of a plurality of classes; and (f) causing, by the attribute data writer library, the application to create attribute data corresponding to the class responsive to a file being one of created or opened by the application. 2. The method of claim 1 , wherein (b) further comprises executing, by the service, the attribute data writer responsive to a user being logged in. 3. The method of claim 1 , wherein (c) further comprises receiving, by the attribute data writer, a second process id corresponding to a parent process. 4. The method of claim 1 , further comprising determining, by the attribute data writer, if one of the path or name of the file, determined from the process is, is in a list of applications to be monitored by the attribute data writer. 5. The method of claim 4 , further comprising determining, by the attribute data writer responsive to the file being in the list of applications to be monitored, a type of architecture of the application. 6. The method of claim 5 , wherein (d) further comprises launching, by the attribute data writer, a version of the injector program corresponding to the type of architecture. 7. The method of claim 1 , wherein (e) further comprises obtaining, by the attribute data write library, information on the injected application and classifying, based on the information, the application into the class of the plurality of classes comprising an email client, a word processor, a web browser, a portable document format reader or writer. 8. The method of claim 1 , further comprising causing, by the attribute data writer library, the data to be stored to one of a master file table or an alternate data stream. 9. The method of claim 1 , further comprising: identifying an attribute data file of a second file being one of opened or created by the application; identifying from one or more attribute data values in the attribute data file a class of the application; and identifying from one or more attribute data values in the attribute data file a non-system initiator application of the application. 10. The method of claim 9 , further comprising determining that the second file is suspicious based on the one or more attribute data values. 11. The method of claim 10 , further comprising displaying, responsive to the determination, a prompt that the second file is suspicious.
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Location-sensitive, e.g. geographical location, GPS · CPC title
service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12) · CPC title
monitoring of user actions (tracking the activity of the user H04L67/535) · CPC title
by adding security routines or objects to programs · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.