What the public preview shows
Public pages show normalized names, categories, statuses, risk labels, confidence scores, source counts, and selected non-sensitive source metrics. They intentionally do not expose source URLs or citation paths.
Methodology
How we turn public source records into buyer-readable reports.
We organize IoT Support Risk source records into searchable previews, paid report context, and clear verification questions for consumers, MSPs, cyber insurers, retailers, property managers, schools, and device vendors.
What paid reports add
Paid reports add the source trail, source-observed dates, report-generation context, interpretation notes, and a checklist tailored to the device being reviewed.
- Device/security signal snapshot
- Known exploited and exploitability interpretation where available
- Remediation and inventory-mapping checklist
- Locked source citations and monitoring path
How source records refresh
DataVerityHub checks configured sources on a schedule. Existing rows are updated when source keys match; changed rows preserve enough source history for verification and reporting.
What buyers should still verify
Security records are triage intelligence and should be validated against asset inventory, firmware versions, compensating controls, and vendor advisories.
Reports are designed to show what was checked, what was found, and what still needs direct confirmation.
Source groups, authority scores, and locked citation access are shown in the coverage registry on each product homepage.