Retention and accessibility of data characterizing events on an endpoint computer

US10354067B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10354067-B2
Application numberUS-201615356029-A
CountryUS
Kind codeB2
Filing dateNov 18, 2016
Priority dateFeb 26, 2016
Publication dateJul 16, 2019
Grant dateJul 16, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An endpoint computer system can harvest data relating to a plurality of events occurring within an operating environment of the endpoint computer system and can add the harvested data to a local data store maintained on the endpoint computer system. In some examples, the local data store can be an audit log and/or can include one or more tamper resistant features. Systems, methods, and computer program products are described.

First claim

Opening claim text (preview).

What is claimed is: 1. A system, comprising: computer hardware having at least one data processor and memory storing instructions which, when executed by the at least one data processor, result in configured to perform operations comprising: harvesting, by an endpoint computer system, data relating to a plurality of events occurring within an operating environment of the endpoint computer system, the harvesting comprising receiving and/or inferring the data using one or more sensors executing on the endpoint computer system; adding the data to a local data store maintained on the endpoint computer system, the local data store comprising an audit log, the audit log comprising a series of data containers, each data container in the series comprising a tamper resistant feature, currently generated forensic data being stored in a current data container of the series while preceding data containers in the series are closed to further write operations; generating a query response in response to a query specifying an artifact on the endpoint computer system and/or an event of the plurality of events, the generating comprising identifying and retrieving responsive data from the local data store, the responsive data being related to the artifact on the endpoint computer system specified by the query and/or to the event of the plurality of events specified by the query, the generating further comprising mitigating an amount of the data returned as part of the responsive data, the mitigating comprising interpreting the query at the endpoint computer system and focusing on specific data of the responsive data that are most likely to be relevant to a subject of the query; and taking an action based on the detecting that the audit log has been compromised, the action comprising one or more of: quarantining a thread, process, and/or routine responsible for the compromising of the audit log; and protection and/or other prevention of corruption of the forensic data that are used to generate the audit log and local cache. 2. A system as in claim 1 , wherein the artifact comprises a digital item of interest comprising one or more of a file, a programs, and a system characteristic. 3. A system as in claim 1 , further comprising detecting that the audit log has been compromised based on a change in the tamper resistant feature. 4. A system as in claim 1 , wherein the tamper resistant feature comprises a cryptographic fingerprint that references at least one prior data container in the series, and wherein the change in the tamper resistant feature comprises a data container of the series of data containers being referenced in the cryptographic fingerprint of a following data container but no longer being present in the audit log. 5. A system as in claim 1 , wherein the tamper resistant feature comprises data compression and signing with a public key and/or enciphering of a combination of the data container plus a signature comprising the public key. 6. A system as in claim 1 , wherein the audit log and the local cache are both stored on the endpoint computer. 7. A system as in claim 1 , wherein each data container of the series of data containers in the audit log is encrypted and wherein the forensic data are written to the current data container in an append-only manner. 8. A system as in claim 1 , wherein the harvesting further comprises receiving and/or inferring at least some of the data using additional data generated external to the endpoint computer system. 9. A system as in claim 1 , wherein the adding of the data to the local data store further comprises determining, based on one or more criteria, to retain in the local data store a first subset of the data as more likely to be relevant and to exclude from the local data store and a second subset of the data as more likely to be irrelevant. 10. A system as in claim 1 , wherein the event comprises an action occurring on the endpoint computer system and involving one or more artifacts on the endpoint computer system and/or wherein the event comprises a capture of what occurred at a specific point in time relating to the at least one artifact. 11. A system as in claim 1 , wherein the responsive data comprises one or more of one or more times that a particular file was accessed on the endpoint computer system, how the particular file was used on the endpoint computer system, when the particular file was first detected on the endpoint computer system, location of a registry persistence point, and use of a registry by a software routine to allow itself to persist after a reboot of the endpoint computing system. 12. A system as in claim 1 , wherein the one or more sensors comprises at least one of a kernel mode collector, a removable media sensor, a sensor that collects data about a current state of a computing environment executing on the endpoint computer, a malware detection and/or interdiction process, a user authentication process, and a user authentication re-verification process. 13. A system as in claim 1 , wherein the operations further comprise: harvesting the data according to a first set of data collection criteria; determining, via a threat detection module, that a heightened level of alert is necessary based on a determination that data stored in the audit log indicates that a threat or an attack is underway or imminent; and in response to the a heightened level of alert, harvesting the data according to a second set of data collection criteria, wherein the second set of data collection criteria is put into operation when the threat detection module indicates that a threat or attack is (i) in progress, (ii) might be imminent, or (iii) has just occurred, and directs the system to harvest data with (a) added detail, (b) added complexity and/or (c) granularity. 14. A system as in claim 13 , wherein the threat detection module comprises a machine learning component. 15. A system as in claim 14 , wherein the machine learning component performs at least one operation selected from determining that the heightened level of alert is necessary, blocking or terminating execution of a process or thread, and determining that the alert level can be lowered back to the first set of data collection criteria. 16. A system as in claim 14 , wherein the machine learning component accomplishes the at least one operation by processing data already in the local data store to determine that a potentially undesirable event has occurred and/or by processing the harvested data as it is received to determine that a potentially undesirable event is currently occurring. 17. A non-transitory computer readable medium storing instructions that, when executed by one or more programmable processors, cause the one or more programmable processors to perform operations comprising: harvesting, by an endpoint computer system, data relating to a plurality of events occurring within an operating environment of the endpoint computer system, the harvesting comprising receiving and/or inferring the data using one or more sensors executing on the endpoint computer system; adding the data to a local data store maintained on the endpoint computer system, the local data store comprising an audit log, the audit log comprising a series of data containers, each data container in the series comprising a tamper resistant feature, currently generated forensic data being stored in a current data container of the series while preceding data containers in the series are closed to further write operations; generating a query response in response to a query specifying an artifact on the endpo

Assignees

Inventors

Classifications

  • Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title

  • involving event detection and direct action · CPC title

  • G06F21/56Primary

    Computer malware detection or handling, e.g. anti-virus arrangements · CPC title

  • involving long-term monitoring or reporting · CPC title

  • Auditing as a secondary aspect · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10354067B2 cover?
An endpoint computer system can harvest data relating to a plurality of events occurring within an operating environment of the endpoint computer system and can add the harvested data to a local data store maintained on the endpoint computer system. In some examples, the local data store can be an audit log and/or can include one or more tamper resistant features. Systems, methods, and computer…
Who is the assignee on this patent?
Cylance Inc
What technology area does this patent fall under?
Primary CPC classification G06F21/56. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jul 16 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 7 related publications on this page (citations in our corpus or others sharing the same primary CPC).