Overview
This article explains how asset inheritance works in Hyver. Some assets are part of a hierarchy, where child assets automatically inherit attributes from their parent — including visibility, relevancy, and scope. This helps streamline asset management and ensures consistent tracking across complex environments.
1. What is asset inheritance?
Hyver supports hierarchical relationships between assets. When one asset is a “child” of another, it automatically inherits key attributes from its “parent.”
These attributes include:
Visibility – Whether the asset is shown in reports and dashboards
Relevancy – Whether the asset is considered in risk calculations
Scope – Whether the asset is part of the current engagement’s analysis
2. How inheritance works
When you assign an attribute to a parent asset, that value is passed down to all child assets unless manually overridden.
For example:
A domain marked as “In Scope” will pass that status to all subdomains and URLs under it
A service will pass attributes to its related certificates
IP ranges act as root assets and pass scope to the individual IPs within them
3. What counts as a parent asset?
In Hyver’s model, the following are treated as root-level or parent assets:
Domains
IP addresses
IP ranges
All other assets (like URLs, certificates, services) are considered sub-assets and inherit attributes from these parents.
4. How inheritance affects engagement assets
Any asset included in an engagement’s content is automatically:
Relevant
Visible
In Scope
All child assets discovered under those parents will inherit these settings by default.
Important notes
Inherited attributes can be manually adjusted at the child level if needed
Using inheritance reduces the need to manually tag or define each sub-asset individually
Wrap-up / Next Steps
Asset inheritance makes it easier to manage complex asset structures without losing consistency. Define scope and relevancy once at the parent level — and let Hyver take care of the rest.