Ideally, the output of a report is designed to go to a specific kind of audience (usually the asset owner)....... Ideally (which is most cases).
An Asset group has a defined Asset ownership to a team in your organization, who can then commence remediation of their assets. If we allow sorting by tags (remember tags are hierarchical too and this will loop the reporting data if there are child tags to parent tags), then it may cover assets not owned by a team, and will make no sense for the target audience as not everyone is responsible for every asset. We however, provide ticketing on a tag based target.
If you want to benefit from a feature like "Group by tag" in reporting, then you may create the template to "sort by Host", but when you consume/execute the template, set the targets to Tags. Problems solved.
Let me know if you like this idea.
djprakash - The use of dynamic asset tagging is preferred in our organization, and we have worked very hard on creating an appropriate hierarchy under the guidance of our TAM. We use asset groups for scanning and tags for reporting. The tags are tailored to our report recipients. We should have the option to sort by asset tag, just as those who use sort by asset group.
The Qualys reporting tool is lacking in so many ways, and I can often get around the issue by using CSV and macros to modify the data, but Qualys should be providing the basics so that manual work required is less.
I'll try the "sort by host" with Tags, but I am fairly certain the results are not what I'm looking for as I have tried every combination I can.
Retrieving data ...