Methods and systems for improving analytics in distributed networks

Information

  • Patent Grant
  • 10193929
  • Patent Number
    10,193,929
  • Date Filed
    Friday, March 13, 2015
    9 years ago
  • Date Issued
    Tuesday, January 29, 2019
    5 years ago
Abstract
Systems and methods for improving analytics in a distributed network are described herein. An example system includes at least one processor, an analytics module, and a security policy module. The security policy module is operable to define a security policy. The security policy is executed by the processor on a network packet. Furthermore, the processor collects network information from the network packet. The analytics module is operable to analyze the network information with additional group information from the security policy. The analysis is used by the processor to generate the result. Based on the generated result, the security policy module updates the security policy.
Description
TECHNICAL FIELD

The present disclosure relates generally to data processing and, more particularly, to methods and systems for improving analytics in distributed networks.


BACKGROUND

The approaches described in this section could be pursued but are not necessarily approaches that have previously been conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.


Cloud computing, virtualization, software defined networks, and mobility are transforming legacy data centers having a client-to-server traffic flow, sometimes referred to as “north-south,” into data centers having server-to-server traffic flow, sometimes referred to as “east-west.” East-west traffic may also include traffic that travels between servers in different data centers. Due to the traffic volume or complexity of client requests, client requests may not be serviced by a single server. East-west architecture of data centers may enable data assets to be advantageously positioned in different locales, both inside and outside the enterprise premises. However, traditional perimeter security solutions often fail and cannot adequately protect the data centers from attackers.


An enterprise may attempt to analyze network traffic travelling between its servers. However, any analysis is normally limited to monitoring network traffic volume and determining trends in the traffic flow in order to discover malicious activities. Notably, the network traffic volume does not provide much contextual data with regards to the network environment. Therefore, attackers may find ways past the traditional perimeters by attacking low profile assets and then moving laterally across the data center to important enterprise assets to compromise enterprise and customer data.


Additionally, any correlations between hosts cannot be determined based solely on the network traffic volume.


SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that is further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.


Provided are systems and methods for improving analytics in a distributed network. An example method may commence with defining a security policy. The security policy may include a firewall security policy, but is not limited to this embodiment. The security policy may be associated with at least one host or one group. The security policy may be executed to determine action against a network packet. The method may further include collecting network information from the network packets. The network information may be generated based on log information associated with the at least one host or one group. The network information may be analyzed with additional group information from the security policy. The analysis may include analyzing network packets inside the at least one group, analyzing network packets traveling between two or more hosts or groups, and analyzing connections between the two or more hosts or groups. Based on the analysis, Domain Name Server (DNS) information for the network packet may be determined. Based on the DNS information, it may be determined whether a Domain Generation Algorithm (DGA) has been used to generate a domain name of a domain associated with the network packet. Based on log information associated with at least one group, the log information may be checked for security threats. Furthermore, the method may include generating a result from the analysis. Based on the generated result, the security policy may be updated. Updating of the security policy may include applying actions (e.g., permit or deny a connection), rearranging at least one group (for example, moving hosts between groups) and modifying security system parameters for the at least one group. The updating may further include generating an enforcement policy associated with at least one group, applying a packet capture (PCAP) to analyze contents of the network packet associated with the at least one group, and modifying a monitoring policy associated with the at least one group.


Also provided is a system for improving analytics in a distributed network. The system may comprise at least one processor, an analytics module, and a security policy module. The security policy module may be operable to define a security policy. The security policy may be associated with at least one group having at least one host. The security policy may be executed by the processor to inspect a network packet.


Furthermore, the processor may collect network information from the network packets. The analytics module may be operable to analyze the network information with additional group information from the security policy. The analysis may include determining DNS information for the network packet, based on the DNS information; determining whether a DGA has been used to generate a domain name of a domain associated with the network packet; and, based on log information associated with at least one group, analyzing the network information for security threats. The analysis may be used by the processor to generate a result. Based on the generated result, the security policy module may update the security policy. The updating may include generating an enforcement policy associated with at least one group, collecting packet capture of the network packet associated with at least one group, and modifying a monitoring policy associated with the at least one group.


In further exemplary embodiments, modules, subsystems, or devices can be adapted to perform the recited steps. Other features and exemplary embodiments are described below.





BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements.



FIG. 1 illustrates an environment within which systems and methods for improving analytics in a distributed network can be implemented, in accordance with some embodiments.



FIG. 2 is a block diagram showing various modules of a system for improving analytics in a distributed network, in accordance with certain embodiments.



FIG. 3 is a flow chart illustrating a method for improving analytics in a distributed network, in accordance with some example embodiments.



FIG. 4 shows a schematic diagram of interactions between a security policy module and an analytics module, in accordance with an example embodiment.



FIG. 5 shows a schematic diagram of analytics performed by a system for improving analytics in a distributed network, in accordance with an example embodiment.



FIG. 6 shows a diagrammatic representation of a computing device for a machine in the exemplary electronic form of a computer system, within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein, can be executed.





DETAILED DESCRIPTION

The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show illustrations in accordance with exemplary embodiments. These exemplary embodiments, which are also referred to herein as “examples,” are described in enough detail to enable those skilled in the art to practice the present subject matter. The embodiments can be combined, other embodiments can be utilized, or structural, logical, and electrical changes can be made without departing from the scope of what is claimed. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope is defined by the appended claims and their equivalents. In this document, the terms “a” and “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive “or,” such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated.


