Prioritise IT by the business services it supports.
See what each service depends on
Knowing a service exists isn’t enough. Your team needs to see what it runs on, what connects to what and who owns each part.
Relationships between assets
Any two assets can hold a typed relationship, such as a website and the server it runs on.
Follow the chain
Start from an asset and follow its relationships to see what it supports and what supports it.
Ownership alongside
Owners are held as relationships too, so the person to call sits next to the dependency.
Build services from rules and end the diagram upkeep
A severity score treats a payments server and a test system alike. Your organisation knows the difference, and Rebasoft captures that judgement once and carries it into the ranking.
Rule-based or manual membership
Membership comes from rules, from your own selections, or from both.
Nested services
Services sit inside one another, reflecting how the business describes itself.
A focused start
Begin with the handful of services the organisation depends on, and the ranking reflects them from the outset.
Importance flows down, and vulnerability priority follows
Tagging assets one by one goes stale. A rating set on the service reaches its members, which saves your team the upkeep and keeps priorities aligned with the business.
A payments service receives high values for the qualities that matter to it, and that judgement is made once.
Lower-rated members inherit at a 0.8 factor, and a value set by an operator is preserved.
A flaw on a payments member rises above higher-CVSS flaws on less important systems in Today’s Work, with no re-tagging required.
Traffic reveals the members a service list has missed
A service list kept by hand drifts from reality. With flow exports in place, Rebasoft proposes the hosts that belong, and your engineer makes the decision.
- 10:15
An engineer opens Discovered Members
For the mail service, Rebasoft shows the ports its members serve and the ports they call.
- 10:16
One host matches the pattern
It serves the same front door and calls the same backends, yet it has never been recorded as part of the service.
- 10:18
Workstations are set aside
They are listed as consumers, with the reason they were not proposed, because using a service does not make a machine part of it.
- 10:20
The engineer accepts the proposal
The decision rests with a person, and a host joins a service once it has been accepted.
- Next ranking
Importance reaches the new member
The host inherits the importance of the mail service, and its vulnerabilities are ranked accordingly.
A composite of real customer situations. Times are illustrative.
Service Rankings show vulnerabilities by business service
Boards ask about payments rather than CVEs. Service Rankings give you that answer in the terms the business uses.
Ranked by service
Vulnerabilities and finding SLA roll up from members to their service, showing which service carries the most.
Unassigned assets
Assets that belong to no service are listed, along with the findings they hold.
No false assurance
A service with no rollup is shown as not evaluated.
From the blog
7 Best SaaS Discovery Tools for Clearer Control
Compare the best SaaS discovery tools for continuous visibility, risk prioritisation and audit-ready evidence across your organisation’s cloud estate.
Read article
How to Classify Critical Assets by Business Impact
Learn how to classify critical assets using service context, dependency mapping and evidence to reduce cyber risk, improve resilience and focus action.
Read article
CMDB Versus Asset Discovery: What You Need
CMDB versus asset discovery: understand what each delivers, where records fail, and how visibility strengthens risk, resilience and audit evidence daily.
Read articleWho decides what belongs in a service?
What does setup involve?
What does this show when a device fails?
More questions? See the full Rebasoft FAQ — answers by topic and by role, or how Rebasoft is priced.
Start with a service your organisation depends on
In thirty minutes on a live console, you will see how a service is built, how importance flows and how members are proposed.