I've been reading through everything but cant put a finger on it. Is it possible to create a dynamic tag to identify laptops based on device model or something else? Example: Latitude or e5450
Thanks for this info grant, we ended up reporting on software as well, which is our hdrive encryption software, every laptop in the environment has this software so it has worked well.
Jason, do you guys use a certain dns naming convention for laptops in your network? You could tag by dns name contains?
That might work. Thanks
What type of scan are you doing? Authenticated or non authenticated; or Cloud Agent.
If I know that I can give you more accurate information. But if you look at the informational items you get back from a scan like QID 82044 for NetBios Name you could create an Asset Search Tag.
Let me know what type of scan your doing and I can probably provide you a more detailed explanation
We will be using cloud agent on laptops, my asset view dashboard shows manufacture and model, was hoping to be able to tag the model part without having to rely on netbios name@
ok I have reporting issues with the cloud Agent; separate tickets have been sent to Qualys on this.
Well not as easy as I thought.
So the Cloud Agent does give you the Registry and you can access it sorta from the Cloud Agent module. I have asked for more access to this maybe as a QID for information.
If you look in a windows system in the registry you would have something like HKLM/HARDWARE/DESCRIPTION/System/BIOS/SystemProductName and then the DATA Value which for mine is Precision M4700
So if they where to add this as a QID then you could do an asset search for that QID with the results data contains a string then make a tag out of that.
I would probably see if your TAM knows where they are on the new searching mechanisms; that may in fact solve the issue. I know the data is in Qualys just your ability to access the information.
I can think of other ways to do it but they would not be "well supported"
I would suggest you file a case with Qualys seems like something most of people would want is to have a TAG Structure just setup by Model, vendor, etc..
We created a OVAL check that looked for "battery management type software". We made the sweeping assumption that a windows device with battery management in use, would be a laptop and not a PC or a server . It worked pretty well. Regrettably, I dont have the OVAL code anymore but I did not get the impression it was tough to write. Hope this helps.
would you be able to provide the code or regex you used?
Eddy , For tagging via software it real easy. For Rule Engine choose "Software Installed" then for REG Ex, we just simply entered the name of the software, as Qualys see it. So for us we use Symantec PGP, so we just put pgp there and it identified all our devices running this software and tagged it as laptop. Not sure if it suppose to be this easy but it sure was for us.
Careful with this assumption. I have seen a number of platforms (Such as ATM's) with battery/power management ACPI support in the BIOS. This of course ended up with the OS enumerating a battery, etc. I was bitten by this once deploying power policies.
Retrieving data ...