US2016359914A1PendingUtilityA1
Determining the chronology and causality of events
Est. expiryJun 5, 2035(~8.9 yrs left)· nominal 20-yr term from priority
Inventors:Khawar DeenNavindra YadavAnubhav GuptaShashidhar GandhamRohit Chandra PrasadAbhishek Ranjan SignhShih-Chun Chang
G06T 11/26H04W 72/54H04L 41/0894H04L 63/20G06F 2221/2105G06F 2221/033H04L 43/04H04L 47/31H04L 43/12G06F 21/552H04L 63/06H04L 43/02G06F 2009/45595H04L 45/66G06F 2221/2145H04L 47/2483H04L 69/22H04L 63/0227G06N 20/00G06F 2009/45587H04J 3/14H04L 63/1408G06F 2009/4557H04L 43/0882H04L 41/046H04L 63/145H04L 47/32H04L 63/0876H04L 43/0876H04L 43/062H04L 47/2441H04L 63/0263H04L 43/0841H04L 47/20H04L 45/38G06F 2221/2115G06F 16/2365H04L 43/0888H04L 63/1441G06F 21/566H04L 9/0866G06F 3/0482G06F 2221/2111H04L 63/1466G06F 3/04842H04L 45/74H04L 43/0864H04W 84/18G06F 2221/2101G06F 2009/45591H04L 41/0816H04L 41/0803H04L 41/0806H04L 63/16H04L 43/10H04L 69/16H04L 67/10H04L 63/1433H04L 43/16H04L 43/0829H04L 41/22H04L 41/16H04J 3/0661H04L 63/1416H04L 9/3242H04L 1/242G06F 21/53H04L 47/11H04L 63/1425H04L 47/28H04L 45/306G06F 3/04847H04L 43/08H04L 41/12H04L 41/0893H04L 67/01H04L 63/1458H04L 43/045H04L 43/20H04L 41/40G06F 9/45558G06F 21/556H04L 67/535H04L 67/51H04L 67/75H04L 67/1001H04L 61/5007H04L 43/026G06F 16/17H04L 45/507G06F 16/1748G06F 16/137G06N 99/00H04L 43/0805G06F 16/122H04L 43/0811G06F 16/235G06F 16/162H04L 43/0858G06F 16/2322G06F 16/173G06F 16/174H04L 45/46H04L 9/3239H04L 67/12H04L 43/106H04L 41/0668G06F 16/1744G06F 16/9535G06F 16/285G06F 16/29G06F 16/288G06F 16/248G06F 16/24578H04L 7/10
71
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
An example method includes calculating latency bounds for communications from two sensors to a collector (i.e., maximum and minimum latencies). After the collector receives an event report from the first sensor and an event report form the second sensor, the collector can determine, using the latency bounds, whether one event likely preceded the other.
Claims
exact text as granted — not AI-modified1 . A computer-implemented method comprising:
receiving, from a first sensor at a first time, a description of a first event; receiving, from a second sensor at a second time, a description of a second event; and determining that the first event preceded the second event.
2 . The computer-implemented method of claim 1 , further comprising:
determining a minimum latency associated with the first sensor; determining a maximum latency associated with the second sensor; and wherein the determining that the first event preceded the second event comprises:
comparing the first time minus the minimum latency for the first sensor with the second time minus the maximum latency for the second sensor.
3 . The computer-implemented method of claim 2 , further comprising:
determining a maximum latency associated with the first sensor; determining a minimum latency associated with the second sensor; and determining that the first event caused the second event by determining that the first time minus the maximum latency associated with the first sensor is within a predetermined range with the second time minus the minimum latency associated with the second sensor.
4 . The computer-implemented method of claim 3 , wherein determining that the first event caused the second event is based on the type of event of the first event and the type of event of the second event.
5 . The computer-implemented method of claim 4 , wherein the second event is a data center attack.
6 . The computer-implemented method of claim 1 , further comprising:
receiving, from the first sensor, a description of a third event; receiving, from the second sensor, a description of a fourth event; wherein the determining that the first event preceded the second event comprises:
determining that the first event preceded the third event;
determining that the third event preceded the fourth event; and
determining that the fourth event preceded the second event.
7 . The computer-implemented method of claim 6 , wherein:
determining that the first event preceded the third event comprises comparing:
a timestamp associated with the first event with a timestamp associated with the third event; or
a sequence number associated with the first event with a sequence number associated with the third event; and
determining that the third event preceded the fourth event comprises comparing:
an event type associated with the third event with an event type associated with the fourth event.
8 . The computer-implemented method of claim 7 , wherein the first event is a data center attack, the method further comprising:
determining that the second event did not cause the first event.
9 . The computer-implemented method of claim 1 , wherein the second event is a process starting.
10 . The computer-implemented method of claim 1 , wherein the second time is before the first time.
11 . A non-transitory computer-readable medium having computer readable instructions stored thereon that, when executed by a processor of a computer, cause the computer to:
receive, from a first sensor at a first time, a description of a first event; receive, from the first sensor, a description of a third event; receive, from a second sensor at a second time, a description of a second event; receive, from the second sensor, a description of a fourth event; and determine that the first event preceded the second event by:
determining that the first event preceded the third event;
determining that the third event preceded the fourth event; and
determining that the fourth event preceded the second event.
12 . The non-transitory computer-readable medium of claim 11 , wherein:
the instructions that cause the computer to determine that the first event preceded the third event further cause the computer to compare:
a timestamp associated with the first event with a timestamp associated with the third event; or
a sequence number associated with the first event with a sequence number associated with the third event; and
the instructions that cause the computer to determine that the third event preceded the fourth event further cause the computer to compare an event type associated with the third event with an event type associated with the fourth event.
13 . The non-transitory computer-readable medium of claim 12 , wherein the first event is a data center attack and the instructions further cause the computer to:
determine that the second event did not cause the first event.
14 . The computer-implemented method of claim 1 , wherein the second sensor is installed on a virtual machine and the second event is a process starting.
15 . The computer-implemented method of claim 1 , wherein the second time is before the first time.
16 . A system comprising:
a processor; a computer-readable medium; and non-transitory computer-readable instructions stored thereon that, when executed by the processor, cause the system to:
determine a minimum latency associated with a first sensor;
receive, from the first sensor at a first time, a description of a first event;
determine a maximum latency associated with a second sensor;
receive, from the second sensor at a second time, a description of a second event; and
determine that the first event preceded the second event by:
comparing the first time minus the minimum latency for the first sensor with the second time minus the maximum latency for the second sensor.
17 . The system of claim 16 , wherein the instructions further cause the system to:
determine a maximum latency associated with the first sensor; determine a minimum latency associated with the second sensor; and determine that the first event caused the second event by determining that the first time minus the maximum latency associated with the first sensor is within a predetermined range with the second time minus the minimum latency associated with the second sensor.
18 . The system of claim 17 , wherein the instructions that cause the system to determine that the first event caused the second event do so based on the type of event of the first event and the type of event of the second event.
19 . The system of claim 18 , wherein the second event is a data center attack.
20 . The system of claim 16 , wherein the sensor is installed on a virtual machine and the second event is a process starting up.Join the waitlist — get patent alerts
Track US2016359914A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.