This disclosure provides methods and systems for improving analytics in a distributed network. A distributed network is a type of computer network, in which enterprise infrastructure resources are divided over a number of networks, processors, and intermediary devices. For the east-west traffic architecture, the network traffic may be spread out over a plurality of virtual machines (e.g., servers or hosts) and physical hosts inside the distributed network. As used herein, “host” refers to any computer connected to the distributed network.


The methods and systems of the present disclosure may allow integrating a security system, a security policy, and security analytics. More specifically, every network packet sent between hosts can be inspected by a security policy module. The security policy module may set a security policy for each host or a group of hosts. Generally, the security policy may include a set of rules directed to protecting information technology assets of a system, organization, or other entity. The security policy may define access control lists between address groups, where address groups are mostly groups of hosts with similar security attributes or functions, such as address groups for File Transfer Protocol (FTP) or Web/Hypertext Transfer Protocol (HTTP) servers.


The methods and systems of the present disclosure may import group information (for example, security attributes of the hosts) to group hosts together from a security system (or an enforcement module) and to utilize the group information for security analytics. More specifically, an analytics module may analyze intra-group network information, which relates to network packets travelling between the hosts of the same group, using an analytics model to correlate with the security system security policies related to the network packets. During the analysis, the analytics module can find inconsistent patterns in the network information related among hosts of a same address group, thus detecting the invasion. Based on the result of the analysis, the analytics module may send feedback to the security policy module. The feedback may include, for example, similar patterns in the network information. Based on the feedback received from the analytics module and correlation of security attributes related to the hosts, the security policy module may update the current security policy related to the hosts to perform deep packet inspection to retrieve more information for analysis, or block all network connections to a specific host if it detects malware infection of the host.


Additionally, the analytics module may analyze inter-group network information related to network packets travelling between hosts belonging to different groups. Based on the analysis and similar patterns found in the network information, the updated security policy may be generated, according to which some hosts of different groups may be regrouped. For example, the network information related to hosts of Group A and Group B may be analyzed, and based on the analysis of the network information and correlation of the security parameters, the hosts of Group A may be grouped together with some hosts of Group B into Group C. The hosts of Group C may have similar patterns in the network information, and a uniform security policy may be applied to the hosts of Group C.



FIG. 1 illustrates an environment 100 within which systems and methods for improving analytics in a distributed network can be implemented, in accordance with some embodiments. The environment 100 may include a virtualized environment in a distributed network (not shown), in which network traffic may travel between hosts 105. The hosts 105 may include any computers, servers, virtual machines, and the like of the distributed network. The hosts 105 may be grouped into groups, shown as a group A 110, a group B 115, and a group C 120. A system 200 for improving analytics in a distributed network may collect network information 125 related to the hosts 105 and network packets travelling between the hosts 105. A security policy module 230 may provide the system 200 with a security policy 135 related to the hosts 105. The security policy module 230 may communicate with analytics module 220 to check rules for applications associated with or running on hosts 105. The analytics module 220 may also analyze the network information 125 correlated with the security policy 135. Based on the analysis, the analytics module 220 may send a result 145 of the analysis to the security policy module 230. The security policy module 230 may use the result 145 to generate an updated security policy and apply the updated security policy 150 to the hosts 105. Application of the updated security policy is described further in related U.S. patent application Ser. No. 14/673,640, filed Mar. 30, 2015, entitled “Conditional Declarative Policies.”



FIG. 2 is a block diagram showing various modules of a system 200 for improving analytics in a distributed network, in accordance with certain embodiments. The system may comprise a processor 210, an analytics module 220, a security policy module 230, and one or more enforcement points. The processor 210 may include a programmable processor, such as a microcontroller, central processing unit, and so forth. In other embodiments, the processor 210 may include an application-specific integrated circuit or programmable logic array, such as a field programmable gate array, designed to implement the functions performed by the system. In various embodiments, the system 200 may reside outside an organization in a data center outside control of the organization and be provided as a cloud service.


The processor 210 may be operable to execute a security policy on a network packet. In an example embodiment, the processor 210 receives the security policy from the security policy module 230. In an example embodiment, the security policy is associated with at least one group, which includes at least one host. In a further example embodiment, the group includes a plurality of servers.


The processor 210 may be further operable to generate network information related to the network packet. In an example embodiment, the generating of the network information is based on log information associated with at least one group. In another example embodiment, the log information is stored in an indexed database (not shown). The index database may be operable to log and index the network information related to network packets. Furthermore, the processor 210 may be operable to generate a result from an analysis performed by the analytics module 220.


In an example embodiment, the result may include determining that the domain associated with the network packet is valid. In other embodiments, the result may include determining that the domain associated with the network packet is invalid. Moreover, the result may include determining that the domain associated with the network packet requires an elevated scrutiny. The elevated scrutiny may include collecting packet capture (PCAP) associated with the domain. A PCAP may consist of an application programming interface for capturing network traffic. Therefore, a PCAP may be a process of intercepting and logging network traffic.


In an example embodiment, the processor 210 may be operable to extract group information from the security policy. The group information may include group security attributes associated with the at least one group.


The analytics module 220 may be operable to analyze the network information. The analytics module 220 may receive the network information from the processor 210. The analysis may be performed using analytics module 220 correlated with the security policy.


In an example embodiment, during the analysis, the analytics module 220 may analyze data packets inside the at least one group or analyze data packets between two or more groups. Furthermore, the analytics module 220 may analyze connections between the two or more groups.


