Discovery Schedule

What is a Discovery Schedule?

A discovery schedule is a configured set of instructions telling an asset discovery system when, where, and how to scan for devices and collect inventory data. Rather than manually initiating discovery scans whenever you need updated information, a discovery schedule automates the process, running scans on defined intervals—daily, weekly, monthly, or on-demand. Discovery schedules specify the target network ranges or individual systems to scan, the discovery methods to use (agent-based, SSH, SNMP, WMI, etc.), the credentials required for authentication, and what information should be collected during the scan.

Discovery schedules can be incredibly simple or highly sophisticated depending on organizational needs. A basic schedule might scan a single IP range using SNMP every Friday evening. A sophisticated schedule might define multiple target groups with different discovery methods for each—agents for Windows servers, SSH for Unix systems, SNMP for network devices, and API calls for cloud resources. Some organizations create tiered discovery schedules where full discovery runs monthly and incremental discovery runs weekly, balancing data freshness with network impact.

The execution of a discovery schedule follows a defined lifecycle. When a scheduled scan time arrives, the discovery system wakes up, establishes connections to target devices, authenticates using the configured credentials, executes the discovery queries, collects the responses, and stores the gathered data in the asset database. If the scan encounters problems—a device is offline, authentication fails, a network is unreachable—the discovery schedule typically continues trying other targets rather than aborting. After completion, the system logs results and can trigger alerts if significant issues are detected or if discovery success rates fall below defined thresholds.

Why It Matters

Discovery schedules transform asset inventory from a project into a continuous operation. Without scheduling, asset discovery requires someone to manually initiate scans, wait for completion, and review results. This manual approach leads to infrequent, irregular discovery cycles. Asset data goes stale between discovery runs, vulnerabilities appear in systems for months before discovery reveals them, new devices aren't cataloged until someone remembers to run another scan. Scheduled discovery eliminates this administrative burden and ensures that your asset database refreshes automatically based on a reliable cadence.

Scheduled discovery is essential for detecting changes in your IT environment. Compliance frameworks require organizations to maintain accurate asset documentation and demonstrate that they know what systems exist and what software is installed on them. With scheduled discovery, you can show auditors that your asset inventory was updated last week, and provide evidence of how it's changed since the previous scan. This continuous verification satisfies compliance requirements and creates an audit trail of your infrastructure state over time.

Discovery schedules also support rapid incident response and security operations. If a security team needs to understand what systems might be affected by a newly discovered vulnerability, they can reference asset inventory populated by discovery schedules to identify all vulnerable systems. If malware appears on a device, discovery schedules help determine whether it's spread to other systems. If a system fails, knowing its recent discovery data helps engineers understand its configuration and dependencies.

Different organizations schedule discovery at different frequencies depending on how volatile their infrastructure is. A static data center might schedule full discovery monthly with incremental updates monthly. A rapidly changing cloud-heavy organization might schedule discovery hourly to keep pace with auto-scaling, container orchestration, and rapid deployment cycles. Scheduling frequency becomes a tuning parameter that organizations optimize to balance infrastructure change velocity against discovery system load.

How Open-AudIT Helps

Open-AudIT includes flexible discovery scheduling capabilities allowing you to define discovery schedules for different networks, systems, and discovery methods. You can configure schedules to run on specific days and times, or on intervals throughout the day. The scheduling system tracks discovery success rates, logs all discovery activities, and maintains a history of what was discovered during each scan. You can then compare inventory data across discovery cycles to identify changes, track hardware aging, and ensure your asset database stays current as your infrastructure evolves.