Business services and dependency mapping

Prioritise IT by the business services it supports.

Define your business services once, map what they depend on, and Rebasoft ranks vulnerabilities by what your organisation actually runs on.
Business services Illustrative
Start from what the business runs
Customer Portal Business-critical Order Processing Important
importance flows down to members
Members 12 accepted Proposed 1 from traffic Nested 2 services
so a finding on a member ranks higher
Member Ranked up
vm-sql-02
Known exploited CVE Inherited importance
In the console

Every service, and where it stands

Each service shows its status, importance and subservices. Issues split into performance, vulnerability and compliance, and route to the right team.

Sample data.
Relationship and dependency mapping

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.

In the console

See how far a problem reaches

A failing subservice shared by several services outranks a single-service failure, and the assets behind it are listed beside it.

Sample data.
The service model

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.

The cascade

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.

01
You rate the service

A payments service receives high values for the qualities that matter to it, and that judgement is made once.

02
Members inherit the rating

Lower-rated members inherit at a 0.8 factor, and a value set by an operator is preserved.

03
The work list reorders

A flaw on a payments member rises above higher-CVSS flaws on less important systems in Today’s Work, with no re-tagging required.

The node nobody recorded

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.

  1. 10:15

    An engineer opens Discovered Members

    For the mail service, Rebasoft shows the ports its members serve and the ports they call.

  2. 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.

  3. 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.

  4. 10:20

    The engineer accepts the proposal

    The decision rests with a person, and a host joins a service once it has been accepted.

  5. 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.

In the console

Know which services need attention

Sort by importance, environment and owner, so the right team picks up the right service.

Sample data.
Service Rankings

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.

Green means checked, so a quiet service is not mistaken for a safe one.
In the console

Service Rankings in the console

Each service shows its SLA breaches, active KEVs and critical findings, with unassigned assets listed alongside.

From a Rebasoft demo estate. CIATV is the importance score shown in the console.
Common questions
Who decides what belongs in a service?
Your team does. You define services and set their importance, rules handle membership, and flow data proposes hosts for you to accept, so business judgement stays with the people who hold it.
What does setup involve?
Setup starts with a list of your services and a view of how much each one matters. Flow exports add the traffic proposals.
What does this show when a device fails?
Rebasoft shows which services the device belongs to, so your team knows straight away where to look.

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.