By way of further non-limiting example, the analysis may include determining DNS information for the network packet. Based on the DNS information, the analytics module 220 may determine if a DGA is used to generate a domain name of a domain associated with the network packet. Additionally, based on log information associated with at least one group, the analytics module 220 may check the network information for security threats.


The security policy module 230 may be operable to define the security policy. In an example embodiment, the security policy module 230 sends the security policy to the processor 210. The security policy module 230 may be further operable to update the security policy based on the result generated by the analytics module 220. In an example embodiment, the updating may include rearranging at least one group. The rearranging of the group may include moving hosts between groups. In other words, hosts belonging to different groups may be grouped into a single group. Security policy module 230 is described further in related U.S. patent application Ser. No. 14/673,640, filed Mar. 30, 2015, entitled “Conditional Declarative Policies.”


In a further example embodiment, the updating of the security policy may include modifying security system parameters for the at least one group. Additionally, the updating may include generating an enforcement policy associated with at least one group. In further embodiments, the updating includes modifying a monitoring policy to perform packet capture to further analyze contents of the network packet associated with the at least one host or one group.


One or more enforcement points intercept and analyze network traffic. One or more enforcement points are described in related U.S. patent application Ser. No. 14/657,282, filed Mar. 13, 2015, entitled “Methods and Systems for Providing Security to Distributed Microservices,” which is hereby incorporated by reference in its entirety.



FIG. 3 is a flow chart illustrating a method 300 for improving analytics in a distributed network, in accordance with some example embodiments. The method 300 may commence with defining a security policy at operation 302. The security policy may be associated with at least one group. The at least one group may include at least one host, at least one server, and the like. Optionally, the method 300 may include extracting group information from the security policy. The group information may include group security attributes associated with the at least one group.


Upon defining the security policy, the security policy may be executed on a network packet and information related to the network packet may be generated at operation 304. The network information may be analyzed at operation 306. In an example embodiment, the analyzing may include analyzing data packets inside the at least one group and analyzing data packets between two or more groups. Additionally, connections between the two or more groups may be analyzed.


By way of non-limiting example, analyzing may further include determining DNS information for the network packet. Based on the DNS information, it may be determined if a DGA is used to generate a domain name of a domain associated with the data packet. In further embodiments, the analyzing includes checking the network information for security threats based on log information associated with at least one group.


The analyzing may be performed using an analytics module with domain info extracted from security policy. The analysis may include generating a result. The result may include determining that the domain associated with the network packet is valid. In a further embodiment, the result may include determining that the domain associated with the network packet is invalid. Furthermore, the result may include determining that the domain associated with the network packet requires an elevated scrutiny. The elevated scrutiny may imply applying a PCAP to further network packets associated with the domain.


At operation 308, in response to a determination that elevated scrutiny is not needed, a policy is added to quarantine the infected host or group. At operation 310, the security policy is optionally updated.


At operation 308, in response to a determination that elevated scrutiny is needed, a policy is added to perform deep packet inspection and/or collect PCAP. At operation 310, the security policy is optionally updated.


In an example embodiment, the updating includes rearranging at least one group. The rearranging may include moving hosts between groups. The updating may further include modifying security system parameters for the at least one group.


In further example embodiments, the updating includes generating an enforcement policy associated with at least one group. In case the domain is determined to be invalid, all network packets coming from an invalid domain may be blocked. Furthermore, in the course of the updating, PCAP may be applied to analyze contents of the network packet associated with the at least one group. The updating may further result in modifying a monitoring policy associated with the at least one group.



FIG. 4 shows a schematic diagram 400 of interaction between a security policy module 230 and an analytics module 220, according to an example embodiment. The security policy module 230 may collect and provide group information 410 to the analytics module 220. The group information 410 may be intra-group information (i.e., may relate to hosts of the same group) or inter-group information (i.e., may relate to hosts of different groups). Based on the group information 410 received from the security policy module 230, the analytics module 220 may perform an analysis and provide a result 420 of the analysis to the security policy module 230. The result 420 may include rules to be included, changed, or updated in a security policy related to the hosts. For example, the rules may include adding or changing an enforcement policy related to the hosts or a domain associated with the hosts, adding or changing a monitoring policy related to the hosts or the domain associated with the hosts, collecting PCAP with a specific policy, collecting more information related to the hosts or the domain associated with the hosts, such as metadata of an application associated with the host, and so forth.



FIG. 5 shows a schematic diagram 500 of analytics performed by a system for improving analytics in a distributed network, according to an example embodiment. The security policy module 230 may include a sensor 505. The sensor 505 may collect at least one of application metadata 510, application information 515, some contextual information 520 related to an application associated with the hosts in a distributed network, and the like. The sensor 505 may provide the collected information to the analytics module 220. The analytics module 220 may perform pre-processing 525 of the information received from the sensor 505. The analytics module 220 may check rules for different applications. More specifically, the analytics module 220 may analyze the network packets to detect malicious activity. For example, in a case of receiving a DNS related to the network packet, the analytics module 220 may check whether a Domain Generation Algorithm (DGA) 530 is used to generate a domain name of a domain associated with a network packet sent by the host. For a Hypertext Transfer Protocol (HTTP) request, a Uniform Resource Locator (URL) User Agent 535 may be checked. Typically, the URL User Agent 535 is software used by HTTP to identify software or an application originating the request or network packet. Other checking 540 may be performed with regard to information related to other applications.


