You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been tinkering with axonshell and axonius as a way to sort of... not do the coding and correlation through our own internal tools. The data you collect has been quite helpful!
With that said: Do you have any plans to expand the scope of assets that you expose through the API/CLI? I could be missing something, but as far as I can tell, it appears that I can query for Device and User assets, but, for example, I cannot query for Groups, Roles, Accounts, Permissions, Containers, Object Storage, or other Assets enumerated in the GUI.
Totally get that the work behind exposing even one of these types would be significant, more just curious if this is on the roadmap, and if so, if there's any rough ETA, e.g. "Exposing XYZ Assets via the CLI/API is in development, can't commit to any dates, but maybe on the order of months to a year"
Thanks!
The text was updated successfully, but these errors were encountered:
Hi all!
I've been tinkering with axonshell and axonius as a way to sort of... not do the coding and correlation through our own internal tools. The data you collect has been quite helpful!
With that said: Do you have any plans to expand the scope of assets that you expose through the API/CLI? I could be missing something, but as far as I can tell, it appears that I can query for Device and User assets, but, for example, I cannot query for Groups, Roles, Accounts, Permissions, Containers, Object Storage, or other Assets enumerated in the GUI.
Totally get that the work behind exposing even one of these types would be significant, more just curious if this is on the roadmap, and if so, if there's any rough ETA, e.g. "Exposing XYZ Assets via the CLI/API is in development, can't commit to any dates, but maybe on the order of months to a year"
Thanks!
The text was updated successfully, but these errors were encountered: