Skip to main content


Sometimes, a situation may arise in a group that prevents our analysts from pentesting part of the scope or maybe all of it. Your team needs to keep track of these situations and solve them, so we can resume our assessments. The place on the ARM where you can see a cumulative record of solved and unsolved events in your group is the Events section.

Event Tab View

Events Table

This section shows a table providing the following information:

  • ID: The event’s unique identifier
  • Root: Refers to the nickname of the root.
  • Date reported: When the event was reported
  • Description: The problem that, according to the hacker, impeded, or still impedes, their security assessments
  • Type: The category in which the problem falls, which can be Authorization for special attack, Incorrect or missing supplies, ToE different from what was agreed upon or Other
  • Status: The condition of the event, which can be Solved, Pending, or Unsolved.
  • Date closed: When the event was solved, if it was; otherwise, only a hyphen is shown

Status in the event

The statuses help us to have more clarity about the status of our events. We handle three types: Unsolved, Pending, and Solved. Here we will explain the flow of these.

First, when an event is opened, it will have the status Unsolved.

Unsolved Status

Here you have to give the solution to this created event. When you have it, go to the checkbox on the left and click on it. When you do this, the Request Verification option will be activated immediately.

Request Verification Option

When you click on it, you will get a pop-up window where you will have to explain the justification of how you solved this event; remember to enter at least ten characters, followed by clicking on the Confirm button.

Confirm Button

At this moment, our event will enter the Pending state, where we will be waiting for the verification that the supplied solution is effective.

Pending State

When validated and the solution successful, it will move to our third Solved state.

If this solution does not work, the event will be set to Unsolved status, and you will receive a notification where you will see a comment from the analyst. These comments will be sent to you as a notification, but you can also see them in the Comments tab.


Export events

You can download the event table to a CSV (comma-separated values) file by clicking on the Export button.

Columns filter

You can show or hide columns in the table by clicking on the Columns button and toggling the on/off button in front of each column name.

Columns Filter


By clicking the Filters button, you can access several filter options corresponding to the variables that give columns their names.


The search bar filters the information contained in the columns of the table.

Event details

When you select an event, you access a new section with its details. In the header, you find the type of event, its ID, the date it was reported and its current status.

Event Details Header

You can see three tabs under the header: Description, Evidence and Comments. In Description, you find why the event was reported by one of our hackers along with their email, the site where it is present and the number of components affected.

Event Details Description

In Evidence, you find images, videos or GIFs justifying the reported event.

Event Details Evidence

In Comments, you find the discussion established between your company's staff and Fluid Attacks' hackers or project managers about the event. You can leave your comments there.

Event Details Comments

Types of events

Network access issues

The network port no longer has internet access.

VPN issues

Fails on the VPN connection.

Remote access issues

Problems with connection methods. For example, when access to environmental is not possible.

Authorization special attack

A specific test needs to be performed, which may affect availability or integrity and requires permission by the customer to carry out a specific test.

Client cancels project milestone

Customer cancels projects.

Client explicitly suspends project

The client suspends the project for a specified time or excludes a particular part of the ToE.

Cloning issues

Some repository does not clone.

Credential issues

No credentials exist, or those that do exist are not valid.

Data update required

Reset user credentials or data changes to consume a service.

Environment issues

Problems in the environment, either because it does not open or because some flow inside it has functional problems.

Installer issues

Unable to install or error when installed on mobile or desktop application.

Missing supplies

Lack of supplies other than credentials.

TOE differs approved

In One-Shot or continuous service there are services different from those agreed upon or non-existent functionalities.


Any other problems that do not fall into the above categories.