The analytics module 220 may put the results of analysis into an index database 545, in which all information related to applications and analysis performed by the analytics module 220 may be logged and indexed. A user query 550 may be directed to the index database 545 and may be duly processed based on the indexed information contained in the index database 545 and visualized to a user using a user interface 555.


The example procedure of generating a feedback by an analytics module to a security system security module may include the following steps. The analytics module 220 may have all information related to the network traffic inside a distributed network. All information related to the network traffic may be logged. For example, the analytics module 220 may receive information related to the DNS associated with the network packet. The DNS may provide DNS connection information. An example security policy may prescribe group A to communicate with group B. The query communicated from group A to group B may be a domain ‘ABC.com’ request. A domain ‘ABC.com’ reply may be ‘1.1.1.1’.


Upon receiving all network information, the analytics module 220 may check if the domain is associated with a security threat, such as malware. For example, the analytics module 220 may check a blacklist to verify whether malicious behaviors of the domain were previously identified or whether the domain is present in a list of domains associated with malware. Additionally, as the Domain Generation Algorithm 530 is usually used to generate domains on the spot, the analytics module 220 may check if the domain name is similar to domain names that can be generated by the Domain Generation Algorithm 530. Such checking may result in a false positive; therefore, the analytics module 220 may perform additional checking and verify whether the query related to domain is valid or invalid.


If it is determined that a DNS query related to domain ‘ABC.com’ is invalid, the security policy module may update the security policy related to group D associated with the DNS query related to domain ‘ABC.com.’ For example, an enforcement policy with regard to group D may be generated. The updated security policy may include blocking any further network packets from group D.


If it cannot be determined whether the DNS query related to domain ‘ABC.com’ is valid or invalid, an elevated scrutiny may be applied to the domain. For example, a PCAP may be applied to further network packets associated with the group D. In this way, further information may be collected about suspicious connections.



FIG. 6 shows a diagrammatic representation of a computing device for a machine in the exemplary electronic form of a computer system 600, within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein can be executed. In various exemplary embodiments, the machine operates as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine can operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine can be a server, a personal computer (PC), a tablet PC, a set-top box (STB), a PDA, a cellular telephone, a digital camera, a portable music player (e.g., a portable hard drive audio device, such as an Moving Picture Experts Group Audio Layer 3 (MP3) player), a web appliance, a network router, a switch, a bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.


The example computer system 600 includes a processor or multiple processors 602, a hard disk drive 604, a main memory 606 and a static memory 608, which communicate with each other via a bus 610. The computer system 600 may also include a network interface device 612. The hard disk drive 604 may include a computer-readable medium 620, which stores one or more sets of instructions 622 embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 622 can also reside, completely or at least partially, within the main memory 606 and/or within the processor(s) 602 during execution thereof by the computer system 600. The main memory 606 and the processor(s) 602 also constitute machine-readable media.


While the computer-readable medium 620 is shown in an exemplary embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present application, or that is capable of storing, encoding, or carrying data structures utilized by or associated with such a set of instructions. The term “computer-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media. Such media can also include, without limitation, hard disks, floppy disks, NAND or NOR flash memory, digital video disks, Random-Access Memory (RAM), Read-Only Memory (ROM), and the like.


The exemplary embodiments described herein can be implemented in an operating environment comprising computer-executable instructions (e.g., software) installed on a computer, in hardware, or in a combination of software and hardware. The computer-executable instructions can be written in a computer programming language or can be embodied in firmware logic. If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interfaces to a variety of operating systems. Although not limited thereto, computer software programs for implementing the present method can be written in any number of suitable programming languages such as, for example, C, Python, JavaScript, Go, or other compilers, assemblers, interpreters or other computer languages or platforms.


