Resolve events

Last updated: Oct 26, 2026

---

During a security assessment, some situations can stop the Fluid Attacks tool or analysts. Then they cannot test the scope of the group, or a part of it.

These situations are events. Your team must solve them, so that the assessment can continue effectively.

The Events section of each group shows a cumulative record of the solved and unsolved events of that group.

When you have events to solve, a red banner tells you in the Groups section. The banner stays for only a short time. It shows the number of affected groups, the number of unsolved events, and the days since Fluid Attacks reported the oldest event.

Move the pointer over the banner to see the names of the affected groups.

When you go to a group, a red dot on the Events tab shows that the group has one or more unsolved events. You must examine these events immediately. Click the tab to go to the Events section.

Know your events table

The table in the Events section gives full information about each event.

These are short descriptions of the information in the table:

• ID: A unique identifier for the event
• Type: The category of the problem (read the descriptions of event types below)
• Date reported: The date when Fluid Attacks reported the event
• Description: A detailed explanation of the problem that prevents the security assessment
• Status: The current state of the event, which can be "Solved," "Pending," or "Unsolved" (read the event status categories below)
• Date closed: The date and time when the event was solved (if applicable)
• Repository: The nickname of the affected repository

Types of events

Fluid Attacks sorts events into these categories:

• Authorization for a special attack: Some tests can have an effect on availability or integrity. For these tests, Fluid Attacks must get the explicit approval of the customer.

  If an unforeseen situation affects the performance or execution of the running application during security testing, Fluid Attacks shall immediately notify you via the corresponding Engagement Manager to inform you of the details about the issue and actions performed.

• Cloning issues: There are problems with the clone process of the repository

• Credentials issues: Missing or incorrect credentials prevent the access to the assets to test

• Data update required: User credentials or data must be reset or updated to use a service

• Environment issues: There are problems with the testing environment, such as unavailability or functional problems

• Installer issues: There are problems when you install or run the application on mobile or desktop

• Missing supplies: Necessary resources other than credentials are missing.

  This condition frequently occurs when a group has no repositories in scope, or when the clone process failed for all registered repositories. Thus, the group has no security testing.

  In that situation, Fluid Attacks automatically opens a missing supplies event with the message "No repositories in scope. No security testing is being performed, but costs may apply."

  This event links to a virtual repository with the name general. This repository is only for the event, and the platform does not count it as an active repository.

  When you add a repository to the group and the clone process is successful, the platform closes the event automatically.

  Fluid Attacks checks daily (Monday through Friday) whether each group has at least one repository with a successful clone. Groups without any such repository receive this event automatically; groups that subsequently register one have it closed automatically.

• Network access issues: The network port does not have internet connectivity

• Other: The problem is not in the predefined categories

• Remote access issues: Problems with connection methods prevent the access to the environment

• Request user modification/workflow update: Changes to test users (for example, a role change or unblock) or to workflow conditions are necessary to continue the tests

• The client cancels a project milestone: The client cancels a predefined phase or deliverable of the project

• The client explicitly suspends the project: The client temporarily suspends the project or excludes specific parts of the target of evaluation (ToE).

• ToE different than agreed upon: The client gives a ToE that the plan does not include

• VPN issues: The VPN connection fails

Event status

In the Events section of the platform, the Status column shows the state of each event.

An event has these statuses, in this sequence:

1. Unsolved: The initial state when Fluid Attacks reports the event. Your action is necessary.
2. Pending: After you solve the event and request a verification, the event awaits verification by Fluid Attacks.
3. Solved: The problem is solved and verified.

View event details

Click the ID of an event in the table to see detailed information and a comment space. If your group has an Advanced plan subscription, you can post comments in this space, and the Fluid Attacks team can see them and reply. If not, it is a read-only section.

Description

The Description section of an event shows this information:

• Description: What the problem is (or was)
• Solving reason: Why the problem is solved (if applicable)
• Repo (nickname): The nickname of the affected repository
• Reattacks on hold: The number of reattacks that the event prevents
• Date closed: The date when Fluid Attacks verified that the problem is solved (if applicable)

Evidence

The Evidence section of the event shows screenshots or videos as proof of the problem that prevents the tests. Click an item of evidence to make it larger and to see the download option. If there is more than one item, click Download File to download them in a ZIP folder.

Comments

The Comments section of the event is a forum-like space where your team and Fluid Attacks discuss the event. For instructions on how to use this section, read "Post comments".

Request a verification that the event is solved

When you solve the reported problem, you can request that the Fluid Attacks team make sure that the event is solved. Then, the tests can continue. To do this, do these steps:

1. Go to the Events section of the group.

2. Select the checkbox next to the event you solved.

   

3. Click Request verification.

4. In the pop-up window, write a description of your solution (10 or more characters).

   

5. Click Confirm.

The event status then changes to Pending while Fluid Attacks verifies that your solution is effective.

If Fluid Attacks finds that your solution does not solve the problem, you get a notification. The result is also in a comment in the Comments section. Do the verification process again until the event is solved.

Filter the events table

Click the filter button () to see the options to filter the events table. The available options are Date reported, Type, Status, and Date closed.

Show or hide columns of the events table

Click Columns to open a pop-up window. There, you can reorder, show, or hide columns in the table. Click Reset to default to show all the columns.

Export the events table

You can download the content of the table in the Events section as a CSV (comma-separated values) file. Click Export.

Search the events table

Type in the search box to show only the rows of the table that match your search.