Software Victimology (Part 1)

What prompted me to found this discipline (that is supposed to be a sister discipline of software criminology, software security, secure code construction and software defect construction) is understanding that some software components are innocent victims of other component coding mistakes or deliberate subversion and some start as a part of crimeware but eventually become victims themselves (they crash, hang, spike, leak, are dumped, subverted, etc.). I would also like to borrow and reuse the neglected term victimware here in a broad sense. More on this later as I have to switch to software trace analysis patterns.

- Dmitry Vostokov @ -

One Response to “Software Victimology (Part 1)”

  1. Crash Dump Analysis » Blog Archive » Malware Analysis Patterns Says:

    […] inclusion of victimware is necessary because of the effects of defective […]

Leave a Reply

You must be logged in to post a comment.