While creating or managing identities, many IT administrators worry that assigning excessive permissions to users and groups could lead to grave consequences like insider attacks or data breaches. These security risks could be even more worrisome if there are no predefined permission sets for each role.
A simple remedy is to design standard templates with the required permissions, as well as group memberships for all roles, especially the privileged roles. You can use this template whenever you create or modify a user account.
When it comes to permissions and rights management, many IT admins face the dilemma of "How much is too much?" But this situation can't be ignored; incorrectly assigning permissions can lead to disastrous consequences if sensitive data ends up in the wrong hands.
To avoid this, follow this rule of thumb: assign minimal permissions, and remove additional privileges when they are no longer needed or after a specific period of time. To decide what the minimum permissions are and how long special permissions are required, consult the business process owners, or the HRs. Using a solution that helps you automatically assign permissions and revoke them after a specific period makes permissions management easier.
If your offboarding process is not rigidly enforced, ex-employees might retain access to user accounts and critical resources. Infrequent or irregular deprovisioning could lead to excessive stale accounts, which could prove detrimental to your organization's security.
Running automated deprovisioning schedules at frequent intervals keeps your AD environment devoid of stale accounts. You should also sync your AD with your HR software or database so that when a user account is deleted from either of these tools, it is also deleted from AD.
User inactivity can occur when an employee goes on extended leave, or an IT admin forgets to disable a former employee’s account. To streamline the onboarding process, some organizations create user accounts with the same passwords before employees join the organization. This can lead to inactive accounts that are easily misused by existing employees. It's essential to track user inactivity and disable the respective accounts to prevent insider attacks; user accounts should either be disabled, or stripped of unnecessary privileges to prevent misuse.
Overloading an IT admin with IAM tasks can place an excessive amount of security responsibilty on one person. This can lead to errors due to fatigue, like typos, and might result in modifications to the wrong accounts, misallocation of permissions, and more.
A best practice is to delegate IAM tasks to different IT technicians for different departments. Even better is monitoring an IT technician's everyday activities and rectifying inappropriate ones.
Create custom templates to create or modify users.
Auto-fill attributes with the help of conditions.
Proactively define duplication.
Set or modify NTFS permissions granularly.
View existing and modified permissions for a specific folder.
Define tasks that are to be performed during cleanup.
Automatically pick up users to be deleted through reports or a CSV file.
Set the time interval and frequency for the automation.
Generate a list of users who have not logged on for a specified period.
Take remedial action.
Delegate specific OUs to a particular technician.
Assign templates to be used to perform a delegated task.
© 2019 Zoho Corporation Pvt. Ltd. All rights reserved.