Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requesting ability to capture all resources, even those which aren't fully understood by AzureHound #41

Open
rsheasby opened this issue May 19, 2023 · 1 comment

Comments

@rsheasby
Copy link

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.

@timkatsapas
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants