Skip to content

Commit 6f942a7

Browse files
author
David Curwin
committed
Change to security admin
1 parent 1cfce31 commit 6f942a7

File tree

1 file changed

+35
-35
lines changed

1 file changed

+35
-35
lines changed

articles/defender-for-cloud/integration-servicenow.md

Lines changed: 35 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,15 @@ ms.date: 11/13/2023
1212

1313
ServiceNow is a cloud-based workflow automation and enterprise-oriented solution that enables organizations to manage and track digital workflows within a unified, robust platform. ServiceNow helps to improve operational efficiencies by streamlining and automating routine work tasks and delivers resilient services that help increase your productivity.
1414

15-
ServiceNow is now integrated with Microsoft Defender for Cloud, which enables customers to connect ServiceNow to their Defender for Cloud environment to prioritize remediation of recommendations that impact your business. Microsoft Defender for Cloud integrates with the ITSM module (incident management). As part of this connection, customers will be able to create/view ServiceNow tickets (linked to recommendations) from Microsoft Defender for Cloud.
15+
ServiceNow is now integrated with Microsoft Defender for Cloud, which enables customers to connect ServiceNow to their Defender for Cloud environment to prioritize remediation of recommendations that impact your business. Microsoft Defender for Cloud integrates with the ITSM module (incident management). As part of this connection, customers can create/view ServiceNow tickets (linked to recommendations) from Microsoft Defender for Cloud.
1616

1717
## Common use cases and scenarios
1818

19-
As part of the integration, you can create and monitor tickets in ServiceNow directly from Microsoft Defender for Cloud:  
19+
As part of the integration, you can create and monitor tickets in ServiceNow directly from Microsoft Defender for Cloud:
2020

21-
- **Incident**: An incident is an unplanned interruption of reduction in the quality of an IT service. It can be reported by a user or monitoring system. ServiceNow’s incident management module helps IT teams track and manage incidents, from initial reporting to resolution.
22-
- **Problem**: A problem is the underlying cause of one or more incidents. It’s often a recurring or persistent issue that needs to be addressed to prevent future incidents.  
23-
- **Change**: A change is a planned alternation or addition to an IT service or its supporting infrastructure. A change management module helps IT teams plan, approve, and execute changes in a controlled and systematic manner. It minimizes the risk of service disruptions and maintains service quality.  
21+
- **Incident**: An incident is an unplanned interruption of reduction in the quality of an IT service. It can be reported by a user or monitoring system. ServiceNow’s incident management module helps IT teams track and manage incidents, from initial reporting to resolution.
22+
- **Problem**: A problem is the underlying cause of one or more incidents. It’s often a recurring or persistent issue that needs to be addressed to prevent future incidents.
23+
- **Change**: A change is a planned alternation or addition to an IT service or its supporting infrastructure. A change management module helps IT teams plan, approve, and execute changes in a controlled and systematic manner. It minimizes the risk of service disruptions and maintains service quality.
2424

2525
## Preview prerequisites
2626

@@ -32,42 +32,42 @@ As part of the integration, you can create and monitor tickets in ServiceNow dir
3232

3333
## Create an application registry in ServiceNOW
3434

35-
To onboard ServiceNow to Defender for Cloud, you need a Client ID and Client Secret for the ServiceNow instance. If you don't have a Client ID and Client Secret, follow these steps to create them:
35+
To onboard ServiceNow to Defender for Cloud, you need a Client ID and Client Secret for the ServiceNow instance. If you don't have a Client ID and Client Secret, follow these steps to create them:
3636

3737
1. Sign in to ServiceNow with an account that has permission to modify the Application Registry.
38-
1. Browse to **System OAuth**, click **Application Registry**.
38+
1. Browse to **System OAuth**, and select **Application Registry**.
3939

4040
:::image type="content" border="true" source="./media/integration-servicenow/app-registry.png" alt-text="Screenshot of application registry.":::
4141

42-
1. In the upper right corner, click **New**.
42+
1. In the upper right corner, select **New**.
4343

4444
:::image type="content" border="true" source="./media/integration-servicenow/new.png" alt-text="Screenshot of where to start a new instance.":::
4545

4646
1. Select **Create an OAuth API endpoint for external clients**.
4747

4848
:::image type="content" border="true" source="./media/integration-servicenow/endpoint.png" alt-text="Screenshot of where to create an OAUTH API endpoint.":::
4949

50-
1. Complete the OAuth Client application details to create a Client ID and Client
50+
1. Complete the OAuth Client application details to create a Client ID and Client
5151
Secret:
5252
- **Name**: A descriptive name (for example, MDCIntegrationSNOW)
5353
- **Client ID**: Client ID is automatically generated by the ServiceNow OAuth server.
5454
- **Client Secret**: Enter a secret, or leave it blank to automatically generate the Client Secret for the OAuth application.
55-
- **Refresh Token Lifespan**: Time in seconds that the refresh token is valid.
55+
- **Refresh Token Lifespan**: Time in seconds that the refresh token is valid.
5656
- **Access Token Lifespan**: Time in seconds that the access token is valid.
5757

