Changes between Version 33 and Version 34 of ExDescLang


Ignore:
Timestamp:
Oct 11, 2010 4:31:53 PM (14 years ago)
Author:
sunshine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ExDescLang

    v33 v34  
    106106 * '''Timeline of events: '''
    107107
    108    [[Image(wormwf.jpg)]]
     108 
    109109
    110    (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).
     110 * '''Invariants:'''
    111111
    112    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:
    113      * scan event generates traffic from A to B that exploits a vulnerability at B
    114      * infection event at B executes some code that places a copy of malware at B with ability to auto-start
    115  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.
     112= TODO =
    116113
    117  * '''Invariants:''' There are some in definition of topology and timeline above. No additional ones are needed here.
     114 * How is ordering of events defined?
     115 * What do we denote "all", "each", "none", "some"
     116 * How do we denote state transitions because of an event, vs. self-initiated, vs. those that emit an event