Enabling and Disabling Fingerprinting During Scans
Why disable fingerprinting?
Fingerprinting can be enabled or disabled under the Scan Template Configuration Menu. Disabling Fingerprinting allows users to run policy scans without dedicating resources to Fingerprinting, which improves scan times. If Fingerprinting is disabled, the console will not integrate Fingerprint related data. For assets where previous scans did collect Fingerprint data, the console will retain that data.
Fingerprinting Operating Systems
Operating Systems will still be fingerprinted as this is required for correct Policy functionality.
Disable Fingerprinting in Scans
Fingerprinting will be enabled by default. Custom scan templates will have to be created in order to disable Fingerprinting.
In the Scan Template Configuration Menu in the console, click on the General tab.
In order to disable Fingerprinting you must first disable Vulnerabilities. Uncheck the Vulnerabilities Box. If you enable Vulnerabilities, Fingerprinting will automatically be enabled.
Uncheck the Enable Fingerprinting Box. A pop up will appear. Select Yes to confirm your intention to uncheck the box and disable Fingerprinting.
Enable Fingerprinting in Scans
Fingerprinting is enabled by default. If you previously disabled Fingerprinting and wish to reactive it, Fingerprinting### can be enabled using two methods.
- Check the Enable Fingerprinting Box. There is no confirmation when enabling the Fingerprinting Box as there is less potential impact when reactivating Fingerprinting then when deactivating it.
- Check the Vulnerabilities Box which will automatically enable fingerprinting.
Impact of Disabling Fingerprinting
Disabling Jess Modules
When fingerprinting is disabled the following Jess Modules will be deactivated:
Disabling fingerprinting in the console will also disable integrations for certain types of data to prevent loss of already collected data.
The following data types will not be integrated if fingerprinting is disabled: