Best Practices for Access Permissions

This section describes the best practices that ScienceLogic recommends you follow when creating Access Keys. Although you can completely customize your own Access Keys, the recommendations provided in this section will make managing Access Keys easier.

Use the following menu options to navigate the SL1 user interface:

• To view a pop-out list of menu options, click the menu icon ().
• To view a page containing all of the menu options, click the Advanced menu icon ().

Best Practices

ScienceLogic recommends you follow these best practices when creating Access Keys:

• In general, Access Keys should include Access Hooks for one area of the product. It is a good idea to select a category for an Access Key and then include only Access Hooks from the same category. If you want to easily grant a user Access Hooks that cover different sections of the product, we recommend you create an Access Key for each section and then align them with a User Policy.
• If you are creating an Access Key that includes Access Hooks with dependencies, you should also align the Access Hooks they depend on with the Access Key, even if they are in a different category.
• To avoid confusion, you shouldn't create too many similar Access Keys. If there is a large overlap between Access Keys, consider creating an Access Key that only includes the overlapping Access Hooks, then create additional Access Keys for users that must be granted the non-overlapping Access Hooks.
• If you are using Access Keys to control access to user generated content, consider creating Access Keys without aligned Access Hooks solely for that purpose. If you do this, it is easier to grant and remove access to dashboards, knowledge base articles, and device groups without affecting a user's granted Access Hooks.

Due to security vulnerabilities, ScienceLogic recommends that customers who installed SL1 prior to 8.9.2 disable the Knowledge Base. For details, see the release notes for version 8.9.2 of SL1.