How Discovery works

The network already knows what is on it.

ARKYPEL reads what your infrastructure and tools already record, identifies every device from how it talks, and asks one targeted question only where doubt remains. Here is how, step by step.

Diagram: eight record sources (switch tables, directory and identity, DHCP, virtualization, Wi-Fi and RADIUS, vulnerability scanners, IT service management, endpoint security) feed one read-only collector on site, then a correlator, then a live inventory. Each inventory row lists the sources that saw the asset, a confidence bar and a CMDB status. dc-paris-01, a domain controller, is seen by the directory, DHCP, a switch table and the endpoint agent, with high confidence. shadow-01 is seen only by the Wi-Fi controllers, low confidence, status ARKYPEL only.
01 Enumerate

Read the records you already have.

Every switch, directory, DHCP server, hypervisor and security tool keeps a partial list of what is on your network. None of them is complete. Together, they come close. ARKYPEL reads each one with read-only access and merges them into one inventory.

Reads from the tools you already run.

Directory and identity
  • Active Directory
Network
  • Aruba
  • Switch tables
  • DHCP
  • Wi-Fi controllers
  • RADIUS
Virtualization
Vulnerability scanners
IT service management
Endpoint security
  • Microsoft Defender
Also
  • Network capture (optional)

What each source tells us.

  • How it is read
    SNMP, read-only.
    What is read
    • MAC address
    • Switch, port, VLAN
    • ARP (IP to MAC)
    • LLDP / CDP neighbors
    What it tells us
    Where every device is plugged in.
Correlate

More witnesses, more certainty.

Every source is a witness. A device seen by the directory, DHCP, a switch and the endpoint agent is certain. A device seen only by a switch exists, sits on a known port, and moves on to typing.

Two asset cards. dc-paris-01 is seen by four witnesses: Directory, DHCP, Switch table and Endpoint agent, and its existence meter reads Certain. An unlabeled device known only by its MAC address is seen by the switch table alone; its meter reads Exists, and it is tagged Moves to typing.
02 Type

Every device betrays what it is, without being asked.

A passive engine identifies each device from how it already talks: network stack behavior, DHCP, the outer layer of encrypted sessions, industrial protocols. Nothing is sent to the device.

Three devices identified passively. A Windows workstation, from its DHCP request, TCP handshake and TLS hello: Unknown, then Computer, then Windows workstation, high confidence. A printer, from its DHCP request, mDNS announce and TCP handshake: Unknown, then Embedded device, then Printer, high confidence. A PLC, from an industrial protocol and its TCP handshake: Unknown, then Industrial controller, then PLC, medium confidence. Nothing is sent to the device.
03 Resolve

Ask one question, only where doubt remains.

ARKYPEL knows which assets it is unsure about and picks the cheapest question that would settle each one. One lightweight query per uncertain IT device, then stop. Never an active packet in industrial zones. Credentialed inspection only on the servers you authorize.

Assets grouped in three zones: IT, Servers and OT. Most assets are identified. Each uncertain IT asset received exactly one lightweight question from the collector and is now identified. One server is marked for credentialed inspection, where authorized. The OT zone is labeled Observed only, zero active packets: no question enters it, and its uncertain assets stay as they are.

The order is about cost and safety, not about which method matters most. Records, observation and targeted questions run as one loop.

Reconcile

CMDBs are museums. Here is the gap.

ARKYPEL compares what your CMDB declares with what the network actually shows, and gives every asset a status.

  • MatchedDeclared and confirmed.
  • ConflictingDeclared, but the network says otherwise.
  • ARKYPEL onlyOn the network, missing from the CMDB.
The CMDB and the network compared asset by asset. dc-paris-01, printer-01 and ot-plc-01: declared and confirmed, status Matched. as400-legacy-01: declared retired, but still seen on a switch, status Conflicting. db-analytics-02 and shadow-01: on the network, missing from the CMDB, status ARKYPEL only.
Evidence per asset

Confidence, not a list.

Asset recordTyped
hostname
dc-paris-01
type
Domain controller
location
switch core-sw-02, port Gi1/0/14, VLAN 10
confidence
High
witnesses
Directory, DHCP, Switch table, Endpoint agent
CMDB status
Matched
Asset recordNot typable
hostname
(none)
type
Not typable
location
switch acc-sw-07, port Gi1/0/32, VLAN 40
confidence
Exists, type unknown
reason
Seen in the switch table only, no traffic on monitored segments, in an industrial zone where no question is asked.

Every line carries the evidence behind it, so your team can audit why we say a device is a PLC. When we cannot type a device, we say so, and why.

Deployment

One collector. Read-only. Hosted where you need it.

  1. 1

    Deploy one collector VM, air-gap capable.

  2. 2

    Issue read-only access: an SNMP user, an LDAP reader, a read-only hypervisor role, API tokens for your tools.

  3. 3

    First inventory, with evidence per asset.

  4. 4

    Continuous collection, so the inventory stays current.

No agent required on endpoints. Industrial zones are observed, never probed.

Continuous assessment

On top of the inventory, a continuous assessment.

ARKYPEL asset graph with assets grouped by network zone.
See how your network is really divided. Assets grouped by network zone, with the connections between them.
ARKYPEL attack path from an exposed gateway to the domain controller.
Follow the route to what matters. From an exposed gateway to the domain controller, hop by hop.
Prioritization
Risk that knows your environment.
Validation
Prove the path, or close it.

Product names and logos are trademarks of their respective owners. Their use on this page identifies the systems ARKYPEL is designed to read from and does not imply endorsement or partnership.