Moving RapidScan to the new Infrastructure

Next Steps

Integration with Assessment Web API

The new Assessment WebAPI is currently being implemented.

• Repository Name: Generic.WebAPI.RapidScan (must be changed to Generic.WebAPI.Assessment)

• Solution Name: AssessmentWebAPI

• URL: https://assessment.mobilize.net/api

Integration with the Assessment Model

Differences between the Generic Scanner Output and the Assessment Model

Generic Scanner Output	Assessment Model
Keyword.Technology	NONE

Plan

• PBI to modify RapidScan in order to generate .pam files, which should be read from the AssessmentWebAPI in order to generate the reports

Changes for the Generic Scanner

Implementation of a Generic UI

Implementation of a Generic Bundle

Currently, RapidScan does not need a license to be run. We should look at the CodeProcessor property named RequiresALicense

Check if there is a conflict between not needing the license and then requiring a license in a new version (because of the Auto Update feature of the new infrastructure):

We think maybe auto-update can be Off in the versions which do not require a license

Plan

• Implement the Bundle for RapidScan

  • Use RequiresLicense in ICodeProcessor interface

• Eventually: include a license in the download

Integration with the new Telemetry

There are multiple fields which are sent from the old Telemetry service (used by RapidScan) but is not sent from the new Telemetry Service. These are some of them

• Computer Name

• RunAsAdmin

• System CPU

• System Ram

Additionally, the old Telemetry service (used by RapidScan) sents the number of files from each extension. However, the new Telemetry service only sents the extensions found.

This data related to the extensions found is gathered by the CodeProcessor

Plan

• Add these fields to the generic telemetry (all products should sent this fields)

• Prepare the Telemetry of RapidScan in order to sent the number of files from each extension

Plan

Assessment Model

• Create the Assessment Web API

• Create the Assessment Database

• GenericScanner

  • Integrate with the Assessment Model

• Create "Upload Assessment Model" endpoint in Assessment Web API

• Implement "Upload Assesment Model" feature in Controller

Integration with the new Infrastructure

• Generic Telemetry

  • Add fields to the generic telemetry (all products should sent these fields: ComputerName, RunAsAdmin, SystemCPU, SystemRam)

  • Prepare the Telemetry of RapidScan in order to sent the number of files from each extension

• Bundle

  • Implement the Bundle for RapidScan

    • Use RequiresLicense in ICodeProcessor interface

    • The auto-update feature might be Off for this version

  • Eventually: include a license in the download

    • The auto-update feature might be On for this version

• Generic UI

  • Prepare the UI/UX wireframes with Nathalia

• Implement new Infrastructure Interfaces

  • Implement ICodeProcessor

  • Implement ICodeProcessorWorker

  • Check the status of the VBUC Light Scanner (will they implement an ICodeProcessorWorker?)

    • We could make the same CodeProcessorWorker run the Assessment and the VBUC Light Scanner, but this should be changed eventually

    • We could work with the VBUC Team to implement the ICodeProcessorWorker

Priorities for the Integration with the new Infrastructure

1. UX/UI for RapidScan

2. UX/UI for Generic Scanner Infrastructure

3. Adjustments required for the Controller

   1. Telemetry

4. Prepare the Bundle