Owner Stakeholder Assignment

  • How are asset owners and other involved stakeholders correlated? For example, if one person is responsible for ticket but other people own the associated risk. Please demonstrate how this can be managed (CMDB, Active Directory OU, internally managed asset lists, etc.)
    • Asset ownership is easy to configure in RiskVision. You can specify one owner for an asset, another owner for a ticket, and another owner for any identified risk. Entities, such as assets or apps, can have multiple stakeholders, and we can integrate your Active Directory OU to use your existing role structure. Although this is all out of the box configuration, because of the flexibility in the tool, it's important to think through how you model this structure. For example, you may want to model both hardware components and software components as assets, each of which have owners. Once modeled, you can integrate with your existing technologies like your CMDB to perform the following operations:
      • Import your entities
      • Import the relationship of those entities to each other (i.e. Server1 hosts DB1 and App1),
      • Import the organizations hierarchy.
  • How granular can stakeholder assignment be? For example, one piece of software on a particular asset might have a different responsible party than another piece of software on that same asset.
    • Multiple owners can be assigned to assets, such as the primary owner, business owner, and executive owner. The types of ownership allows you to easily set up workflows and assign different owner types to different stages of the workflow. The ownership types are completely configurable.