Changes between Version 13 and Version 14 of ExDescLang

Timestamp:

Oct 11, 2010 1:50:27 PM (14 years ago)

Author:

sunshine

Comment:

--

ExDescLang

@@ -41 +41 @@
 Dimensions:
  * Logical topology: 
-[[Image(wormobj.jpg)]]
- (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.)
+   [[Image(wormobj.jpg)]]
+   (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.)
  * Timeline of events: 
-[[Image(wormwf.jpg)]]
- (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)
+   [[Image(wormwf.jpg)]]
+   (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)
 
-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:
-   * scan event generates traffic from A to B that exploits a vulnerability at B
-   * infection event at B executes some code that places a copy of malware at B with ability to auto-start
+   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:
+     * scan event generates traffic from A to B that exploits a vulnerability at B
+     * infection event at B executes some code that places a copy of malware at B with ability to auto-start
 
  * Invariants: