It would be extremely helpful to have a community group for the product. I have mentioned this to our account manager. We have community support with several other products, and it allows us to learn best practices or examples from other organizations using the same product. Additionally, while most of the documentation around the product is quite good, it would be beneficial to have examples of possible scenarios, such as creating an integration with a ticketing system. Providing real-world examples of how to construct a ticket format for Jira, Azure DevOps, or ServiceNow with specific examples would help us understand how it might work in our environment. Part of the reasons we selected Vulcan was to bring data sources and duplicate the information; however, we've had issues where it doesn't do that. For example, if there is a vulnerability, if it finds that in three different locations on the same device, it doesn't duplicate them effectively and increases the account instead of consolidating it into a single vulnerability that has three different actions. So it skews the counts that we have when we're looking at the volume of vulnerabilities. It misrepresents the number of assets that are affected. For example, if we've got a vulnerability that affects assets, and if one of the assets has three different folders where that vulnerability or the piece of software is, the solution counts that as three different assets. It gets confusing. It's telling us we have more assets than we actually have. When we raise a vulnerability campaign that gets created into an Azure DevOps ticket, one of our requirements is to allow updates to flow back into Vulcan to help us understand the status of a campaign. That is a piece of information that is currently missing, and we've requested this capability pretty much from day one. Right now, it means when we're working through those vulnerabilities with our infrastructure team (who are responsible for fixing them), we're revisiting the same vulnerabilities to find out what's going on with that vulnerability. We don't see any information about that campaign since what we actually wanted as part of the solution is the ability for them to send that and document the updates in DevOps tickets and for that information to flow back into Vulcan so that we can see that information, and we don't have to kind of visibility.
