See what falls when one asset fails
The website depends on the hosting, and the hosting depends on the domain. On Professional, you record which assets are connected, and Ejerblik shows the domino effect: every asset hit directly or indirectly if one asset fails or changes owner.
An asset rarely stands alone.
The asset register shows what the company owns, but not what depends on what. Email depends on the domain, the webshop on the payment solution and the website on the hosting. That knowledge usually sits in the head of whoever set it up.
On Professional, you record the relationships as simple statements: this asset depends on that asset, with an optional short description such as "DNS setup" or "hosting contract". Relationships go one way. The website depending on the hosting does not mean the hosting depends on the website.
Click an asset and you see three things: what it depends on, what depends on it, and the domino effect, the whole chain of assets affected if you lose access to it.
One lapsed domain can take the whole chain with it.
Ejerblik works out the chain for you. If the website depends on the hosting, and the hosting on the domain, both hosting and website appear under the domain's domino effect, even though you only recorded the two links separately.
A typical example: the domain is not renewed because the payment card on it has expired. Email stops working, the website disappears, and the webshop's order confirmations do not arrive. In the list of assets with relationships, the domain carries a badge with the number of assets in its chain, so you can see it in advance.
You can prioritise by consequence, not just by risk level. The asset with the longest chain is where two-factor authentication (2FA), a second administrator and a renewal date in the register make the biggest difference.
When the owner leaves, the chain goes too.
The register shows who owns and is responsible for each asset. The relationships show what depends on it. Together they tell you what is at stake when an employee leaves or a supplier relationship ends.
A typical example: the agency that built the website is listed as the owner of the domain. The partnership ends, and it turns out that email, the website and the booking system all depend on an asset the company does not hold the keys to. With the relationships recorded, you see it before the partnership ends, not afterwards.
You know which assets to hand over first, and what follows once they are in place.
The dependencies are in writing, not in one person's head.
The relationships live in Ejerblik alongside the rest of the register. They are not a drawing in a slide deck that was made once and never updated. Remove a relationship, and the chain is corrected straight away.
A typical example: in a sale, the buyer's lawyer asks for documentation of which systems are critical and what they depend on. The answer is in the register rather than with the one employee who set everything up.
The company becomes less dependent on individuals, and you can answer when someone asks.
From invisible to visible risk
The domino effect worked out
Click an asset and see every asset hit directly or indirectly if it fails.
Critical links flagged
Assets that others depend on get a badge with the number of assets in their chain, so you can spot the critical links in the list.
A clear handover
When an employee or a supplier leaves, you know which assets need a new owner, and what depends on them.
The relationships drawn out
Select a person to see what leaves with them.
Questions and answers
Which asset would take the most others down with it?
Create a free account and map your assets. Relationships and the domino effect come with Professional.
No lock-in · Data in the EU · Support in English