Thus, systems and methods for improving analytics in a distributed network are described. Although embodiments have been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes can be made to these exemplary embodiments without departing from the broader spirit and scope of the present application. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims
  • 1. A system for improving analytics in a distributed network, the system comprising: a hardware processor executing instructions stored in memory, the instructions comprising: executing a security policy on a network packet;collecting network information from the network packet;generating a result from an analysis;analyzing the network information with additional group information from the security policy, the analyzing including examining communications including network packets between at least some hosts in a group, the analyzing further including identifying patterns indicative of malicious activity in the communications;in response to the analyzing, defining a second security policy, the second security policy applying to the group, each host of the group having a similar security attribute associated with group security attributes of the group;updating the security policy based on the generated result, the updating the security policy including at least one of: performing deep packet inspection on the communications, andblocking network communications to an infected host in the group;collecting at least one of application metadata, application information, and contextual information related to an application associated with another host in the group; andproviding the collected information; wherein analyzing the network information correlated with the security policy includes: analyzing network packets between a first host in the group and a second host in the group;analyzing network packets between a third host in the group and a fourth host in a second group; andanalyzing connections between the group and the second group;wherein the network information from the network packets regarding a current state of the distributed network is dynamic and changing over time.
  • 2. The system of claim 1, wherein the the instructions further comprise extracting group information from the security policy, the group information including the group security attributes associated with the group.
  • 3. The system of claim 1, wherein the updating the security policy based on the generated result includes: permitting or denying a connection; andmodifying security system parameters for the group.
  • 4. The system of claim 1, wherein the analyzing the network information correlated with the security policy includes at least one of the following: determining Domain Name Server (DNS) information for the network packet;based on the DNS information, determining if a Domain Generation Algorithm (DGA) was used to generate a domain name of a domain associated with the network packet; andbased on log information associated with the group, checking the network information for security threats.
  • 5. The system of claim4, wherein the result includes at least one of the following: determining that the domain associated with the network packet is valid;determining that the domain associated with the network packet is invalid; anddetermining that the domain associated with the network packet requires an elevated scrutiny.
  • 6. The system of claim 5, wherein the elevated scrutiny includes applying a packet capture (PCAP) to further network packets associated with the domain.
  • 7. The system of claim 1, wherein the generating of the result related to the network packet is based on log information associated with the group.
  • 8. The system of claim 1, wherein the updating the security policy based on the generated result includes one or more of the following: generating an enforcement policy associated with the group;collecting Packet Capture (PCAP) to analyze contents of the network packet associated with the group; andmodifying a monitoring policy associated with the group.
  • 9. A method for improving analytics in a distributed network, the method comprising: defining a security policy, the security policy applying to a group, each host of the group having a similar security attribute associated with group security attributes of the group;executing the security policy on a network packet;collecting network information from the network packet;analyzing the network information with additional group information from the security policy, the analyzing including examining communications including network packets between at least some hosts in the group, the examining including identifying patterns indicative of malicious activity in the communications;generating a result from the analysis;updating the security policy based on the generated result, the updating the security policy including at least one of: performing deep packet inspection on the communications, andblocking network communications to an infected host in the group;collecting at least one of application metadata, application information, and contextual information related to an application associated with another host in the group; andproviding the collected information for the analysis; wherein the analyzing the network information includes: analyzing network packets between a first host in the group and a second host in the group;analyzing network packets between a third host in the group and a fourth host in a second group; andanalyzing connections between the group and the second group;wherein the network information from the network packets regarding a current state of the distributed network is dynamic and changing over time.
  • 10. The method of claim 9, further comprising extracting group information from the security policy, the group information including the group security attributes associated with the group.
  • 11. The method of claim 9, wherein the updating the security policy includes: permitting or denying a connection; andmodifying security system parameters for the group.
  • 12. The method of claim 9, wherein the analyzing includes at least one of the following: determining Domain Name System (DNS) information for the network packet;based on the DNS information, determining if a Domain Generation Algorithm (DGA) was used to generate a domain name of a domain associated with the network packet; andbased on log information associated with the group, checking the network information for security threats.
  • 13. The method of claim 12, wherein the result includes at least one of the following: determining that the domain associated with the network packet is valid;determining that the domain associated with the network packet is invalid; anddetermining that the domain associated with the network packet requires an elevated scrutiny.
  • 14. The method of claim 13, wherein the elevated scrutiny includes applying a packet capture (PCAP) to further network packets associated with the domain.
  • 15. The method of claim 9, wherein the updating the security policy includes one or more of the following: generating an enforcement policy associated with the group;collecting Packet Capture (PCAP) to analyze contents of the network packet associated with the group; andmodifying a monitoring policy associated with the at least one group.
  • 16. A system for improving analytics in a distributed network, the system comprising: a hardware processor executing instructions stored in memory, the instructions comprising: executing a security policy on a network packet, wherein the security policy is associated with a group;collecting network information from the network packet;generating a result from an analysis;performing the analysis, the analysis including analyzing the network information with additional group information from the security policy, the analyzing including examining communications including network packets between at least some hosts in a group, the analyzing further including identifying patterns indicative of malicious activity in the communications, wherein the analyzing includes at least one of: determining Domain Name System (DNS) information for the network packet;based on the DNS information, determining if a Domain Generation Algorithm (DGA) was used to generate a domain name of a domain associated with the network packet; andbased on log information associated with at least one group, checking the network information for security threats;defining the security policy, the security policy applying to the group, each host of the group having a similar security attribute associated with group security attributes of the group;updating the security policy based on the generated result, wherein the updating includes at least one of: performing deep packet inspection on the communications;blocking network communications to an infected host in the group;generating an enforcement policy associated with the group;applying Packet Capture (PCAP) to analyze contents of the network packet associated with at least one group; andmodifying a monitoring policy associated with the group;collecting at least one of application metadata, application information, and contextual information related to an application associated with another host in the group; andproviding the collected information; wherein analyzing the network information correlated with the security policy includes: analyzing network packets between a first host in the group and a second host in the group;analyzing network packets between a third host in the group and a fourth host in a second group; andanalyzing connections between the group and the second group; wherein the network information from the network packets regarding a current state of the distributed network is dynamic and changing over time.
