Section 12 Security Management

Section 12 Security Management

Security Management

Security Management allows Administrators to set up users or groups, and policies and scopes, which, combined, become a Security Policy Definition (SPD). Policies are vital for keeping proper access rights to your most sensitive data. The ability to group users into sets to assign permission levels (a Policy) is incredibly useful for maintaining a least-privilege policy. Policies are complex and are applied to enable users to access and change data.

A group is a collection of users with a given set of permissions assigned to the group (and transitively, to the users). 

A password policy is a set of rules designed to enhance computer security by encouraging users to employ strong passwords and use them properly. The computer system will force users to follow the password policy. WIB™ Review has a strict password policy that is NIST compliant. For more information regarding the Password Policy please contact support@radixdata.com.

Section 12.2   Organizational Chart of Users, Groups and Roles


Section 12.2.1    Security Quick Start Reference

1       Create a Policy

2       Create a Scope

3       Add a Policy to a Group and assign the scope

4       Add Users to a Group
 

Section 12.3   Groups

A group of users is given access to work areas (scope of projects/collections) that all need access to the same resources. Groups can be created based on individual users who all need access to certain resources or based on global groups (such as departments: accounting, business function (accounts payable or accounts receivable), or workflow process function (invoice approval).

Section 12.3.1                  Create a New Group

Using the Navigation Tree, select Users>Groups>Policies>Scopes. Each section contains tables showing information for each security level. Select the Groups tab to view a list of users and Policies assigned to the Group. Select Add New to create a New Group. You can edit, delete, or view the group settings by highlighting the group and selecting edit, delete, or details, respectively.

Section 12.3.2                 Group Properties

Section 12.3.2.1           Group Name

Give the Group a descriptive name. Some examples of good group names are A department (Operations), a business function (Accounts Payable), or a processing function (Reviewers).

Section 12.3.2.2           Group User(s)

Users can be assigned directly to a group. The user will keep the permissions granted to the user. The user will then be granted access to work areas under the group scope. Users can belong to multiple groups. 

Section 12.3.2.3           Group Security Policy

A group-level security policy defines which portal areas (Policy) and project or collections (Scopes) the users assigned to the group have access to. 

Section 12.3.2.5.1                Data Policy

A Group Data Policy grants access to work areas in the workspace. Roles can be inherited in the group policy, or can be defined separately. If a Role has a data policy defined, the Role Data Policy overrides the Group Data Policy.

Section 12.4   Users

A user is associated with an access license (UAL). They are not shared by Users; each User must have their own UAL. Once a User has their own UAL, it does not matter how many machines they log in from. Users are assigned a Role and are part of a Group. Users can have a separate Security Policy that limits or grants added privileges beyond their defined Role or Group.

Section 12.5  Creating a Security Policy

Administrators can create a security policy for a user or a role. Components of a Policy include the level (user/role), accessibility settings (group/user/role), and action settings. Each Security Policy must address all areas of WIB Review: who can access each area, what actions are allowed and to whom or which role/user the policy applies.

Section 12.5.1                  Policy Name

Name the policy in such a way that it describes either the role or an individual user’s job function. It is suggested that the Policy Name be different from the Group or Username, as staff and responsibilities change over time, and you want the Policy to reflect the functionality that persists. You can change the name of the policy.

Section 12.5.2         Security Policy Definition (SPD)

A Security Policy definition is comprised of Policies and Scopes, which are applied to a User or a Group of Users. Go to Policies\Overview and select New. You will be prompted to select either Wizard or Design View to create the new policy.

Section 12.5.2.1           Security Policy Wizard

The Wizard walks you through each page of the portal and guides you through the sections and actions available to users. Take into consideration the job functions of the group or user you are creating a policy for, and assign which areas of the portal they should have access to and what actions they are permitted to take.

Section 12.5.2.2            Security Policy Design View

You are not required to use the Wizard; you can also create a Policy in Design view. You can toggle from the Wizard to Design view using the button in the right corner of the Wizard stepper.

Section 1.1.1  

Section 12.6      Create a Scope

Go to Scopes and select New. Select the Projects and Collections you want a User or a Group of Users to have access to.

 1.1.2 

Section 12.7      Assign the Policy and Scope

You must assign the Policy and Scope to a specific user or group. If you access the Policy from a Group or User, the Policy Summary will populate with the User or Group the Policy is assigned to.


    • Related Articles

    • Section 10.2 Automation

      Section 10.2 Automation Automation describes a wide range of technologies that reduce human intervention in processes. Human intervention is reduced by predetermining decision criteria, sub-process relationships, and related actions — and embodying ...
    • Section 3 Site Navigation

      Site Navigation The user can expand the Navigation Drawer by selecting the hamburger menu so that each icon label is visible. Icon Page Description Home Page Quick access to most frequented areas. Projects and associated stats are displayed for the ...
    • Section 11 Data Management

      Data Management Data Management allows administrators to watch sessions and keep data synchronized with changes to the configuration by rebuilding data at various levels. Section 11.2 Data Management Monitoring Levels Data Management is organized by ...
    • Section 9 Project Management

      Project Management A Project holds the overall design of the system. This area allows the Workspace Administrator to manage Projects and their parts (entities). A Project has the following entities: collections, attributes, automation, and workflow. ...
    • Section 12.5 Security Policy

      Section 12.5 Creating a Security Policy Administrators can create a security policy for a user or a role. Components of a Policy include the level (user/role), accessibility settings (group/user/role), and action settings. Each Security Policy must ...