New article
Recently updated
Understanding security
Who is this article for?
Ideagen EHSQ Enterprise or Decani administrators or module developers managing security settings
Appropriate administrative permissions required.
Overview
Application security within the platform is handled with a combination of system and user settings. Administrators play a vital role in ensuring a subscriber's information is secure and that the data meets subscriber requirements.
Security Best-Practices
The following items should be reviewed and approved by the subscriber’s security department.
- Consider and monitor Ideagen recommended hardware and browser configuration guidelines and Login Options
- Single Sign On (SSO)
- IP Restrictions
- Mobile Behavior
- Set a period of inactivity to determine when a user’s session should be terminated. The default is two hours. User accounts can also be automatically disabled after a defined period. This is not a default setting.
- Limit the number of admins with the User Access Control Administrator role. This is the only role that can grant other administrative roles to users. If there is only one person with this role, they know that others will not be granting themselves administrative roles and rights.
- Do not allow or encourage shared or generic accounts.
- Educate users about what type of information should and should not be entered or uploaded into the system. For example, classified or controlled information, PII (personally identifiable information), financial information, etc.
- Encourage users to use the "Forgot Password" option if they are not using SSO.
- Use Roles to manage oversight of user permissions across the various applications.
- Use Reporting Authorities to segment data.
- Use Record Access Control to control access at the objects level.
- Limit the number of users with the Module Developer role. This role can permanently change application fields, behaviors, and rules.