Remove the security report's dependency on the Monkey model

[mssalvatore]

Refactor

Component(s) to be refactored

• monkey_island.cc.services.reporting.ReportService

Explanation

The Monkey model has been superseded by the Agent model. Various parts of the Monkey model have been broken out into other components, such as events or signals. Decouple the ReportService from the Monkey model.

Tasks

• Understand the slowest part of report generation and how it scales (0d) @ilija-lazoroski
• Either remove caching or cache based on latest event (0d) @ilija-lazoroski
• Remove aws_instance_id from report generation (0d) - @shreyamalviya
• Refactor the "tunnel issue" report component in the UI (0.5d) - @shreyamalviya
  • Pull machines and node communications and determine if any tunneling was used
  • Display the "tunnel issues"
  • Remove "tunnel issue" generation from the backend
• Refactor the UI to use the logic from Remove /api/exploitations/manual endpoint #2509 to get "manual monkeys" (0d) @ilija-lazoroski

[ilija-lazoroski]

Encryption/decryption of the events takes the longest when generating the reports. First thing that will upgrade the performance is to create an index when we get the events by type. That increases the performance by ~20%. Next thing is to fix encryption/decryption slowness which will be done in #2545

[ilija-lazoroski]

Test 1:

1. Removed encryption/decryption
2. Added index for event type field
3. No caching

Test 2:

1. Removed encryption/decryption
2. Added index for event type field
3. Caching
   First time generating the report:

Every other time:

It is safe to say that saving the report in the database and retrieving it if it is the latest saves more time then regenerating it again. It is good enough mechanism for now.