Entity Intelligence
This is the layer that turns an observed hostname into a named organization, incorporated somewhere, owned by someone, and subject to a legal regime. Not every one of them is a company you would have chosen.
Every other part of SCVue deals in domains, addresses and files. This one deals in organizations. It cross-references everything observed in your traffic against SCVue's intelligence catalog, and, in the part that makes it usable, marks which entities are actually present in the traffic you are looking at, rather than merely existing in it.
A hostname cannot be sanctioned, cannot be a subsidiary, and cannot appear on a watch list. The company operating it can be all three.
Every company identified in the supply chain, with its home country, category, role in the chain, and the domains it operates. Alongside them, the key people connected to those companies, with role and country, which is what supports beneficial ownership and politically exposed person (PEP) checks against the suppliers you actually use.
Red flags about who has influence over your supply chain, grouped by jurisdiction, supply chain history, privacy behavior, and concentration. Sanctions screening names the entity, the list it appears on, the specific program, and its country.
The products, libraries, frameworks and services identified in the chain, with vendor, category, ecosystem, known versions and license: an SBOM for the browser-side supply chain, built from what was observed loading. Every license found is listed with the products carrying it, and categories differ substantially in what they demand.
The owning entity behind each domain, with its city, region, country, website, privacy policy and terms. Every field is editable, so your own research becomes part of the record.
Details arrive automatically where the catalog already covers a domain, and any domain it has not already resolved can be enriched on demand.
Where a catalog entry is not enough, nDiligence profiles back the record with on-demand enhanced reports and analyst research: beneficial ownership, financial integrity and patterns of influence, human reviewed.
Sanctions exposure through a third-party script is exposure nonetheless, and it is not something a vendor questionnaire will surface.
Ownership and network details entered by hand are stored globally and reused across every application that touches the same domain, so establishing who owns something is work done once rather than once per assessment.
Capture a session in the browser, import it, and read what comes back. A free community account is available immediately.