Liongard Ideas Portal

Submit and upvote ideas to make Liongard better. You get 20 votes so vote wisely. 🙂

To learn more about our Ideas Portal, check out our FAQs.
To schedule a feedback session with a member of the Liongard Research Team, click here.

See what we've shipped by clicking here!

Security First an all Inspectors

Dear all,

I see a lot of features on Lingard but i miss some security design features which nowadays should be the priority:

In general:

  • Log of every movement inside the app. Specially from liongard staff while giving support like ITGlue

  • Ability to disable access from liongard staff like in Auvik

  • Every new inspector should be designed with least privileged permissions and a guide how to do it. (Like the azure Inspector which is perfect)

Well done:

  • Azure: read only guide, very well done.

  • Sophos XG: API access IP limited and read only (Great!)

More specific:

  • VMware is great but i have to use a root password! SSH is supposed to be disabled always. Other solutions like auvik uses PowerCLI scripts to get the info.

  • Shouldn´t have to be Doman Admin for installing the service... Should never install anything on a DC. I understand Liognard starff went around all this before, but other solutions are trying to avoid using doman admins.

  • Synology: Again the same... using an Admin account. What about SNMPv3?

  • Veeam Availability Console: Using admin password again. A guide for the least priviledge would be appreciated. Usually the user is also admin of the computer.

  • Cisco: Again, no guide for doing a non root user. Perhaps its not possible to do, but i think this could be enforced.

I know it would overcomplicate the solution but a "enforced security deployment" would be great. Even with less capabilities, but i cant use the solution "as is" for some customers that are super concerned about security.

Hope this helps


  • Luis Morcillo
  • Dec 31 2020
  • Reviewed - Under Consideration
Last Reviewed Date 2021-03-19
  • Attach files