Detailed Workflow

Document created by RSA Information Design and Development on Apr 7, 2017Last modified by RSA Information Design and Development on Apr 7, 2017
Version 2Show Document
  • View in full screen mode
  

The following figure depicts the Malware Spectrum process flow and the interactions between all the components that exist in Security Analytics.

malware spectrum workflow

The overall workflow for continuous submission is detailed in the below steps:

  1. NextGen Session Query at specific interval: Malware Analysis collects sessions from the NextGen service that are tagged with a spectrum meta key (spectrum.consume or spectrum.consume11).
  2. Malware Analysis service requests the NextGen Source to pre-cache the sessions. The session contents are pre-cached at the Decoder.

  3. Malware Analysis service queries the pre-cached content from the NextGen service.

  4. If the session content contains files, the Malware Analysis service proceeds with Static, Community, and Sandbox Analysis.

Note: The Sandbox Analysis is performed only if any of the Static, Community, and NextGen score results above the Threshold value (the default is 50).

  1. If any of the Static, Community, and NextGen score is greater than or equal to the threshold (default is 50), proceed with Sandbox Analysis.

Note: Events will be saved only if at least one score is greater than or equal to 41.

Next Topic:Scoring Modules
You are here
Table of Contents > How Malware Analysis Works > Detailed Workflow

Attachments

    Outcomes