From a single create to a 5000-row streaming import: duplicate governance, the license gate, scanner enrichment, and a reconciled, audit-clean inventory.
This guide shows you how PMAP builds one asset inventory from three very different sources without producing duplicate rows. You will create assets by hand, run a bulk streaming import, and let scanner ingestion auto-populate the inventory, all under consistent duplicate handling. Along the way you will see how the license quota gate fails fast and how scanner enrichment merges technical detail under strict source precedence.
It is written for asset and vulnerability owners who reconcile machine-discovered and human-entered records. By the end you will be able to choose the right duplicate handling mode per source, respect the license gate that returns HTTP 402 before any insert, assign polymorphic owners, manage IP addresses, and verify full coverage on the asset detail page.
Inside this guide
- Read the Assets workspace and create one asset by hand while watching deduplication work.
- Choose the right duplicate handling mode of error, skip, or update for each ingestion source.
- Run a bulk streaming import of up to 5000 assets and import from Nmap and Masscan files.
- Understand the license quota gate and why a capped tenant fails fast with HTTP 402.
- Let scanner enrichment merge ports, services, technologies, and OS detail under field-level locking.
- Assign polymorphic owners and reconcile assets from scanners and manual sources.
- Bulk update tags, criticality, and the active flag, then export and verify the inventory.
Before you start
- A PMAP account with asset read, create, and export permissions (asset:create, asset:export) in your company scope.
- Your tenant’s asset license quota headroom, so you know how many assets you can still create before the cap returns HTTP 402.
- An ingestion source ready: a list to type by hand, an NDJSON batch of up to 5000 rows, or a scanner integration that auto-populates during ingestion.
- A naming and IP convention agreed for your environment, because duplicate detection matches by asset name and by IP within the company.
- Familiarity with your owner model of users and teams, with roles owner, custodian, and approver, so you can attribute responsibility as assets land.
