Keeping your account secure and data protected is a growing concern in today’s era. For a good experience with HackerRank, we recommend you to follow some of the best practice guidelines to keep your account secure and ensure that no data is lost.
Why is this important:
Security compliance is of utmost importance across all organisations and failure to do the same might lead to significant amount of business risk. Here are some of the key reasons why maintaining compliance with IT regulations is important for organisations.
- Enhancing Security
- Reducing Data Loss
- Building Trust among all stakeholders
Keeping in line with the security compliance measures of companies, HackerRank have come up with a number of best practice measures which can help you enhance the security of your HackerRank for Work account.
Create a strong password for your account
We recommend to use a strong password for your new HackerRank account. Some key points to remember while setting up your account password:
- Use a combination of alphanumeric characters in your password
- Ensure to maintain a minimum of 8 characters while setting your password
- Use at least one uppercase letter, one lowercase letter and one digit in your password
Keep your account credentials private
It is always a good practice to keep account login credentials confidential. Sharing user account credential with fellow team members might raise question in data security.
Keeping this in mind, HackerRank has introduced a new feature that allows you to have only one active session at a time. We have started to roll out this feature to customers and will soon make it live to your organisation. You can request this feature for your account at email@example.com if you you need it on priority.
If you attempt to login to your HackerRank for Work account while the same account is already active from another device or browser, you will see the below blocking error.
Click Continue to logout from other active sessions and proceed further.
Note:This is a mandatory authentication check that the system performs and it cannot be turned off. Consider changing your account password if you see the message again and again.
Log out of your account once work is over
Another good practice to ensure data security is to close your session when work is over. After making any change always save your work and once your work is over, logout from your account. This reduces the chance of other entities(authorised or unauthorised) from accessing your system and also reduces the chance of losing important data.
Inactive Session Timeout
As an enterprise organisation that is particular about compliance and security, you might want to ensure the security of your data by implementing strict session inactivity timeout limit.
As a company admin, you can set a threshold, beyond which, if any session within your organisation is inactive, then the same will be automatically logged out. Follow the below steps to set session timeout in your HackerRank for Work account.
- Login to your HackerRank for Work account.
- Click Settings from the top right dropdown of your account.
- From the left hand panel of your Account Settings page, click on Compliance & Security option.
- Scroll down to the Timeout Inactive Session section.
- Tick the “Enable timeout for inactive sessions” checkbox and set the inactivity time limit of your organisation. Any session, that stays beyond this set threshold, will get automatically logged out of the network.
- You can set any time limit between 15 mins to 24 hours as the threshold for inactive session timeout.
Note: This setting is available to Company Admins only. And, if you do not wish to set any inactivity timeout limit for your organisation, then, any inactive session within your organisation will automatically get logged out after 24 hours.
- Users will get below message on their screen if they stay inactive beyond the threshold value set by the company admin.
- On clicking on the Login button, users will be redirected back to the Account login page. Please note that any unsaved progress in the previous session will be lost if the session goes inactive and the same user or other any other user logs in after that.
Note: While setting up the inactivity time limit ensure to maintain a balance between usability and security so that your team members can comfortably carry out their activities within the application, without their sessions frequently expiring. We recommend to set 30 mins as the threshold value.