Skip to main content

Roles

Users on the ARM have different roles with associated permissions relevant to work on the platform. Depending on your role, you are granted access to certain functions for your daily use of the ARM. You can see your role on the ARM in the drop-down menu that appears when you click the user icon on the upper-right part of your screen.

The following are the different roles that are available on the ARM, along with their descriptions.

User manager role

This is the role that gives the user the most privileges, this user can do everything that a client is allowed to do in the ARM. This role is made for the leaders of the product and, besides the basic privileges, it allows the user to generate reports, define important treatments like accepting vulnerabilities permanently, requesting Zero Risk treatments, adding and editing users for the group and more.

User role

This is the default user role, it is the one given to developers or the users in charge of solving the vulnerabilities. This user can check all the information about the vulnerabilities needed for solving them and also request reattacks when they deem them solved.

Vulnerability manager role

The role of vulnerability manager was designed for people with a position as technical leaders in their company. This role has access to the basic privileges on the ARM and is also enabled to generate reports; get notifications; define, change and approve treatments; request reattacks, and add tags. The vulnerability manager does not have permissions to manage roots nor add, edit or remove users.

Functions

  • Add roots: This function is for adding git roots to the scope of the group being managed.
  • Add tags: This is for adding tags to the group being managed which is useful for categorizing different groups in an organization.
  • Add users: This function is for adding user to a group and setting their privileges.
  • Approve treatments: This function is for when a treatment change is requested, as there is a need to validate and then accept or reject this request.
  • Change treatments: Each vulnerability can be given a specific treatment. This function gives the ability to request the change of this treatment.
  • Deactivate/Activate root: This function allows you to:
    1. Deactivate repositories for which you no longer want an assessment;
    2. Activate repositories you want to leave available to our analysts, and
    3. Move a root to another group, taking all the associated vulnerabilities with it.
  • Delete groups: With this function you are able to completely delete the group being managed.
  • Edit roots: This function allows you to change URLs of roots that do not have reported vulnerabilities and edit root branches.
  • Edit users: This option is for editing everything related to the users added to the group.
  • Exclusions: This feature allows you to choose files or folders in your repository that you do not want to include in the security assessments.
  • Generate a report: This feature allows you to generate and download a complete report with detailed information about the vulnerabilities of a specific group.
  • Receive notifications: This is the ability to receive notifications that the ARM can send related to your group.
  • Request reattacks: When a vulnerability is solved, there is the need to ask our hackers to verify that it was indeed solved. This function gives you the ability to make this kind of request.
  • View vulnerabilities: The ability to view all the information available about all the vulnerabilities that the project has.
  • ORG vulnerabilities download: Download your organization's vulnerabilities (including all vulnerability statuses) in a .CSV file. For more information, click here

Roles table

In the following table we specify what functions are enabled for each role.

UserVulnerability managerUser manager
Add rootsXX
Add tagsXXX
Add usersX
Approve treatmentsXX
Change treatmentsXXX
Deactivate/Activate rootX
Delete groupsX
Edit rootsXX
Edit usersX
ExclusionsX
Generate a reportXX
Group policiesX
Receive notificationsXXX
Request reattackXXX
View vulnerabilitiesXXX
ORG vulnerabilities downloadX

Internal roles

Fluid Attacks’ internal roles on the ARM.

Hacker

The hacker is a security analyst whose main objectives are identifying, exploiting and reporting vulnerabilities in organizations' systems.

Reattacker

The reattacker is in charge of verifying, through diverse techniques, the effectiveness of the solutions implemented by the organizations for vulnerability remediation.

Customer manager

The customer manager mainly provides support and streamlines processes of the organizations. For example, on the ARM, they can make changes in group information, request reattacks, generate reports and manage stakeholders, among many other things.

Resourcer

The resourcer helps keep updated the inputs provided by the organizations, such as environment credentials and mailmap authors, among others.

Reviewer

The reviewer is in charge of managing the vulnerabilities that are reported to the organizations. They evaluate drafts for approval or disapproval, request reattacks and verify and notify which vulnerabilities are zero risk.

Architect

The architect's main objective is to ensure the highest quality of ethical hacking and pentesting deliverables. Among their functions are deleting false positives or errors, including or deleting evidence, and providing help to the organizations over the support channels.

Admin

The admin is the one who has all the privileges on the ARM, except for the possibility to change treatments.

Internal roles table

In the following table, we specify what functions are enabled for each role:

HackerReattackerResourcerReviewerArchitectCustomer ManagerAdmin
Add draftsXXXX
Add eventsXXXXXX
Add rootsXX
Approve draftsXX
Change treatmentsXX
Confirm/Reject ZRXXX
Deactivate/Activate rootX
Delete groupsXX
Edit rootsXX
Generate a reportXXXX
Manage evidencesXXX
Request reattackXXXXXXX
Request ZRXX
Solve eventsXXXXXX
Verify reattackXXXX