US Referenced Citations (247)
Number Name Date Kind
6253321 Nikander et al. Jun 2001 B1
6484261 Wiegel Nov 2002 B1
6578076 Putzolu Jun 2003 B1
6765864 Natarajan et al. Jul 2004 B1
6970459 Meier Nov 2005 B1
6981155 Lyle et al. Dec 2005 B1
7028179 Anderson et al. Apr 2006 B2
7058712 Vasko et al. Jun 2006 B1
7062566 Amara et al. Jun 2006 B2
7096260 Zavalkovsky et al. Aug 2006 B1
7373524 Motsinger et al. May 2008 B2
7397794 Lacroute et al. Jul 2008 B1
7464407 Nakae et al. Dec 2008 B2
7467408 O'Toole, Jr. Dec 2008 B1
7475424 Lingafelt Jan 2009 B2
7516476 Kraemer et al. Apr 2009 B1
7519062 Kloth et al. Apr 2009 B1
7620986 Jagannathan et al. Nov 2009 B1
7694181 Noller et al. Apr 2010 B2
7725937 Levy May 2010 B1
7742414 Iannaccone et al. Jun 2010 B1
7774837 McAlister Aug 2010 B2
7849495 Huang et al. Dec 2010 B1
7900240 Terzis et al. Mar 2011 B2
7904454 Raab Mar 2011 B2
7996255 Shenoy et al. Aug 2011 B1
8051460 Lum et al. Nov 2011 B2
8112304 Scates Feb 2012 B2
8254381 Allen Aug 2012 B2
8259571 Raphel et al. Sep 2012 B1
8291495 Burns et al. Oct 2012 B1
8296459 Brandwine et al. Oct 2012 B1
8307422 Varadhan et al. Nov 2012 B2
8321862 Swamy et al. Nov 2012 B2
8353021 Satish et al. Jan 2013 B1
8369333 Hao et al. Feb 2013 B2
8396986 Kanada et al. Mar 2013 B2
8429647 Zhou Apr 2013 B2
8468113 Harrison et al. Jun 2013 B2
8490153 Bassett et al. Jul 2013 B2
8494000 Nadkarni Jul 2013 B1
8499330 Albisu Jul 2013 B1
8528091 Bowen et al. Sep 2013 B2
8565118 Shukla et al. Oct 2013 B2
8612744 Shieh Dec 2013 B2
8661434 Liang et al. Feb 2014 B1
8677496 Wool Mar 2014 B2
8688491 Shenoy et al. Apr 2014 B1
8726343 Borzycki et al. May 2014 B1
8730963 Grosser, Jr. et al. May 2014 B1
8798055 An Aug 2014 B1
8813169 Shieh et al. Aug 2014 B2
8813236 Saha et al. Aug 2014 B1
8819762 Harrison et al. Aug 2014 B2
8898788 Aziz et al. Nov 2014 B1
8935457 Feng et al. Jan 2015 B2
8938782 Sawhney et al. Jan 2015 B2
8990371 Kalyanaraman et al. Mar 2015 B2
9009829 Stolfo et al. Apr 2015 B2
9015299 Shah Apr 2015 B1
9027077 Bharali et al. May 2015 B1
9036639 Zhang May 2015 B2
9060025 Xu Jun 2015 B2
9141625 Thornewell et al. Sep 2015 B1
9191327 Shieh Nov 2015 B2
9258275 Sun et al. Feb 2016 B2
9294302 Sun et al. Mar 2016 B2
9294442 Lian et al. Mar 2016 B1
9361089 Bradfield et al. Jun 2016 B2
9380027 Lian et al. Jun 2016 B1
9407602 Feghali et al. Aug 2016 B2
9521115 Woolward Dec 2016 B1
9609083 Shieh Mar 2017 B2
9621595 Lian et al. Apr 2017 B2
9680852 Wager et al. Jun 2017 B1
9762599 Wager et al. Sep 2017 B2
10009317 Woolward Jun 2018 B2
10009381 Lian et al. Jun 2018 B2
10091238 Shieh et al. Oct 2018 B2
20020031103 Wiedeman et al. Mar 2002 A1
20020066034 Schlossberg et al. May 2002 A1
20030014665 Anderson et al. Jan 2003 A1
20030055950 Cranor et al. Mar 2003 A1
20030177389 Albert et al. Sep 2003 A1
20040062204 Bearden et al. Apr 2004 A1
20040095897 Vafaei May 2004 A1
20040172557 Nakae et al. Sep 2004 A1
20050021943 Ikudome et al. Jan 2005 A1
20050033989 Poletto et al. Feb 2005 A1
20050060573 D'Souza Mar 2005 A1
20050114829 Robin et al. May 2005 A1
20050190758 Gai Sep 2005 A1
20050201343 Sivalingham et al. Sep 2005 A1
20050246241 Irizarry, Jr. et al. Nov 2005 A1
20050283823 Okajo Dec 2005 A1
20060005228 Matsuda Jan 2006 A1
20060037077 Gadde et al. Feb 2006 A1
20060050696 Shah et al. Mar 2006 A1
20060137009 Chesla Jun 2006 A1
20070016945 Bassett et al. Jan 2007 A1
20070019621 Perry et al. Jan 2007 A1
20070022090 Graham Jan 2007 A1
20070064617 Reves Mar 2007 A1
20070079308 Chiaramonte et al. Apr 2007 A1
20070130566 van Rietschote et al. Jun 2007 A1
20070168971 Royzen et al. Jul 2007 A1
20070192861 Varghese et al. Aug 2007 A1
20070192863 Kapoor et al. Aug 2007 A1
20070198656 Mazzaferri et al. Aug 2007 A1
20070239987 Hoole et al. Oct 2007 A1
20070271612 Fang et al. Nov 2007 A1
20070277222 Pouliot Nov 2007 A1
20080016339 Shukla Jan 2008 A1
20080016550 McAlister Jan 2008 A1
20080083011 McAlister et al. Apr 2008 A1
20080086772 Chesla Apr 2008 A1
20080155239 Chowdhury et al. Jun 2008 A1
20080163207 Reumann et al. Jul 2008 A1
20080229382 Vitalos Sep 2008 A1
20080239961 Hilerio Oct 2008 A1
20080301770 Kinder Dec 2008 A1
20080307110 Wainner et al. Dec 2008 A1
20090077621 Lang et al. Mar 2009 A1
20090083445 Ganga Mar 2009 A1
20090103524 Mantripragada et al. Apr 2009 A1
20090138316 Weller et al. May 2009 A1
20090165078 Samudrala et al. Jun 2009 A1
20090182835 Aviles et al. Jul 2009 A1
20090190585 Allen Jul 2009 A1
20090249470 Litvin et al. Oct 2009 A1
20090260051 Igakura Oct 2009 A1
20090268667 Gandham et al. Oct 2009 A1
20090328187 Meisel Dec 2009 A1
20100043068 Varadhan et al. Feb 2010 A1
20100064341 Aldera Mar 2010 A1
20100071025 Devine et al. Mar 2010 A1
20100088738 Birnbach Apr 2010 A1
20100095367 Narayanaswamy Apr 2010 A1
20100125900 Dennerline et al. May 2010 A1
20100189110 Kambhampati et al. Jul 2010 A1
20100191863 Wing Jul 2010 A1
20100192223 Ismael et al. Jul 2010 A1
20100192225 Ma Jul 2010 A1
20100199349 Ellis Aug 2010 A1
20100208699 Lee et al. Aug 2010 A1
20100228962 Simon et al. Sep 2010 A1
20100235880 Chen et al. Sep 2010 A1
20100274970 Treuhaft et al. Oct 2010 A1
20100281539 Burns et al. Nov 2010 A1
20100287544 Bradfield et al. Nov 2010 A1
20100333165 Basak et al. Dec 2010 A1
20110003580 Belrose et al. Jan 2011 A1
20110022812 van der Linden et al. Jan 2011 A1
20110069710 Naven et al. Mar 2011 A1
20110072486 Hadar et al. Mar 2011 A1
20110075667 Li et al. Mar 2011 A1
20110090915 Droux et al. Apr 2011 A1
20110113472 Fung et al. May 2011 A1
20110138384 Bozek et al. Jun 2011 A1
20110138441 Neystadt et al. Jun 2011 A1
20110184993 Chawla et al. Jul 2011 A1
20110225624 Sawhney et al. Sep 2011 A1
20110249679 Lin et al. Oct 2011 A1
20110263238 Riley et al. Oct 2011 A1
20120017258 Suzuki Jan 2012 A1
20120113989 Akiyoshi May 2012 A1
20120130936 Brown et al. May 2012 A1
20120131685 Broch et al. May 2012 A1
20120185913 Martinez et al. Jul 2012 A1
20120207174 Shieh Aug 2012 A1
20120216273 Rolette et al. Aug 2012 A1
20120278903 Pugh Nov 2012 A1
20120284792 Liem Nov 2012 A1
20120297383 Meisner et al. Nov 2012 A1
20120311144 Akelbein et al. Dec 2012 A1
20120311575 Song Dec 2012 A1
20120324567 Couto Dec 2012 A1
20130019277 Chang et al. Jan 2013 A1
20130081142 McDougal et al. Mar 2013 A1
20130086383 Galvao de Andrade et al. Apr 2013 A1
20130086399 Tychon et al. Apr 2013 A1
20130097692 Cooper et al. Apr 2013 A1
20130145465 Wang et al. Jun 2013 A1
20130151680 Salinas et al. Jun 2013 A1
20130152187 Strebe et al. Jun 2013 A1
20130166490 Elkins et al. Jun 2013 A1
20130166720 Takashima et al. Jun 2013 A1
20130219384 Srinivasan et al. Aug 2013 A1
20130223226 Narayanan et al. Aug 2013 A1
20130250956 Sun et al. Sep 2013 A1
20130263125 Shamsee et al. Oct 2013 A1
20130275592 Xu et al. Oct 2013 A1
20130276092 Sun et al. Oct 2013 A1
20130283336 Macy Oct 2013 A1
20130291088 Shieh et al. Oct 2013 A1
20130298181 Smith Nov 2013 A1
20130298184 Ermagan et al. Nov 2013 A1
20130318617 Chaturvedi et al. Nov 2013 A1
20130343396 Yamashita et al. Dec 2013 A1
20140007181 Sarin et al. Jan 2014 A1
20140022894 Oikawa et al. Jan 2014 A1
20140096229 Bums et al. Apr 2014 A1
20140137240 Smith et al. May 2014 A1
20140153577 Janakiraman et al. Jun 2014 A1
20140157352 Paek et al. Jun 2014 A1
20140250524 Meyers et al. Sep 2014 A1
20140282027 Gao et al. Sep 2014 A1
20140282518 Banerjee Sep 2014 A1
20140283030 Moore Sep 2014 A1
20140298469 Marion et al. Oct 2014 A1
20140310765 Stuntebeck et al. Oct 2014 A1
20140344435 Mortimore, Jr. et al. Nov 2014 A1
20150047046 Pavlyushchik Feb 2015 A1
20150058983 Zeitlin et al. Feb 2015 A1
20150082417 Bhagwat et al. Mar 2015 A1
20150124606 Alvarez May 2015 A1
20150163088 Anschutz Jun 2015 A1
20150180894 Sadovsky Jun 2015 A1
20150186296 Guidry Jul 2015 A1
20150229641 Sun et al. Aug 2015 A1
20150249676 Koyanagi et al. Sep 2015 A1
20150269383 Lang et al. Sep 2015 A1
20150295943 Malachi Oct 2015 A1
20160028851 Shieh Jan 2016 A1
20160191466 Pernicha Jun 2016 A1
20160191545 Nanda Jun 2016 A1
20160203331 Khan Jul 2016 A1
20160294774 Woolward et al. Oct 2016 A1
20160294875 Lian et al. Oct 2016 A1
20160323245 Shieh et al. Nov 2016 A1
20160337390 Sridhara et al. Nov 2016 A1
20160350105 Kumar et al. Dec 2016 A1
20170005986 Barisal et al. Jan 2017 A1
20170063795 Lian et al. Mar 2017 A1
20170134422 Shieh et al. May 2017 A1
20170168864 Ross et al. Jun 2017 A1
20170180421 Shieh et al. Jun 2017 A1
20170195454 Shieh Jul 2017 A1
20170208100 Lian et al. Jul 2017 A1
20170223033 Wager et al. Aug 2017 A1
20170223038 Wager et al. Aug 2017 A1
20170279770 Woolward et al. Sep 2017 A1
20170339188 Jain et al. Nov 2017 A1
20170374032 Woolward et al. Dec 2017 A1
20170374101 Woolward Dec 2017 A1
20180005296 Eades et al. Jan 2018 A1
20180191779 Shieh et al. Jul 2018 A1
Foreign Referenced Citations (12)
Number Date Country
201642616 Dec 2016 TW
201642617 Dec 2016 TW
201642618 Dec 2016 TW
201703483 Jan 2017 TW
201703485 Jan 2017 TW
WO2002098100 Dec 2002 WO
WO2016148865 Sep 2016 WO
WO2016160523 Oct 2016 WO
WO2016160533 Oct 2016 WO
WO2016160595 Oct 2016 WO
WO2016160599 Oct 2016 WO
WO2017100365 Jun 2017 WO
Non-Patent Literature Citations (26)
Entry
Specification, U.S. Appl. No. 14/673,679, filed Mar. 30, 2015.
Specification, U.S. Appl. No. 14/673,640, filed Mar. 30, 2015.
Specification, U.S. Appl. No. 14/677,827, filed Apr. 2, 2015.
Specification, U.S. Appl. No. 14,657,282, filed Mar. 13, 2015.
International Search Report dated May 3, 2016 in Patent Cooperation Treaty Application No. PCT/US2016/024116 filed Mar. 24, 2016.
International Search Report dated May 3, 2016 in Patent Cooperation Treaty Application No. PCT/US2016/024300 filed Mar. 25, 2016.
International Search Report dated May 3, 2016 in Patent Cooperation Treaty Application No. PCT/US2016/024053 filed Mar. 24, 2016.
International Search Report dated May 6, 2016 in Patent Cooperation Treaty Application No. PCT/US2016/019643 filed Feb. 25, 2016.
Dubrawsky, Ido, “Firewall Evolution—Deep Packet Inspection,” Symantec, Created Jul. 28, 2003; Updated Nov. 2, 2010, symantec.com/connect/articles/firewall-evolution-deep-packet-inspection.
Non-Final Office Action, dated Jul. 6, 2016, U.S. Appl. No. 15/151,303, filed May 10, 2016.
Final Office Action, dated Jul. 7, 2016, U.S. Appl. No. 14/877,836, filed Oct. 7, 2015.
Non-Final Office Action, dated Jul. 25, 2016, U.S. Appl. No. 15/090,523, filed Apr. 4, 2016.
Notice of Allowance, filed Jul. 27, 2016, U.S. Appl. No. 15/080,519, filed Mar. 24, 2016.
Non-Final Office Action, dated Sep. 16, 2016, U.S. Appl. No. 15/209,275, filed Jul. 13, 2016.
Non-Final Office Action, dated May 18, 2016, U.S. Appl. No. 14/964,318, filed Dec. 9, 2015.
International Search Report dated Jun. 20, 2016 in Patent Cooperation Treaty Application No. PCT/US2016/024310 filed Mar. 25, 2016, pp. 1-9.
“Feature Handbook: NetBrain® Enterprise Edition 6.1” NetBrain Technologies, Inc., Feb. 25, 2016, 48 pages.
Arendt, Dustin L. et al., “Ocelot: User-Centered Design of a Decision Support Visualization for Network Quarantine”, IEEE Symposium on Visualization for Cyber Security (VIZSEC), Oct. 25, 2015, 8 pages.
“International Search Report” and “Written Opinion of the International Searching Authority,” Patent Cooperation Treaty Application No. PCT/US2016/065451, dated Jan. 12, 2017, 20 pages.
Notice of Allowance, dated Nov. 17, 2016, U.S. Appl. No. 14/877,836, filed Oct. 7, 2015.
Notice of Allowance, dated Nov. 29, 2016, U.S. Appl. No. 15/151,303, filed May 10, 2016.
Final Office Action, dated Nov. 14, 2016, U.S. Appl. No. 14/964,318, filed Dec. 9, 2015.
Non-Final Office Action, dated Jan. 5, 2017, U.S. Appl. No. 15/348,978, filed Nov. 10, 2016.
Notice of Allowance, dated Feb. 1, 2017, U.S. Appl. No. 15/090,523, filed Apr. 4, 2016.
Maniar, Neeta, “Centralized Tracking and Risk Analysis of 3rd Party Firewall Connections,” SANS Institute InfoSec Reading Room, Mar. 11, 2005, 20 pages.
Hu, Hongxin et al., “Detecting and Resolving Firewall Policy Anomalies,” IEEE Transactions on Dependable and Secure Computing, vol. 9, No. 3, May/Jun. 2012, pp. 318-331.
Related Publications (1)
Number Date Country
20160269442 A1 Sep 2016 US