GB2585192A - Impeding location threat propagation in computer networks - Google Patents
Impeding location threat propagation in computer networks Download PDFInfo
- Publication number
- GB2585192A GB2585192A GB1909425.9A GB201909425A GB2585192A GB 2585192 A GB2585192 A GB 2585192A GB 201909425 A GB201909425 A GB 201909425A GB 2585192 A GB2585192 A GB 2585192A
- Authority
- GB
- United Kingdom
- Prior art keywords
- network
- malware
- computer systems
- computer
- propagation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000004891 communication Methods 0.000 claims abstract description 47
- 208000015181 infectious disease Diseases 0.000 claims abstract description 43
- 238000000034 method Methods 0.000 claims abstract description 39
- 230000001681 protective effect Effects 0.000 claims abstract description 19
- 238000004590 computer program Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 5
- 230000009471 action Effects 0.000 claims description 4
- 230000002123 temporal effect Effects 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 8
- 230000000903 blocking effect Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 5
- 230000002596 correlated effect Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000000875 corresponding effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013213 extrapolation Methods 0.000 description 2
- 238000005067 remediation Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000116 mitigating effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000037361 pathway Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 208000024891 symptom Diseases 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/145—Countermeasures against malicious traffic the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/552—Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/142—Network analysis or design using statistical or mathematical methods
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Virology (AREA)
- General Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Mathematical Analysis (AREA)
- Probability & Statistics with Applications (AREA)
- Pure & Applied Mathematics (AREA)
- Mathematical Physics (AREA)
- Mathematical Optimization (AREA)
- Human Computer Interaction (AREA)
- Algebra (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A computer implemented method to block malware propagation in a network 202 of computer systems comprises: receiving, for each of several time periods, a temporal model 504 of the network, such as a graph having nodes and edges, identifying communications between systems and a malware infection state of each system; identifying a physical location where one or more systems are involved in propagation of the malware, the identification being based on changes to malware infection states of computer systems, colocation of systems, and communications therebetween identified in the models; and implementing protective measures at the location to block malware propagation through the network, such as reconfiguring, disconnecting, precluding access to, or applying an anti-malware service to devices at the location. The method may be carried out by a security component 500 containing a location identifier 506 which generates a map 510 for each model indicating infected 560, remediated 552, 556, 564, and vulnerable 558 systems. The location may be that of a router, switch, bridge, domain name server, proxy, gateway, etc. Location identification may involve correlating communications data or infection states.
Description
Impeding Location Threat Propagation In Computer Networks The present invention relates to impeding the propagation of a threat through computer networks.
Malicious software, known as malware, threatens computer systems communicating via computer networks. Malware can be propagated between computer systems across communications links such as physical, virtual, wired or wireless network communications. As computer systems within a network are infected with malware, a rate of spread of malware can increase presenting a threat to potentially all network-connected devices.
Thus, there is a challenge in providing an effective approach to impeding the propagation of such threats within computer networks.
According to a first aspect of the present invention, there is a provided a computer implemented method to block malware propagation in a network of computer systems, each computer system in the network having associated location information indicating a physical location, the method comprising: receiving, for each of a plurality of time periods, a model of the network of computer systems identifying communications therebetween and a malware infection state of each computer system; identifying a physical location at which one or more computer systems are involved in propagation of the malware, the identification being based on changes to malware infection states of computer systems; colocation of computer systems and the communications therebetween identified in the models; and implementing protective measures in respect to the physical location so as to block propagation of the malware through the network.
Preferably, the identified location is a location of one or more of one of: a computer system in the network; and a network element in the network.
Preferably, the network element includes one or more of: a network appliance; a router; a switch; a bridge; a domain name server; a proxy; a gateway; an access point; a network interface card; a repeater; and a virtualised network device.
Preferably, identifying a physical location includes performing a plurality of correlation processes, each correlation process correlating one or more of: data about communications 30 between computer systems in the network; and malware infection states of computer systems, the physical location being identified based on the correlations.
Preferably, data about communications between computer systems includes one or more of: characteristics of communications between computer systems in the network; characteristics of endpoints of communications between computer systems in the network; changes to communication characteristics over time.
Preferably, malware infection states of computer systems include: an infected state in which a computer system is subject to a malware infection; a vulnerable state in which a 5 computer system is susceptible to malware infection; and a remediated state in which a computer system is remediated of a malware infection.
Preferably, the method further comprises: identifying, for a network appliance in the computer network through which a set of sub-networks of the network communicate, a subnetwork in which a proportion of computer systems infected by the malware meets a predetermined threshold; and responsive to the identification, implementing protective measures in respect to the network appliance so as to block propagation of the malware through the appliance.
Preferably, the protective measures include performing an action in respect of the physical location, wherein the action includes one or more of: reconfiguring one or more devices at the physical location; disconnecting one or more devices at the physical location; precluding access to devices at the physical location by at least a subset of computer systems in the network; and applying an anti-malware service to devices at the physical location, so as to block propagation of the malware.
Preferably, each model is a graph data structure having computer systems as nodes and 20 communications therebetween as edges.
According to a second aspect of the present invention, there is a provided a computer system including a processor and memory storing computer program code for performing the steps of the method set out above.
According to a third aspect of the present invention, there is a provided a computer system including a processor and memory storing computer program code for performing the steps of the method set out above.
Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which: Figure 1 is a block diagram a computer system suitable for the operation of 30 embodiments of the present invention; Figure 2 is a component diagram of an arrangement for blocking malware propagation in a network in accordance with an embodiment of the present invention; Figure 3 depicts an illustrative embodiment for identifying a common resource according to the arrangement of Figure 2 in accordance with an embodiment of the present invention; Figure 4 is a flowchart of a method to block malware propagation in a network 5 according to an embodiment of the present invention; Figure 5 is a component diagram of an arrangement for blocking malware propagation in a network using location information according to an embodiment of the present invention; Figure 6 is a flowchart of a method to block malware propagation in a network using 10 location information according to an embodiment of the present invention; Figure 7 is a component diagram of an arrangement for blocking malware propagation in a network using a forecast model of the network according to an embodiment of the present invention; and Figure 8 is a flowchart of a method to block malware propagation in a network using a 15 forecast model of the network according to an embodiment of the present invention.
Figure 1 is a block diagram of a computer system suitable for the operation of embodiments of the present invention. A central processor unit (CPU) 102 is communicatively connected to a storage 104 and an input/output (I/O) interface 106 via a data bus 108. The storage 104 can be any read/write storage device such as a random-access memory (RAM) or a non-volatile storage device. An example of a non-volatile storage device includes a disk or tape storage device. The I/O interface 106 is an interface to devices for the input or output of data, or for both input and output of data. Examples of I/O devices connectable to I/O interface 106 include a keyboard, a mouse, a display (such as a monitor) and a network connection.
Figure 2 is a component diagram of an arrangement for blocking malware propagation in a network in accordance with an embodiment of the present invention. A computer network 202 is a means for communication between a each of a plurality of computer systems such as a wired, wireless, cellular, physical, virtualised or logical network or a network comprised of two or more such arrangements as will be apparent to those skilled in the art.
Communicating computer systems include physical and/or virtualised computer systems communicatively connected to the network 202 such as via network interface hardware, virtualised hardware or other suitable means. Computer systems may be connected physically (or in a virtualisation of a physical manner) to one network while being logically connected to another network such as through a tunnelling, virtual network, virtual private network (VPN) or other suitable technology. A particular topology, technology or arrangement of the network 202 is not significant.
A security component 200 is provided as a hardware, firmware, software or combination 5 component arranged to provide security services for the network 202. The security component 200 can be provided as a dedicated physical or virtualised computer system or device, such as a network appliance, apparatus or the like in communication with the network 202. Alternatively, the security component 200 can be provided as a facility, service or function of one or more devices in the network 202 such as network appliances. For example, the security component 200 can be provided as part of a router, switch, gateway, proxy, access point, hub or other network appliances, any or all of which can be virtualised.
The security component 200 is operable to provide services for impeding the propagation of malware between computer systems in the network 200 by blocking malware propagation as will be described below. The security component 200 receives a model 204 of the network of computer systems for each of a plurality of time periods. Thus, the model can be described as a temporal model. For example, a model can be received for each time period according to a predefined schedule. Alternatively, a model can be received for a time period according to one or more trigger conditions such as a security event including a detection of malware within the network. Each model 204 identifies communications between computer systems within the network 202 so as to indicate paths of communication between the computer systems. Additionally, each model 204 identifies, for each computer system represented in the model, a malware infection state of the computer system. In one embodiment, malware infection states indicated in a model for a time period include: an infected state in which a computer system is subject to malware infection during the time period; a vulnerable state in which a computer system is not subject to a malware infection but is also not protected from, or remediated of, the malware infection during the time period; and a remediated state in which a computer system has been remediated of a prior malware infection. In a preferred embodiment, the models are provided as one or more graph data structures in which computer systems are indicated as stateful nodes in a graph with communications therebetween indicated as edges between nodes. For example, the illustrative model 204 depicted in Figure 2 includes nodes representing computer systems with edges representing network communications. Further, each node in Figure 2 indicates its malware infection state such that a hatched node is remediated, a black node is infected and a white node is vulnerable.
The models 204 can be specifically generated for the network by a modelling, reporting, analysis or other suitable component. For example, determination of computer systems in the network can be made by monitoring network traffic or through predefined network topology or configuration information. Further, communication between such systems can be determined based on network traffic such as routing information, traffic target/destination information and the like. A malware infection state of each computer system can be provided by, for example, security services provided with or for each computer system such as antimalware services. Such services can determine, based on malware detection rules, the existence of malware within a computer system (a state of infected). Similarly, a remediation of malware can indicate a state of remediated. The identification of computer systems being in a vulnerable state can be determined using a conservative approach to include computer systems being in neither the infected nor remediated states, for example.
The security component 200 includes a common resource identifier 206 as a hardware, software, firmware or combination component for identifying a common resource in the network 202 involved in the propagation of malware. Resources in the network 202 include hardware, software, firmware or combination components such a network elements or computer systems themselves. A network element in the network 202 can include, for example: a network appliance; a router; a switch; a bridge; a domain name server; a proxy; a gateway; an access point; a network interface card; a repeater; a virtualised network device, and/or other network elements as will be apparent to those skilled in the art. Thus, the common resource identifier 206 is operable to identify a resource in the network 204 that is involved in the propagation of malware and in respect of which protective measures can be implemented so as to block the propagation of the malware. Thus, a mitigator component 208 is provided as a hardware, firmware, software or combination component for deploying protective measures for the network 202 to block propagation of malware.
For example, a network appliance identified as a resource common to communication by multiple infected computer systems in the network 202 can be identified as a common resource involved in the propagation of malware. Protective measures deployed by the mitigator 208 can include, inter alia: precluding access to the appliance; de-provisioning the appliance; reconfiguring the appliance; disconnecting the appliance; precluding access to the common resource by at least a subset of the computer systems; applying an anti-malware service to the common resource; and other protective measures as will be apparent to those skilled in the art. Further notably, protective measures in respect of an identified common resource can include malware remediation and/or protection deployed at computer systems themselves where the computer systems are involved in communication with, or via, the identified common resource.
In a preferred embodiment, the common resource identifier 206 identifies the common resource based on a plurality of correlation processes, each of which correlates one or more of: data about communications between computer systems in the network; and malware infection states of computer systems in the network. Data about communications between computer systems can include one or more of: characteristics of communications between computer systems; characteristics of endpoints of communications between computer systems; and changes to communication characteristics over time (i.e. across multiple models). Examples of such correlation will be described below with respect to Figure 3.
In a preferred embodiment, the network 202 is comprised of a plurality of sub-networks such as subnets, and the security component 202 is additionally operable to identify a subnet in which a proportion computer systems communicating via the subnet that are in an infected state exceeds a predetermined threshold. Responsive to such an identification, the security component 202 implements protective measures in respect of a network appliance through which communications via the identified subnet pass.
Thus, in use, the security component 200 is operable to identify a common resource in the network 202 involved in the propagation of malware through the network 202, and to implement protective measures to block propagation of the malware through the network 202.
Figure 3 depicts an illustrative embodiment for identifying a common resource according to the arrangement of Figure 2 in accordance with an embodiment of the present invention. In the arrangement of Figure 3, correlations of data based on the temporal models 204 are performed in three ways. A threat being monitored in the illustrative embodiment of Figure 3 is the propagation of malware in a logical network where each node represents a computer system each edge indicates that two nodes directly communicate with each other via a network 202.
According to one exemplary correlation, the network 202 is comprised of a plurality of subnets and identifiers of infected computer systems can be correlated against subnets of the network 202 over time to generate a heat map 306 as a data structure representation of a degree of infection of subnets over time. The horizontal axis of the heatmap 306 corresponds to the progression of time and the vertical axis corresponds to each subnet in the network 202. Darker portions of the heatmap indicate greater extent of infection by computer systems within a corresponding subnet. The correlation by way of the heatmap 306 serves to identify subnets (and, therefore, resources of such subnets) involved in the propagation of the malware over time. Further, the route of propagation between subnets can be determined, so serving to identify a common network resource involved in such propagation over time.
A second exemplary correlation uses identifiers of infected computer systems correlated against request pathway data 304 such as server and URL (uniform resource locator) information over a corresponding period of time or a longer period of time in case some events shown in a device request data were linked to the devices being infected subsequently. All URLs involved in request data of infected computer systems can then be correlated with data identifying known malicious domain name service (DNS) servers to identify one or more malicious DNS servers accessed by the computer systems during the 10 malware propagation. Such a DNS server would thus constitute a common resource.
A third exemplary correlation uses identifiers of infected computer systems correlated with computer system connection data to determine which systems may be launching superfluous requests in a short period of time. Such behaviour can indicate a source of distributed denialof-service (DDoS) attack and provides for an identification of events leading to such an attack. In particular, malware infection is a common technique used to launch a DDoS attack. If a malware infection is not treated, seeking to address the symptoms of a DDoS attack may not be sufficient because entities with malicious control of infected computer systems can persist in their use of such systems to launch new DDoS attacks.
Figure 4 is a flowchart of a method to block malware propagation in a network according to an embodiment of the present invention. Initially, at step 402, the method receives, for each of a plurality of time periods, a model of the network of computer systems identifying communications therebetween and a malware infection state of each computer system. At step 404 the method identifies a common resource in the network involved in propagation of the malware, the identification being based on changes to malware infection states of computer systems and the communications therebetween identified in the models. At step 406, the method implements protective measures in respect to the common resource so as to block propagation of the malware through the network.
Conventional network-wide malware detection and mitigation measures can be undertaken on a topological basis since network components (devices, appliances etc.) may be considered to communicate in accordance with the topology on the network. However, the ability for devices to traverse a network topology and "switch" between networks introduces new challenges for malware propagation control. For example, a singular physical or virtual computer system can switch between multiple networks using virtual private network (VPN) connections or the like, by switching virtualised network configurations (e.g. adding/removing virtual network interface cards (NICs) and virtual network connections that may themselves be provided by an underlying VPN or the like), or by physically changing network (especially as devices are increasingly mobile). Thus, a single device may, momentarily, appear to be communicating via a first network but may subsequently communicate via a second network. Such changes undermine normal malware propagation controls which typically assume ongoing adherence to a fixed network topology.
An embodiment of the present invention seeks address these challenges by employing location information indicating a physical location of a computer system. Figure 5 is a component diagram of an arrangement for blocking malware propagation in a network using location information according to an embodiment of the present invention. Many of the elements of Figure 5 are identical to those described above with respect to Figure 2 and these will not be repeated here. Figure 5 includes a location identifier 506 as a hardware, firmware, software or combination component operable to identify location information indicating a physical location for computer systems represented in the models 504. A physical location of a computer system can be indicated as a geolocation, such as a particular location in geospace. Additionally or alternatively, a physical location can be indicated as a location within a site, building, type of building, container, type of container, relative location or other locations as will be apparent to those skilled in the art.
In one exemplary embodiment, the location identifier 506 is operable to generate a map 510 for each temporal model 504 indicating physical locations of computer systems in the model. Notably, the malware infection state of each computer system in the map 510 can be retained, referenced or discerned. The exemplary map 510 of Figure 5 illustrates twelve computer systems in an infected state of which six are collocated at 560 in the map. A further three systems are collocated with nine vulnerable systems at 554. Further, three groups of remediated systems are indicated at 552, 556 and 564, with one further group of vulnerable systems (comprising a single computer system) at 558. Notably, a map 510 such as that depicted in Figure 5 (or other such suitable representation, record or indication of physical location information for computer systems) is provided for each temporal model 504 such that multiple maps are provided over time.
The location identifier 506 identifies a physical location at which one or more computer systems are involved in propagation of the malware. The physical location involved in propagation is identified based on colocation of computer systems as indicated in the map 510. Further, the physical location is identified based changes to malware infection states of computer systems and communications therebetween, as described above with respect to Figure 2. This, in this way, a location involved in the propagation of malware can be detected and protective measures can be deployed in respect of the identified physical location. For example, in the illustrative example of Figure 5, over time the infection of computer systems at location 554 can be detected to trigger protective measures for devices and systems at location 554 so as to block the propagation of malware at that location. Additionally, proximate locations to the identified location can be protected also, such as location 562 which includes vulnerable computer systems.
Figure 6 is a flowchart of a method to block malware propagation in a network using location information according to an embodiment of the present invention. Initially, at step 602, the method receives, for each of a plurality of time periods, a model of the network of computer systems identifying communications therebetween and a malware infection state of each computer system. At step 604 a physical location at which one or more computer systems are involved in propagation of the malware is identified. The identification at step 604 is based on changes to malware infection states of computer systems; colocation of computer systems and the communications therebetween identified in the models. At step 606, protective measures are implemented in respect to the physical location so as to block propagation of the malware through the network.
Figure 7 is a component diagram of an arrangement for blocking malware propagation in a network using a forecast model of the network according to an embodiment of the present invention. Many of the elements of Figure 7 are identical to those described above with respect to Figure 1 and these will not be repeated here. Figure 7 is enhanced vis-a-vis Figure 1 by the provision of a forecaster component 712 as a hardware, firmware, software or combination component operable to generate forecast models 714 for computer systems in the network 702. The forecaster component 712 receives the temporal models 704 and, based thereon, forecasts network communication and states of infection for computer systems for a plurality of time periods into the future. Thus, each of the forecast models 714 corresponds to a future time period subsequent to the temporal models 704, which can be considered historical models 704. In a preferred embodiment, the forecast models 714 are defined based on an extrapolation of the historical models 704 such that the propagation of malware and the malware infection state of computer systems is predicted by the forecaster 712 based on historical communications between computer systems, the historical malware infection status of computer systems, and how those change over time in the historical models 704.
Accordingly, in the arrangement of Figure 7, the common resource identifier 706 is operable as described above with respect to Figure 1 except that it is operable on the basis of the forecast models 714 such that predicted future state of the network 702 is used to identify a common resource for which protection measures are taken by the mitigator 708. In this way, a future propagation of the malware can be blocked in anticipation.
Figure 8 is a flowchart of a method to block malware propagation in a network using a forecast model of the network according to an embodiment of the present invention. Initially, at step 802, the method receives, for each of a plurality of time periods, a historical model of the network of computer systems identifying communications therebetween and a malware infection state of each computer system. At step 804 the forecaster 712 generates, for each of a plurality of subsequent time periods, a forecast model 714 of the network 702 of computer systems in which each forecast model 714 identifies communications between computer systems and malware infection state of computer systems being determined based on an extrapolation of the set of historical models 704. At step 806 the method identifies a common resource in the network 702 involved in propagation of the malware, the identification being based on changes to malware infection states of computer systems and the communications therebetween identified in the forecast models 714. At step 808 the method implements protective measures in respect to the common resource so as to block propagation of the malware through the network 702.
Insofar as embodiments of the invention described are implementable, at least in part, using a software-controlled programmable processing device, such as a microprocessor, digital signal processor or other processing device, data processing apparatus or system, it will be appreciated that a computer program for configuring a programmable device, apparatus or system to implement the foregoing described methods is envisaged as an aspect of the present invention. The computer program may be embodied as source code or undergo compilation for implementation on a processing device, apparatus or system or may be embodied as object code, for example.
Suitably, the computer program is stored on a carrier medium in machine or device readable form, for example in solid-state memory, magnetic memory such as disk or tape, optically or magneto-optically readable memory such as compact disk or digital versatile disk etc., and the processing device utilises the program or a part thereof to configure it for operation. The computer program may be supplied from a remote source embodied in a communications medium such as an electronic signal, radio frequency carrier wave or optical carrier wave. Such carrier media are also envisaged as aspects of the present invention.
It will be understood by those skilled in the art that, although the present invention has been described in relation to the above described example embodiments, the invention is not limited thereto and that there are many possible variations and modifications which fall within 35 the scope of the invention.
The scope of the present invention includes any novel features or combination of features disclosed herein. The applicant hereby gives notice that new claims may be formulated to such features or combination of features during prosecution of this application or of any such further applications derived therefrom. In particular, with reference to the appended claims, features from dependent claims may be combined with those of the independent claims and features from respective independent claims may be combined in any appropriate manner and not merely in the specific combinations enumerated in the claims.
Claims (10)
- CLAIMS1. A computer implemented method to block malware propagation in a network of computer systems, each computer system in the network having associated location information indicating a physical location, the method comprising: receiving, for each of a plurality of time periods, a model of the network of computer systems identifying communications therebetween and a malware infection state of each computer system; identifying a physical location at which one or more computer systems are involved in 10 propagation of the malware, the identification being based on changes to malware infection states of computer systems; colocation of computer systems and the communications therebetween identified in the models; and implementing protective measures in respect to the physical location so as to block propagation of the malware through the network.
- 2. The method of claim 1 wherein the identified location is a location of one or more of one of: a computer system in the network; and a network element in the network.3. The method of claim 2 wherein the network element includes one or more of: a 20 network appliance; a router; a switch; a bridge; a domain name server; a proxy; a gateway; an access point; a network interface card; a repeater; and a virtualised network device.
- 3. The method of any preceding claim wherein identifying a physical location includes performing a plurality of correlation processes, each correlation process correlating one or 25 more of: data about communications between computer systems in the network; and malware infection states of computer systems, the physical location being identified based on the correlations.
- 4. The method of claim 3 wherein data about communications between computer 30 systems includes one or more of: characteristics of communications between computer systems in the network; characteristics of endpoints of communications between computer systems in the network; changes to communication characteristics over time.
- 5. The method of claim 3 or 4 wherein malware infection states of computer systems 35 include: an infected state in which a computer system is subject to a malware infection; a vulnerable state in which a computer system is susceptible to malware infection; and a remediated state in which a computer system is remediated of a malware infection.
- 6. The method of any preceding claim further comprising: identifying, for a network appliance in the computer network through which a set of sub-networks of the network communicate, a sub-network in which a proportion of computer systems infected by the malware meets a predetermined threshold; and responsive to the identification, implementing protective measures in respect to the network appliance so as to block propagation of the malware through the appliance.
- 7. The method of any preceding claim wherein the protective measures include performing an action in respect of the physical location, wherein the action includes one or more of: reconfiguring one or more devices at the physical location; disconnecting one or more devices at the physical location; precluding access to devices at the physical location by at least a subset of computer systems in the network; and applying an anti-malware service to devices at the physical location, so as to block propagation of the malware.
- 8. The method of any preceding claim wherein each model is a graph data structure having computer systems as nodes and communications therebetween as edges.
- 9. A computer system including a processor and memory storing computer program code for performing the steps of the method of any preceding claim.
- 10. A computer program element comprising computer program code to, when loaded 25 into a computer system and executed thereon, cause the computer to perform the steps of a method as claimed in any of claims 1 to 8.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1909425.9A GB2585192A (en) | 2019-06-30 | 2019-06-30 | Impeding location threat propagation in computer networks |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1909425.9A GB2585192A (en) | 2019-06-30 | 2019-06-30 | Impeding location threat propagation in computer networks |
Publications (2)
Publication Number | Publication Date |
---|---|
GB201909425D0 GB201909425D0 (en) | 2019-08-14 |
GB2585192A true GB2585192A (en) | 2021-01-06 |
Family
ID=67540063
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB1909425.9A Withdrawn GB2585192A (en) | 2019-06-30 | 2019-06-30 | Impeding location threat propagation in computer networks |
Country Status (1)
Country | Link |
---|---|
GB (1) | GB2585192A (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050060562A1 (en) * | 2003-09-12 | 2005-03-17 | Partha Bhattacharya | Method and system for displaying network security incidents |
WO2016190868A1 (en) * | 2015-05-28 | 2016-12-01 | Hewlett Packard Enterprise Development Lp | Processing network data using a graph data structure |
US20180219888A1 (en) * | 2017-01-30 | 2018-08-02 | Splunk Inc. | Graph-Based Network Security Threat Detection Across Time and Entities |
WO2019185404A1 (en) * | 2018-03-25 | 2019-10-03 | British Telecommunications Public Limited Company | Malware infection prediction |
-
2019
- 2019-06-30 GB GB1909425.9A patent/GB2585192A/en not_active Withdrawn
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050060562A1 (en) * | 2003-09-12 | 2005-03-17 | Partha Bhattacharya | Method and system for displaying network security incidents |
WO2016190868A1 (en) * | 2015-05-28 | 2016-12-01 | Hewlett Packard Enterprise Development Lp | Processing network data using a graph data structure |
US20180219888A1 (en) * | 2017-01-30 | 2018-08-02 | Splunk Inc. | Graph-Based Network Security Threat Detection Across Time and Entities |
WO2019185404A1 (en) * | 2018-03-25 | 2019-10-03 | British Telecommunications Public Limited Company | Malware infection prediction |
Also Published As
Publication number | Publication date |
---|---|
GB201909425D0 (en) | 2019-08-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110445770B (en) | Network attack source positioning and protecting method, electronic equipment and computer storage medium | |
Han et al. | Honeymix: Toward sdn-based intelligent honeynet | |
US9160761B2 (en) | Selection of a countermeasure | |
AU2004282937B2 (en) | Policy-based network security management | |
Kalluri et al. | Simulation and impact analysis of denial-of-service attacks on power SCADA | |
US11032302B2 (en) | Traffic anomaly detection for IoT devices in field area network | |
Carlin et al. | Defence for distributed denial of service attacks in cloud computing | |
WO2014063110A1 (en) | Network infrastructure obfuscation | |
Tok et al. | Security analysis of SDN controller-based DHCP services and attack mitigation with DHCPguard | |
Ioulianou et al. | Battery drain denial-of-service attacks and defenses in the Internet of Things | |
US20220239671A1 (en) | Impeding forecast threat propagation in computer networks | |
US20180109555A1 (en) | Inter-domain distributed denial of service threat signaling | |
Ono et al. | A proposal of port scan detection method based on Packet‐In Messages in OpenFlow networks and its evaluation | |
US20220247759A1 (en) | Impeding threat propagation in computer networks | |
US20220272107A1 (en) | Impeding location threat propagation in computer networks | |
CN114500026A (en) | Network traffic processing method, device and storage medium | |
Aborujilah et al. | Security assessment model to analysis DOS attacks in WSN | |
Amin et al. | Edge-computing with graph computation: A novel mechanism to handle network intrusion and address spoofing in SDN | |
GB2585192A (en) | Impeding location threat propagation in computer networks | |
KR20170109949A (en) | Method and apparatus for enhancing network security in dynamic network environment | |
Liatifis et al. | Dynamic risk assessment and certification in the power grid: a collaborative approach | |
Chatterjee | Design and development of a framework to mitigate dos/ddos attacks using iptables firewall | |
Narwal et al. | Game-theory based detection and prevention of DoS attacks on networking node in open stack private cloud | |
KR101772292B1 (en) | Software Defined Network based Network Flooding Attack Detection/Protection Method and System | |
Said et al. | An improved strategy for detection and Prevention IP spoofing attack |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |