--- sourceDocument: Zurich Enterprise Architecture (formerly Application Portfolio Management) sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-portfolio-management Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Enterprise Architecture (formerly Application Portfolio Management) ft:clusterId : - appportman bundleId : - appportman workflow : - Technology --- # Governance, Risk, and Compliance - Legacy # Integrate with Governance, Risk, and Compliance to identify risks - Legacy {#ariaid-title1} Release version: Zurich Updated July 31, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Enterprise Architecture (formerly Application Portfolio Management) integrates with Governance, Risk, and Compliance (GRC) to help identify and assess risks on business applications. ## Before you begin Role required: admin ## About this task Using GRC application, you can analyze the risks associated with assets such as hardware, software, and business application. You can also identify and test controls associated with those risks as well as look at the audits that were conducted on those assets. This analysis helps the application owners to understand the risk of the business application effectively. The application owner can identify significant risks and compliance issues that the business applications are exposed to. This eliminates the need to engage an external auditing system and run the applications through the auditing process. Activate the following plugins to integrate Enterprise Architecture with GRC. ## Procedure 1. Navigate to AllSystem DefinitionPlugins. 2. Install the GRC: GRC Profile Dependencies (com.snc.grc_profile_dep) plugin. 3. Install the GRC: Vendor Risk Management Dependencies (com.snc.grc_vrm_dep) plugin. 4. Install GRC: Policy and Compliance Management Dependencies (com.snc.grc_policy_dep) plugin. This also requires installation of app-compliance from the ServiceNow app store. Note: The integration also requires certain applications that should be installed from the ServiceNow app store. See Request apps on the Store for instructions to download and activate them. ## What to do next [Create an entity referencing the business application](https://www.servicenow.com/docs/y0sMUUPBXQYQNPC7d2mB3g#create-audit-profile-refer-bus-app "Create an entity with reference to the business application table and its specific application record. Use the entity to scope risk exposure and perform risk assessments on business applications."). Attach the entity to an audit. ## Create audit entity for business application - Legacy {#ariaid-title2} Create an entity with reference to the business application table and its specific application record. Use the entity to scope risk exposure and perform risk assessments on business applications. ### Before you begin Role required: sn_audit.admin or sn_audit.manager ### About this task GRC uses the term, entity, instead of profile. An entity can be anything such as a database, server, or a business application that can be audited. ### Procedure 1. Navigate to AllAuditScopingAll Entities. 2. Click New. 3. On the form, fill in the fields. For field information, see [Entity Form](https://www.servicenow.com/docs/a6B70ehOR1TNIj8GqcQkGA "Entity is used to scope risk exposure and perform risk assessments on business applications."). 4. Click Submit. ## Associate a risk to the entity - Legacy {#ariaid-title3} Attach the entity to a risk and create a risk record. Assess and identify risks that can adversely affect your business applications. ### Before you begin Role required: sn_risk.admin and sn_risk.manager ### Procedure 1. Navigate to AllRiskRisk RegisterAll Risks. 2. Create a risk in the Risk form. See: Create a risk manually. Note: Relate the risk to the entity in the Entity field. ## Add business application entity to an engagement - Legacy {#ariaid-title4} The entities are assessed and evaluated for audit engagement. After which the entities that are scoped for audit engagement and validated are associated to an audit. ### Before you begin Role required: sn_audit.manager or sn_audit.admin To add a business application entity to an engagement, you should have created an entity referencing the business application in the Entity field of the Entity form. See: [Create an entity for audit referencing business application](https://www.servicenow.com/docs/y0sMUUPBXQYQNPC7d2mB3g#create-audit-profile-refer-bus-app "Create an entity with reference to the business application table and its specific application record. Use the entity to scope risk exposure and perform risk assessments on business applications."). ### Procedure 1. Navigate to AllAuditEngagementsAll Engagements. 2. To add the business application entity to the engagement, click Add button in the Entities related list. Note: The engagement must be in Scope or Validate state. See: Add profiles to an engagement scope. When an application profile is attached to an engagement, an engagement record with the associated profile is created in Profile to Engagements \[sn_audit_m2m_profile_engagement\] table. ## Add a control to the business application entity - Legacy {#ariaid-title5} Associate a control to a business application entity that might be at risk. It is mandatory that you set effective control on the business applications to mitigate risks and protect your business. As you upgrade your business applications, you can replace your outdated controls. ### Before you begin Role required: admin You should have created an entity before associating a control to it. Controls are created in GRC. ### Procedure To create a control and add an entity to the control, see Create a control. * The entity that you select from the Controls \[sn_compliance_control\] table must be a business application and the entity Class of the record must be application. * The control record can be either in the Draft or Retired state. However, controls in such states are not visible in Enterprise Architecture (formerly Application Portfolio Management) to be associated to a business application. {#business-app-entity-control__ul_czf_xqb_fjb} ## View Governance, Risk, and Compliance risks and engagements for business application - Legacy {#ariaid-title6} As an application owner, you can view the risks that a business application is exposed to. Governance, Risk, and Compliance (GRC) audits the business application entity and the audited risks and engagements are captured as scripted related lists in the business application form. ### Before you begin Role required: sn_apm.apm_user, sn_apm.business_stakeholder_apm_user ### Procedure 1. Navigate to AllEnterprise ArchitectureApplication PortfolioAll Business Applications. 2. Click GRC Risks related item. 3. Review the risk information. The risk statement name, description, and category (legal, financial, operational, and so on) are displayed. The inherent impact level and inherent likelihood of the risk occurring are also shown. See: Manage risks, risk statements, and risk frameworks 4. Click Engagements related item. 5. Review the engagement information. The engagement name, assigned user, state, planned start date, end date, completion percentage, and actual cost are displayed. See: Manage engagements 6. Click Controls related item. 7. Review the control information. The control name, owner, compliance status, classification (preventive, corrective, or detective), and attestation frequency are displayed. See: Manage controls 8. Click the display/hide hierarchical lists arrow beside a risk record in the GRC Risks related list. All controls associated to the risk of the business application are displayed. When you associate a control to a risk, the control with its associated risk is created in Risk to Control \[sn_risk_m2m_risk_control\] table. Figure 1. Controls associated to a risk *[\>]: and then