User Permissions

ER2 uses a form of Role-Based Access Control (RBAC) where a user has access to resources and privileges to perform specific tasks based on the roles and permissions granted to the user.

This article covers the following topics:

• Overview
• Global Permissions
• Resource Permissions
• Permissions Table
• Roles

Overview

A user is granted access to ER2 resources according to the roles and permissions that are explicitly assigned to the user. Permissions can be assigned via:

• Global Permissions: Determines the global settings and resources that a user can manage and access.
• Resource Permissions: Determines the resources that a user can access, and the actions that can be taken on those resources.
• Roles: Contain pre-set combinations of Global Permissions and Resource Permissions that determine the resources that a user can access, and the actions that can be taken on those resources.

Global Permissions

A Global Admin or Permissions Manager can manage the Global Permissions that are assigned to a user.

1. Expand the navigation menu, ENTERPRISE RECON .

2. Go to the USERS AND SECURITY > USER ACCOUNTS page.
3. Hover over a user, click Edit and navigate to the Roles and Permissions > Global Permissions tab.

   Setting	Description for <Setting> = On
   Global Admin	Superuser with global administrative rights to manage all resources. User can access and edit all pages on the ER2 Web Console. The following settings are automatically set to On for a Global Admin: System Manager Permissions Manager Data Type Author Allow API Access
   System Manager	User is granted administrative rights to manage the settings in the following Web Console pages: Data Type Profiles Network Configuration Users and Security User Accounts Add, edit or delete user accounts Security and Compliance Access Control List Monitoring and Alerts Remediation
   Permissions Manager	User can manage User Roles and also assign Target and Target Group permissions to user accounts. See Resource Permissions and Roles for more information.
   Data Type Author	User can create and share custom data types.
   Allow API Access	User is granted access to the Enterprise Recon 2.0 API. User is only able to access resources to which they have explicit permissions to.

See Permissions Table for a detailed list of components that are accessible for each Global Permissions setting.

Resource Permissions

A Global Admin or Permissions Manager can assign and manage the resources that a user has permissions to. Granular permissions can be assigned for Target Groups, Targets and credentials using the Resource Permissions Manager.

Target Groups and Targets

Target Groups are a means of managing Targets as a group, and for the purposes of permission setting, are treated like an individual Target. Targets must belong to one (and are allowed only one) Target Group.

Credentials

Credentials are credential sets saved by the user to access external resources such as Cloud-based Targets, Database Servers, and Remote Scan Targets. Credential sets are treated as independent objects from the Targets they are related to.

To manage the resources that a user has permissions to:

1. Expand the navigation menu, ENTERPRISE RECON .

2. Go to the USERS AND SECURITY > USER ACCOUNTS page.
3. Hover over a user, click Edit and navigate to the Roles and Permissions > Resource tab.
4. Click on + Add permissions to open the Resource Permissions Manager to add or remove permissions from the user.

Resource Permissions Manager

Target Group

Description

Set user permissions for all or specific Target Groups.

Add multiple Target Groups by pressing the Ctrl key and clicking the selected Target Groups.

Permission Details

1. Scan
   • User can schedule and manage scans for the selected Target Group.
2. Remediate
   1. Mark Location for Report
      • User can only perform remedial actions that mark locations for compliance reports (e.g. Confirmed, Remediated Manually, Test Data, False match, Remove Mark)
   2. Act Directly on Location
      • User can only perform remedial actions that act directly on selected locations (e.g. Mask all sensitive data, Quarantine, Delete Permanently, Encrypt file)
3. Report
   1. Summary
      • User can view or download only high-level summary information about a Target Group.
      • User can view the total and breakdown of matches by:
        • Match severity (e.g. prohibited data, match data, test data)
        • Data type (e.g. American Express, Australian Phone Number)
        • Target platform (e.g. Linux 2.6 64 bit, Windows 10 64bit)
        • Target type (e.g. MySQL, all local files)
        • File format (e.g. XML files, ZIP archives)
   2. Detailed
      • User can view or download detailed information about a Target Group.
      • Users can view:
        • The total and breakdown of matches by
          • Match severity (e.g. prohibited data, match data, test data)
          • Data type (e.g. American Express, Australian Phone Number)
          • Target platform (e.g. Linux 2.6 64 bit, Windows 10 64bit)
          • Target type (e.g. MySQL, all local files)
          • File format (e.g. XML files, ZIP archives)
        • Details on match locations
        • Match data samples and contextual information.