5858
>[!NOTE]
5959
>The default value of Refresh Token Lifespan is too small. Increase the value as much as possible so that you don't need to refresh the token soon.
6060
6161
:::image type="content" border="true" source="./media/integration-servicenow/app-details.png" alt-text="Screenshot of application details.":::
6262

63-
1. Click **Submit** to save the API Client ID and Client Secret.
63+
1. Select **Submit** to save the API Client ID and Client Secret.
6464

6565
After you complete these steps, you can use this integration name (MDCIntegrationSNOW in our example) to connect ServiceNow to Microsoft Defender for Cloud.
6666

6767
## Create ServiceNow Integration with Microsoft Defender for Cloud
6868

69-
1. Sign in to [the Azure portal](https://aka.ms/integrations) as at least a [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator) and navigate to **Microsoft Defender for Cloud** > **Environment settings**.
70-
1. Click **Integrations** to connect your environment to a third-party ticketing system, which is ServiceNow in this scenario.
69+
1. Sign in to [the Azure portal](https://aka.ms/integrations) as at least a Security Admin and navigate to **Microsoft Defender for Cloud** > **Environment settings**.
70+
1. Select **Integrations** to connect your environment to a third-party ticketing system, which is ServiceNow in this scenario.
7171

7272
:::image type="content" border="true" source="./media/integration-servicenow/integrations.png" alt-text="Screenshot of integrations.":::
7373

@@ -76,44 +76,44 @@ After you complete these steps, you can use this integration name (MDCIntegratio
7676
:::image type="content" border="true" source="./media/integration-servicenow/add-servicenow.png" alt-text="Screenshot of how to add ServiceNow.":::
7777

7878
Use the instance URL, name, password, Client ID, and Client Secret that you previously created for the application registry to help complete the ServiceNow general information.
79-
80-
Based on your permissions, you can create an **Integration** by using:
81-
79+
80+
Based on your permissions, you can create an **Integration** by using:
81+
8282
- Management group
8383
- Subscription (API only, to reduce subscription level onboardings)
8484
- Master connector
85-
- Connector
85+
- Connector
8686

87-
For simplicity, We recommend creating the integration on the higher scope based on the user permissions. For example, if you have permission for a management group, you could create a single integration of a management group rather than create integrations in each one of the subscriptions.
87+
For simplicity, We recommend creating the integration on the higher scope based on the user permissions. For example, if you have permission for a management group, you could create a single integration of a management group rather than create integrations in each one of the subscriptions.
8888

8989
1. Choose **Default** or **Customized** based on your requirement.
90-
90+
9191
The default option creates a Title, Description and Short description in the backend. The customized option lets you choose other fields such as **Incident data**, **Problems data**, and **Changes data**.
9292

9393
:::image type="content" border="true" source="./media/integration-servicenow/customize-fields.png" alt-text="Screenshot of how to customize fields.":::
9494

95-
If you click the drop-down menu, you see **Assigned to**, **Caller**, and **Short description** are grayed out because those are necessary fields. You can choose other fields such as **Assignment group**, **Description**, **Impact**, or **Urgency**.
95+
If you select the drop-down menu, you see **Assigned to**, **Caller**, and **Short description** are grayed out because those are necessary fields. You can choose other fields such as **Assignment group**, **Description**, **Impact**, or **Urgency**.
9696

9797
:::image type="content" border="true" source="./media/integration-servicenow/customize-fields.png" alt-text="Screenshot of how to customize fields.":::
9898

99-
1. A notice appears after successful creation of integration.
99+
1. A notice appears after successful creation of integration.
100100

101101
:::image type="content" border="true" source="./media/integration-servicenow/notice.png" alt-text="Screenshot of notice after successful creation of integration.":::
102102

103-
You can review the integrations in ARG both on the individual integration or on all integrations.
103+
You can review the integrations in ARG both on the individual integration or on all integrations.
104104

105105
:::image type="content" border="true" source="./media/integration-servicenow/all-integrations.png" alt-text="Screenshot of all integrations.":::
106106

107-
You can review an integration, or all integrations, in [Azure Resource Graph (ARG)](/azure/governance/resource-graph), an Azure service that gives you the ability to query across multiple subscriptions. On the Integrations page, click **Open in ARG** to explore the details in ARG.
107+
You can review an integration, or all integrations, in [Azure Resource Graph (ARG)](/azure/governance/resource-graph), an Azure service that gives you the ability to query across multiple subscriptions. On the Integrations page, select **Open in ARG** to explore the details in ARG.
108108

109109
:::image type="content" border="true" source="./media/integration-servicenow/open.png" alt-text="Screenshot of how to open in ARG.":::
110110

111111
## Create a new ticket from Microsoft Defender for Cloud recommendation to ServiceNow
112112

113113
Security admins can now create and assign tickets directly from the Microsoft Defender for Cloud portal.
114114

115-
1. Navigate to **Microsoft Defender for Cloud** > **Recommendations** and select any recommendation with unhealthy resources that you want to create a ServiceNow ticket for and assign an owner to.
116-
1. Click the resource from the unhealthy resources and click **Create assignment**.
115+
1. Navigate to **Microsoft Defender for Cloud** > **Recommendations** and select any recommendation with unhealthy resources that you want to create a ServiceNow ticket for and assign an owner to.
116+
1. Select the resource from the unhealthy resources and select **Create assignment**.
117117

118118
:::image type="content" border="true" source="./media/integration-servicenow/create-assignment.png" alt-text="Screenshot of how to create an assignment.":::
119119

@@ -124,16 +124,16 @@ Security admins can now create and assign tickets directly from the Microsoft De
124124
- ServiceNow ticket type – Choose **incident**, **change request**, or **problem**.
125125

126126
>[!NOTE]
127-
>In ServiceNow, there are several types of tickets that can be used to manage and track different types of incidents, requests, and tasks. Only incident, change request, and problem are supported with this integration.
127+
>In ServiceNow, there are several types of tickets that can be used to manage and track different types of incidents, requests, and tasks. Only incident, change request, and problem are supported with this integration.
128128
129129
:::image type="content" border="true" source="./media/integration-servicenow/assignment-type.png" alt-text="Screenshot of how to complete the assignment type.":::
130130

131131
To assign an affected recommendation to an owner who resides in ServiceNow, we provide a new unified experience for all platforms. Under **Assignment details**, complete the following fields:
132-
133-
- **Assigned to**: Choose the owner whom you would like to assign the affected recommendation to.
134-
- **Caller**: Represents the user defining the assignment.
135-
- **Description and Short Description**: If you chose a default integration earlier, description, and short description are automatically completed.
136-
- **Remediation timeframe**: Choose the remediation timeframe to desired deadline for the recommendation to be remediated.
132+
133+
- **Assigned to**: Choose the owner whom you would like to assign the affected recommendation to.
134+
- **Caller**: Represents the user defining the assignment.
135+
- **Description and Short Description**: If you chose a default integration earlier, description, and short description are automatically completed.
136+
- **Remediation timeframe**: Choose the remediation timeframe to desired deadline for the recommendation to be remediated.
137137
- **Apply Grace Period**: You can apply a grace period so that the resources that are given a due date don’t affect your Secure Score until they’re overdue.
138138
- **Set Email Notifications**: You can send a reminder to the owners or the owner’s direct manager.
139139

@@ -143,19 +143,19 @@ Security admins can now create and assign tickets directly from the Microsoft De
143143

144144
:::image type="content" border="true" source="./media/integration-servicenow/ticket.png" alt-text="Screenshot of a ticket ID.":::
145145

146-
Click the Ticket ID to go to the newly created incident in the ServiceNow portal.
146+
Select the Ticket ID to go to the newly created incident in the ServiceNow portal.
147147

148148
:::image type="content" border="true" source="./media/integration-servicenow/incident.png" alt-text="Screenshot of an incident.":::
149149

150150
>[!NOTE]
151-
>When integration is deleted, all the assignments will be deleted. It could take up to 24 hrs.
151+
>When integration is deleted, all the assignments will be deleted. It could take up to 24 hrs.
152152
153153
## Bidirectional synchronization
154154

155155
ServiceNow and Microsoft Defender for Cloud automatically synchronize the status of the tickets between the platforms, which includes:
156156

157-
- A verification that a ticket state is still **In progress**. If the ticket state is changed to **Resolved**, **Cancelled**, or **Closed** in ServiceNow, the change is synchronized to Microsoft Defender for Cloud and delete the assignment.
158-
- When the ticket owner is changed in ServiceNow, the assignment owner is updated in Microsoft Defender for Cloud.
157+
- A verification that a ticket state is still **In progress**. If the ticket state is changed to **Resolved**, **Canceled**, or **Closed** in ServiceNow, the change is synchronized to Microsoft Defender for Cloud and delete the assignment.
158+
- When the ticket owner is changed in ServiceNow, the assignment owner is updated in Microsoft Defender for Cloud.
159159

160160
>[!NOTE]
161161
>Synchronization occurs every 24 hrs.

0 commit comments

Comments
 (0)