This information is for all users of Isora GRC.
Third-party vendor product deployments, also known as product deployments, provide a way for you to track who is using a product and how they are using it. Keep in mind that third-party vendor products in inventory aren’t specifically owned by any particular unit. A deployment creates a relationship in Isora GRC between the product and a unit that actually uses the product. It’s also a convenient place for keeping track of details about how the product is being used and who is responsible for the product. You can also assign a data classification based on the type of data the product accesses.
Product Deployment Features
| Field name | Usage |
|---|---|
| Deploying Unit | The unit requesting to use the product or actually using the product. |
| Owning Unit(s)^{1} | Additional unit(s) responsible for this deployment. Usually this is the same as the Deploying Unit, but it doesn’t have to be. (For example, the HR might be utilizing a product that is maintained and managed by IT. In that case, HR is the deploying unit but IT is the owning unit.) |
| Owning User(s)^{1} | User(s) responsible for this deployment (they must have a user account in Isora GRC). |
| Environment | The type of deployment- usually dev, test, production etc (this is a customizable field). |
| Scope^{1} | The scope of the deployment (Enterprise, Team, Individual, Unit). |
| Vendor Contacts^{1} | Contact information for people who are knowledgeable about this product and/or deployment (usually people external to your organization, such as vendor representatives, but they could also be people within the organization who don’t have user accounts in Isora GRC). |
| Notes^{1} | Any additional info you’d like to document about the deployment. |
^{1}These are optional fields.
See also: Third-Party Vendor Product Intake How-To: Create a Third-Party Vendor Product Deployment