I have a customer that would really like to be able to apply a tag based on the content of a specific registry key. Is there anything on the road map ? Large Cloud Agent user.

During build the responsible dept name is added as a reg key and the equipment goes far and wide after that. IP / Hostnames / NetBIOS names / SSL certs - none give consistent answers. Only the reg key would work for this one. Any thoughts ?

Have either of you documented a clear use case and reviewed it with your TAM for a potential feature request?

Community posts don't drive the feature development process, interaction between the customer and TAM does. However, a post on the community can be leveraged in a feature request to demonstrate interest. Interest drives change.

There is no way for a tag to check a registry entry. Tagging happens during post-scan processing.

However, I'm thinking, I don't know, maybe, a PC UDC to check if the registry entry and if matched, an alert of some kind, maybe email, could notify a subscriber to create the tag manually?

Perhaps one day, in the future, the PC UDC detection could maybe create tag as a sub-process of the finding (automagically) .

Further, there might be a way today, an opportunity to script a process using PC and Tag APIs to work together to create a tag and get'er done that way.

Dream Big. Think Outside the Box. I'm sure you two very brilliant guys could come with a great suggestion/recommendations AND a valid business use case to get things rolling.