Feature Requests

Need a way to audit what the employees are doing, when they view a client, export data, create a metric, etc. Having the ability that allows Admins the ability to audit what actions a user made the week before they were fired for example is critical to knowing what risks may be open.Make an audit log report available for administrator actions (environment additions/deletions, etc).

It would be good if we could select every inspector on the inspector page (Example: We have 230 MS365 inspectors) rather than having to select each page (100) at a time.This would make scheduling easier, as we could select all > schedule for 12pm and space out of X amount of minutes, rather than having to do each page at a time.Would also make it easier to add to the schedule in the future, rather than having to fit it into the schedule

I would like to see a search function in Liongard available. Where you can search all over Liongard, through all the options under the admin menu. Or, for example, just like with IT-Glue: https://support.itglue.com/hc/en-us/articles/360004936277-Search

Cloud inspectors run a minimum of every 8 hours but..Being able to detect changes to global admins, new external forwarding rules, change of mx records are all vital to detect changes early to minimise damages caused.Being able to react quickly to security issues is vital.Running inspectors every 8 hours is not good enough. It's not enough to get an alert after the damage is been done.Please allow running of cloud inspectors, especially the Microsoft 365 and domain inspectors down to the hour.THanks.

In the user identity discovery area, I noticed that for users identified in both Active Directory (AD) and Microsoft 365 (M365), we lose visibility into local AD memberships. It would be beneficial to display local AD and M365 group memberships separately and enumerate user roles. This enhancement would greatly aid in conducting privileged access reviews.

The way inspectors are named is problematic in several ways, but one is that they have to be unique globally across all environments. Removing this requirement would let us name Windows Workstations using only their hostname or FQDN. I have to assume that every inspector already has some GUID, and the other associated data tells us things like the inspector type and the environment in which it exists. I don't see the benefit of hard-coding those bits of data into a text name field. I'm sure this change isn't simple on the back end, but it's still worth bringing up.

Auto-fill inspector names according to a default standard. Allow the user to override and name them whatever they want, but don't require them to enter a name at all.

This way you can update multiple inspector's names etc.

When setting up discovered inspectors often we edit an inspector before activating it. It would be nice to have a Save, Save and Activate, or Cancel buttons within the discovered inspector settings.

At the Environment level, allow for the ability to pause all related inspections. The user should also be able to re-enable an Environment and respective Inspectors. When an Environment is disabled, there should be option to hide it from the active list. Agents will remain active regardless of state.