A Proximity Snapshot is a focused external assessment that shows which suppliers are visibly connected to an organisation’s digital ecosystem and how close those relationships appear to critical systems. It uses externally observable evidence to identify supplier links and presents an initial Digital Proximity view without requiring software installation or access to internal networks. The snapshot is designed to give security and risk teams a practical starting point. It can reveal suppliers or dependencies missing from existing inventories, show the evidence behind selected relationships and demonstrate why supplier posture alone is not enough to prioritise risk. It is a sample of the broader continuous visibility available through ThingsRecon Supply Chain Intelligence, rather than a complete replacement for ongoing monitoring.

A ThingsRecon sample scan is an external-only automated assessment of a domain supplied and verified by the organisation. It returns a limited snapshot of discovered assets and, where relevant, supplier connections or proximity indicators. No software agents are installed and the scan does not require credentials to internal systems. The sample is designed to demonstrate the discovery process, the evidence attached to findings and the way ThingsRecon adds context to external exposure. It is narrower than a full deployment and should not be treated as a complete inventory or continuous monitoring programme. Current product information states that sample reports are generally delivered within 48 to 72 hours after verification. In practice, teams should record the supporting evidence, confirm ownership and business criticality, and connect the finding to an accountable workflow. This prevents a useful observation from becoming another isolated score or dashboard alert.

For a verified sample scan, current ThingsRecon product information states that initial sample reports are generally delivered within 48 to 72 hours. A full implementation timeline depends on scope, the number of domains and suppliers, integration requirements and the organisation’s validation and onboarding process. External discovery can begin without installing agents, which reduces technical deployment effort. The first results are still a starting point: teams need to validate ownership, classify critical assets and suppliers, and decide how findings will enter remediation or risk workflows. Continuous monitoring then builds the historical context needed to identify meaningful changes rather than treating the first scan as a finished inventory. In practice, teams should record the supporting evidence, confirm ownership and business criticality, and connect the finding to an accountable workflow. This prevents a useful observation from becoming another isolated score or dashboard alert.

A sample assessment can begin with a verified primary domain and basic confirmation that the organisation is authorised to request the scan. Broader deployments may also use known domains, business entities, subsidiaries, supplier lists or critical-system context to improve scope, attribution and prioritisation. ThingsRecon does not require software installation or credentials to begin external discovery. Providing existing inventories is useful for comparison, but it should not be treated as the boundary of discovery because one objective is to find assets and suppliers the organisation does not already know about. Business owners and criticality information can be added later to strengthen prioritisation and reporting. In practice, teams should record the supporting evidence, confirm ownership and business criticality, and connect the finding to an accountable workflow. This prevents a useful observation from becoming another isolated score or dashboard alert.