You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/topics/process_models/cs/events.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,11 @@ vulnerability lifecycle models can be found in
22
22
[The global vulnerability discovery and disclosure system: a thematic system dynamics approach](http://dspace.lib.cranfield.ac.uk/handle/1826/12665){:target="_blank"}
23
23
by P. S. Lewis.
24
24
We are primarily interested in events that are usually observable to the
25
-
stakeholders of a CVD case. Stakeholders include software
26
-
vendors, vulnerability finder/reporters, coordinators, and
27
-
deployers [CERT Guide to CVD](https://certcc.github.io/CERT-Guide-to-CVD){:target="_blank"}. A summary of this model comparison is
[coordinators](https://certcc.github.io/CERT-Guide-to-CVD/topics/roles/coordinator/){:target="_blank"}, and
29
+
[deployers](https://certcc.github.io/CERT-Guide-to-CVD/topics/roles/deployer/){:target="_blank"}. A summary of this model comparison is
28
30
shown in the Table below.
29
31
30
32
|[Arbaugh et al.](https://doi.org/10.1109/2.889093){:target="_blank"} |[Frei et al.](http://dx.doi.org/10.1007/978-1-4419-6967-5_6){:target="_blank"} |[Bilge et al.](https://doi.org/10.1145/2382196.2382284){:target="_blank"} | Our Model |
0 commit comments