See Reports for more information.

Target

Description

Set user permissions for all or specific Targets.

Add multiple Target by pressing the Ctrl key and clicking the selected Targets.

Access to Targets can be limited to specific paths by defining a Path value. If no Accessible Path is specified, user will be allowed to access all resources on the Target.

See Restrict Accessible Path by Target for more information.

Permission Details

1. Scan
   • User can schedule and manage scans for the selected Target.
2. Remediate
   1. Mark Location for Report
      • User can only perform remedial actions that mark locations for compliance reports (e.g. Confirmed, Remediated Manually, Test Data, False match, Remove Mark)
   2. Act Directly on Location
      • User can only perform remedial actions that act directly on selected locations (e.g. Mask all sensitive data, Quarantine, Delete Permanently, Encrypt file)
3. Report
   1. Summary
      • User can view or download only high-level summary information about a Target.
      • User can view the total and breakdown of matches by:
        • Match severity (e.g. prohibited data, match data, test data)
        • Data type (e.g. American Express, Australian Phone Number)
        • Target platform (e.g. Linux 2.6 64 bit, Windows 10 64bit)
        • Target type (e.g. MySQL, all local files)
        • File format (e.g. XML files, ZIP archives)
   2. Detailed
      • User can view or download detailed information about a Target.
      • Users can view:
        • The total and breakdown of matches by
          • Match severity (e.g. prohibited data, match data, test data)
          • Data type (e.g. American Express, Australian Phone Number)
          • Target platform (e.g. Linux 2.6 64 bit, Windows 10 64bit)
          • Target type (e.g. MySQL, all local files)
          • File format (e.g. XML files, ZIP archives)
        • Details on match locations
        • Match data samples and contextual information.

See Reports for more information.

Credentials

Description

Select the credential sets that will be available to the user.

Permission Details

1. Use
   • User can use the selected credential set when scheduling scans.
2. Edit
   • User can modify the selected credential set.

Restrict Accessible Path by Target

Granular permissions can be assigned by defining specific paths that a user can access for a Target.

To restrict user access to a specific path on a Target:

1. Open the Resource Permission Manager > Choose Resource and select Targets.
2. Click on your selected Target to add it to the right panel.
3. Click on + Add path to restrict access to target to add a new path.
4. In the dropdown list, select the correct Target type.
5. Fill in the Accessible Path value to allow user access only to the specified path.
   
6. (Optional) Click on + Add line to add more accessible paths.
7. Click Add to save the changes.

Example

Target A is a MySQL database. Credential Set X contains the user name and password to access Target A.

User B is a System Manager who has the following resource permissions:

User B can scan Target A using Credential Set X. User B has the rights to edit Credential Set X when necessary.

If matches are found on Target A, User B can mark these locations for compliance reports but is not allowed to perform any remedial action that acts directly on these match locations.

Permissions Table

Resource permissions and Global Permissions that are assigned to a user grants access to specific components in ER2.

Note:

• ^[1] System Managers can edit Targets they have visibility to via Scan, Report or Remediation permissions.
• ^[2] System Managers can import or export Global Filters. System Managers can add Global Filters that apply to all Targets / Target Groups, or add Global Filters that apply only to Targets / Target Groups to which they have visibility to.
• ^[3] Notification and Alerts are only for Targets and events that the user has permissions to.
• ^[4] Activity Log only contains events that the user has visibility or permissions to.
• ^[5] User is able to use the API to access resources to which they have explicit permissions to.

Roles

A Global Admin or Permissions Manager can assign and manage roles that are associated with a user account.

1. Expand the navigation menu, ENTERPRISE RECON .

2. Go to the USERS AND SECURITY > USER ACCOUNTS page.
3. Hover over a user, click Edit and navigate to the Roles and Permissions tab to see the roles assigned to a user.
4. Click on + Add Roles or remove to add or delete roles assigned to the user.

See User Roles for more information.