Explore a Sonar target
Understand the data Sonar already has without launching network activity.
Use this guide to understand data Sonar already has without launching network activity. A target is operator shorthand for a program, optionally narrowed to one scope; the canonical entities live in the Inventory domain model.
Resolve the program
If the program ID is unknown, search first:
Use platform and search filters to disambiguate the result. Do not guess an ID from the display name. If the ID is already supplied by a trusted context, skip directly to the overview.
Map Inventory cheaply
Read:
- program identity and platform;
- current scopes and whether the intended boundary is represented; and
- counts by asset type.
The overview is a planning call, not a complete asset export. Use its counts to decide which lists are worth paging.
Drill into useful assets
- Start with
list_http_pathsfor live endpoints, status, response length, and discovery source. - Use
list_portsto map network services, optionally narrowed by IP. - Use
list_domainsandlist_ip_addressesto establish the surface and pivots. - Use
list_technologies,get_http_path_technologies, andget_port_technologiesto inspect fingerprints. - Use
list_mobiles,list_wildcards, andlist_cidrswhen the target overview shows those boundary types.
Page results instead of requesting a very large limit. Narrow by scopeId, parent asset, search,
or updatedAfter when the tool supports it.
Verify the decision
Before stopping or requesting new work, record:
- the program and optional scope used;
- which asset types and pages were actually read;
- the freshness filter, if any; and
- what is missing or stale enough to justify a scan.
An empty page is not proof
An empty page proves only that the selected page and filters returned no rows. It does not prove the target has no assets or no vulnerability.
If current Inventory is insufficient, continue to Run a bounded scan.