SYSTEM AND METHOD FOR ENHANCED VISUALIZATION OF EXFILTRATION ACTIVITIES
A system is configured to perform operations including receiving an indication of a filesystem event detected by an event monitor; determining a platform domain from the indication of the filesystem event; storing content of the filesystem event in a data store with content from a plurality of filesystem events; and displaying in a graphical user interface, attributes of the plurality of filesystem events, grouped by platform domain.
1 . A system comprising:
a processor subsystem; and
memory including instructions that, when executed by the processor subsystem, cause the processor subsystem to perform operations comprising:
receiving an indication of a filesystem event detected by an event monitor;
determining a platform domain from the indication of the filesystem event;
storing content of the filesystem event in a data store with content from a plurality of filesystem events; and
displaying in a graphical user interface, attributes of the plurality of filesystem events, grouped by platform domain.
2 . The system of claim 1 , wherein the event monitor is configured to interface with a web browser to detect filesystem events.
3 . The system of claim 1 , wherein the event monitor is configured to interface with a kernel filter to detect filesystem events.
4 . The system of claim 1 , wherein the event monitor is configured to interface with an event stream to detect filesystem events.
5 . The system of claim 1 , wherein the event monitor uses calculated hash values for files it monitors to detect when a file experiences the filesystem event.
6 . The system of claim 1 , wherein the event monitor uses calculated hash values for files it monitors to detect when contents of a file experience the filesystem event.
7 . The system of claim 1 , wherein determining the platform domain from the indication of the filesystem event comprises parsing a destination network location associated with the filesystem event.
8 . The system of claim 1 , wherein determining the platform domain from the indication of the filesystem event comprises interfacing with a domain name system (DNS) server to verify that the platform domain is registered with the DNS server.
9 . The system of claim 1 , further comprising:
categorizing the plurality of filesystem events into risk categories; and
displaying in the graphical user interface, the plurality of filesystem events grouped by the risk categories.
10 . The system of claim 1 , further comprising:
categorizing the plurality of filesystem events as being related to either personal activity or corporate activity; and
displaying in the graphical user interface, a first subset of the plurality of filesystem events grouped by personal activity and a second subset of the plurality of filesystem events grouped by corporate activity.
11 . The system of claim 1 , further comprising:
determining from the indication of the filesystem event, a common hostname related to the platform domain; and
displaying in the graphical user interface, the common hostname and the platform domain.
12 . The system of claim 1 , further comprising:
determining prevalent platform domains of the plurality of filesystem events; and
filtering platform domains displayed in the graphical user interface to those that are prevalent.
13 . The system of claim 12 , wherein determining prevalent platform domains comprises:
determining a number of filesystem events that are related to a given platform domain; and
marking the given platform domain as a prevalent platform domain when the number of filesystem events exceeds a threshold number.
14 . The system of claim 12 , wherein determining prevalent platform domains comprises:
determining a number of users associated with filesystem events that are related to a given platform domain; and
marking the given platform domain as a prevalent platform domain when the number of users exceeds a threshold number.
15 . A method comprising:
receiving an indication of a filesystem event detected by an event monitor;
determining a platform domain from the indication of the filesystem event;
storing content of the filesystem event in a data store with content from a plurality of filesystem events; and
displaying in a graphical user interface, attributes of the plurality of filesystem events, grouped by platform domain.
16 . The method of claim 15 , further comprising:
categorizing the plurality of filesystem events into risk categories; and
displaying in the graphical user interface, the plurality of filesystem events grouped by the risk categories.
17 . The method of claim 15 , further comprising:
categorizing the plurality of filesystem events as being related to either personal activity or corporate activity; and
displaying in the graphical user interface, a first subset of the plurality of filesystem events grouped by personal activity and a second subset of the plurality of filesystem events grouped by corporate activity.
18 . The method of claim 15 , further comprising:
determining from the indication of the filesystem event, a common hostname related to the platform domain; and
displaying in the graphical user interface, the common hostname and the platform domain.
19 . A non-transitory machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations comprising:
receiving an indication of a filesystem event detected by an event monitor;
determining a platform domain from the indication of the filesystem event;
storing content of the filesystem event in a data store with content from a plurality of filesystem events; and
displaying in a graphical user interface, attributes of the plurality of filesystem events, grouped by platform domain.
20 . The non-transitory machine-readable medium of claim 19 , wherein the instructions cause the machine to perform operations comprising:
determining prevalent platform domains of the plurality of filesystem events; and
filtering platform domains displayed in the graphical user interface to those that are prevalent.