| | 96 | This example used two metadescriptions. Let's go through each of them: |
| | 97 | |
| | 98 | === Cache poisoning metadescription === |
| | 99 | |
| | 100 | Dimensions: |
| | 101 | * '''Logical topology:''' |
| | 102 | |
| | 103 | [[Image(wormobj.jpg)]] |
| | 104 | |
| | 105 | (in English: There must be two sets of hosts, at least one infected host in infected set and at least one vulnerable host in vulnerable set. There can be a third set of hosts that are not vulnerable or infected. These sets are disjoint.) |
| | 106 | |
| | 107 | Note: I haven't said if these objects are nodes, resources or what. I should have a way of saying this. |
| | 108 | |
| | 109 | * '''Timeline of events: ''' |
| | 110 | |
| | 111 | [[Image(wormwf.jpg)]] |
| | 112 | |
| | 113 | (in English: Each infected host generates scan events that target a vulnerable host - double line means one object acts upon another. There is at least one such event for a vulnerable host and at least one pair of scan+vulnerable host in the experiment. Once an infection event occurs on vulnerable host it transitions to an infected state. An infected host may scan other, non-vulnerable hosts). |
| | 114 | |
| | 115 | Note that I haven't yet defined what scan and infection events mean. I have to do this somewhere but I think the right place for this would be a common repository of domain knowledge rather than attaching these per experiment class since many classes of experiments may need same definitions. Ultimately what I'd like to say in these definitions in plain English is: |
| | 116 | * scan event generates traffic from A to B that exploits a vulnerability at B |
| | 117 | * infection event at B executes some code that places a copy of malware at B with ability to auto-start |
| | 118 | Also note that I haven't said if each infected hosts scans ALL or SOME vulnerable hosts and how many. We should have a mechanism to specify this. Same comment goes for any "acts upon" relationship. |
| | 119 | |
| | 120 | * '''Invariants:''' There are some in definition of topology and timeline above. No additional ones are needed here. |
