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
AzureHound doesn't support every sort of resource that can exist on Azure, obviously this is a necessary compromise due to the sheer number of resource types. However, even for those resources which don't have explicit support, it would be great if they could still be captured by AzureHound and stored as nodes, so they can be used as targets.
For example, if I have an Azure Database which is considered a high value target, there is no way to evaluate its security using AzureHound, as it does not yet support Azure Databases. If there were an option to capture it as an "unknown" resource, it could still at least be set as a target, and I can see who can get ownership of it.
The text was updated successfully, but these errors were encountered:
To add on, with the same token - Azure Storage Accounts also cant seem to be enumerated yet. It would be great even to do very basic IAM permission checking, or at the very least to show the object listed so you know what resources exist.
AzureHound doesn't support every sort of resource that can exist on Azure, obviously this is a necessary compromise due to the sheer number of resource types. However, even for those resources which don't have explicit support, it would be great if they could still be captured by AzureHound and stored as nodes, so they can be used as targets.
For example, if I have an Azure Database which is considered a high value target, there is no way to evaluate its security using AzureHound, as it does not yet support Azure Databases. If there were an option to capture it as an "unknown" resource, it could still at least be set as a target, and I can see who can get ownership of it.
The text was updated successfully, but these errors were encountered: