Asset discovery and ITAM

Which assets support your services, and what is missing?

Where an inventory stops at a device count, Rebasoft shows how far discovery reached, why it stopped and who resolves it.
Business service assurance live
Collected without agents, in a single inventory
UsersNetworkServersContainersCloud
organised into business services
Business service Business-critical
Customer Portal
Owner: IT Operations Tracked over time
feeds
OperationsSecurityGovernance
In the console

Every asset type, counted

Servers, hypervisors and cloud resources appear in one inventory, broken down by type.

From a Rebasoft demo estate.
The ladder

A six-stage ladder shows how well you know each asset

A device count says how many, and leaves you guessing how much you really know. The ladder tracks each asset from first detection to CMDB-ready, and security and compliance work starts from the third stage.

01
Detected

An address has been seen on the network.

02
Identified

The address is a known asset of a recognised type.

03
Inventoried

Collection has succeeded, and software and patch data are available.

04
Attributed

A named owner is responsible for the asset.

05
Asset-managed

Cover and warranty are in order.

06
CMDB-ready

The asset is complete enough to rely on as a configuration item.

A stalled discovery

Discovery gaps arrive with a cause and an owner

A failed-device report leaves your team to work out what went wrong. Rebasoft groups failures by cause and owner, which turns detective work into a short list of jobs.

  1. 08:50

    The ladder shows a stall

    The IT manager sees too few assets reaching Inventoried, a pattern that a device count would have hidden.

  2. 08:55

    Failures are grouped

    Discovery Progress clusters the failures, so she works through a short list of issues rather than a long list of devices.

  3. 09:05

    The pattern points to the cause

    Hosts that are down across many sites are usually powered-off desktops. The same number down in one subnet points to a routing change, so that cluster goes to the network team.

  4. 09:15

    Credentials are handled with care

    A rejected credential is reported separately from a missing one. Rejected credentials are not retried automatically, so collection does not resemble credential stuffing to your intrusion detection system.

  5. 09:30

    Each team receives its own work

    She passes each cluster to the team that can resolve it, and the ladder recalculates hourly as the fixes take effect.

A composite of real customer situations. Figures are illustrative.

Listed once

A single asset inventory, drawn from the sources you already run

Several tools usually mean several asset lists and a spreadsheet to settle the differences. Rebasoft ranks its sources, from your own entries through MDM, hypervisor, cloud, network and flow, so your team stops comparing lists and works from one set of facts.

Devices that leave management

When Intune stops listing a laptop that the network can still see, Rebasoft keeps it live and flags it as unenrolled. A list from one tool would lose it, and a working machine would drop out of view.

Protection against bad data

If a single pull would retire more than half of a group, Rebasoft refuses the list, so a credential that has lost its scope cannot empty your register.

Servers found through traffic

With flow exports in place, a host serving a stable port to many clients joins a review queue with its reasons, which surfaces hosts that credentials miss. Your team makes the decision.

Green means checked. An asset that could not be collected from is shown as blocked, which ends false assurance.
In one place

End-of-life, web and cloud data arrive with no manual research

Where a spreadsheet goes stale, these views refresh from collection. Contract, supplier, warranty, stock and entitlement fields sit alongside them, ready for your team to enter or import.

End of life from 17 sources

Your team sees what is leaving support, asset by asset, with no vendor research. Operating systems, applications and hardware are checked against 17 sources, updated weekly.

Web technology detection

Ageing WordPress and jQuery surface through 53 detection rules, with or without a device behind the site. Where a site reports PHP with no version and SSH collection covers the host, Rebasoft supplies the version from the installed package.

Cloud and virtual sources

One view takes the place of a console per platform. AWS and Azure arrive with a depth ladder for each VM, next to VMware, Proxmox and Hyper-V hosts and guests and Kubernetes clusters, pods and containers.

Field-proven since 2009

Discovery is where Rebasoft began

Network discovery has been the core of Rebasoft since 2009. It has been refined on live estates with customers and partners, so it copes with the legacy equipment and unexpected devices real networks contain.

Consolidation

Retire the asset spreadsheets

Asset and end-of-life spreadsheets
Can replace
Collected data takes the place of manual upkeep.
Standalone asset inventory tools
Can replace
Discovery, end-of-life tracking and ownership sit next to vulnerabilities, traffic and compliance evidence, in one deployment.
Common questions
Do we need an agent on each device?
No. Rebasoft is agentless, so there is nothing to deploy to endpoints or maintain. It uses ARP and switch tables, SNMP, SSH, PowerShell and WMI, along with the APIs of your cloud and virtual platforms.
What does setup involve?
Setup is straightforward: provide credentials for SNMP, SSH and Windows, and API access to your cloud, virtual and MDM platforms. The ladder then shows exactly where access is missing.
Where is our data held?
On your own infrastructure. Rebasoft deploys as virtual appliances in your environment, so your inventory stays with you.

More questions? See the full Rebasoft FAQ — answers by topic and by role, or how Rebasoft is priced.

See how far discovery reaches on an estate like yours

In thirty minutes on a live console, you will see the ladder, the blockers and the team each one belongs to.