Can a discovery schedule in ServiceNow be updated to disable credential‑less discovery?

Pranita Bahugun
Giga Guru

36m ago

Hi everyone,

I would like to know if it’s possible to update a discovery schedule in ServiceNow so that credential‑less discovery is disabled. Currently, credential‑less discovery runs as part of our scheduled scans, but we want to restrict or turn it off for certain schedules without impacting other discovery activities.

Could someone clarify whether this can be configured directly within the discovery schedule, or if it requires additional setup such as behavior rules. If we need to configure Discovery Behavior then how that can be configured?

Any guidance on the recommended approach would be very helpful.

 

Thankyou,

Pranita Bahuguni

Labels:
0 Helpfuls
  • 44 Views
1 REPLY 1

vaishali231
Kilo Sage

12m ago

Hey @Pranita Bahugun 

Yes, this can be controlled, but it is normally handled through Discovery Behavior rather than directly disabling it only from the Discovery Schedule form.

In ServiceNow Discovery, credential-less discovery can run as part of the normal discovery process when no valid credentials are found or when probes/patterns allow credential-less identification. If you want to restrict this only for certain schedules, the recommended approach is to create or modify a Discovery Behavior and associate it with the required Discovery Schedule.

Steps:

  1. Navigate to Discovery > Discovery Definition > Behaviors.
  2. Create a new Discovery Behavior or copy an existing one.
  3. Configure the behavior so that it only uses the required Discovery functionality/phases and excludes credential-less discovery-related activity.
  4. Navigate to Discovery > Discovery Schedules.
  5. Open the required schedule.
  6. In the Behavior field, select the Discovery Behavior you created.
  7. Save the schedule and test with a small IP range first.

This way, the change applies only to the schedules using that behavior and does not impact other Discovery schedules.

If the requirement is to disable credential-less discovery globally, that would be a different approach and should be reviewed carefully because it can affect identification/classification for multiple schedules. For schedule-specific control, Discovery Behavior is the safer and recommended option.

Also, after applying the behavior, review the Discovery Status and ECC Queue/logs for a test scan to confirm that credential-less classification/identification is no longer being triggered for that schedule.

 

*************************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb



0 Helpfuls