You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/stix-objects-api.md
+40-7Lines changed: 40 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,9 @@ Structured Threat Information Expression (STIX) is a language for expressing cyb
25
25
26
26
For more information, see [Introduction to STIX](https://oasis-open.github.io/cti-documentation/stix/intro.html).
27
27
28
+
> [!NOTE]
29
+
> The previous upload indicators API is now deprecated. If you need to reference that API while transitioning to the new STIX objects API, see [Legacy upload indicators API](upload-indicators-api.md).
30
+
28
31
## Call the API
29
32
30
33
A call to the STIX objects API has five components:
@@ -270,9 +273,9 @@ The indicators are sent as an array, so the `recordIndex` begins at `0`.
270
273
271
274
### Other samples
272
275
273
-
#### Stix Indicator
276
+
#### Sample indicator
274
277
275
-
In this example, the indicator is marked with green TLP and uses extension attributes of `toxicity` and `rank`. Although these properties are not in the Microsoft Sentinel schema for indicators, ingesting an indicator with these properties doesn't trigger an error. The properties just aren't referenced.
278
+
In this example, the indicator is marked with the green TLP. Additional extension attributes of `toxicity` and `rank` are also included. Although these properties are not in the Microsoft Sentinel schema for indicators, ingesting an indicator with these properties doesn't trigger an error. The properties just aren't referenced or indexed in the workspace.
276
279
277
280
```json
278
281
{
@@ -340,7 +343,17 @@ In this example, the indicator is marked with green TLP and uses extension attri
340
343
"phase_name": "reconnaissance"
341
344
}
342
345
]
343
-
},
346
+
}
347
+
]
348
+
}
349
+
```
350
+
351
+
#### Sample attack pattern
352
+
353
+
```json
354
+
{
355
+
"sourcesystem": "TestStixObjects",
356
+
"stixobjects": [
344
357
{
345
358
"type": "attack-pattern",
346
359
"spec_version": "2.1",
@@ -394,8 +407,18 @@ In this example, the indicator is marked with green TLP and uses extension attri
394
407
"alias_1",
395
408
"alias_2"
396
409
]
397
-
},
398
-
{
410
+
}
411
+
]
412
+
}
413
+
```
414
+
415
+
#### Sample relationship with threat actor and identity
Copy file name to clipboardExpand all lines: articles/sentinel/upload-indicators-api.md
+24-18Lines changed: 24 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,20 @@
1
1
---
2
-
title: Import threat intelligence with the upload indicators API
2
+
title: Reference the legacy upload indicators API
3
3
titleSuffix: Microsoft Sentinel
4
-
description: This article is a reference for the upload indicators API with an example request and response.
4
+
description: This article is a reference for the legacy upload indicators API with an example request and response.
5
5
author: austinmccollum
6
6
ms.topic: reference
7
7
ms.date: 05/23/2023
8
8
ms.author: austinmc
9
9
---
10
10
11
-
# Reference the upload indicators API (Preview) to import threat intelligence to Microsoft Sentinel
11
+
# Reference the legacy upload indicators API
12
12
13
-
The Microsoft Sentinel upload indicators API allows for threat intelligence platforms or custom applications to import indicators of compromise in the STIX format into a Microsoft Sentinel workspace. Whether you use the API with the [Microsoft Sentinel upload indicators API data connector](connect-threat-intelligence-upload-api.md) or as part of a custom solution, this document serves as a reference.
13
+
The Microsoft Sentinel upload indicators API allowed threat intelligence platforms or custom applications to import indicators of compromise in the STIX format into a Microsoft Sentinel workspace. This document serves as a reference to the legacy API.
14
14
15
15
> [!IMPORTANT]
16
-
> This API is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
16
+
> This API is in PREVIEW but no longer recommended. Use the new STIX objects API in preview to upload threat intelligence. For more information, see [STIX objects API](stix-objects-api.md).
17
+
> The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
17
18
>
18
19
19
20
An upload indicators API call has five components:
@@ -62,10 +63,21 @@ The resource/scope value is the audience of the token. This API only accepts the
62
63
63
64
64
65
### Assemble the request message
66
+
There were two versions of the legacy API. Depending on the endpoint, a different array name was required in the request body. This was also represented by two versions of the logic app connector action.
67
+
68
+
:::image type="content" source="media/stix-objects-api/logic-app-sentinel-connector-action-names.png" alt-text="Screenshot of logic app connector action names for Microsoft Sentinel upload indicators API.":::
@@ -78,7 +90,7 @@ The JSON object for the body contains the following fields:
78
90
|Field name |Data Type |Description|
79
91
|---|---|---|
80
92
|SourceSystem (required)| string | Identify your source system name. The value `Microsoft Sentinel` is restricted.|
81
-
|Value (required) | array | An array of indicators in [STIX 2.0 or 2.1 format](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.html#_muftrcpnf89v)|
93
+
|indicators (required) | array | An array of indicators in [STIX 2.0 or 2.1 format](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.html#_muftrcpnf89v)|
82
94
83
95
Create the array of indicators using the STIX 2.1 indicator format specification, which has been condensed here for your convenience with links to important sections. Also note some properties, while valid for STIX 2.1, don't have corresponding indicator properties in Microsoft Sentinel.
84
96
@@ -119,7 +131,7 @@ The response header contains an HTTP status code. Reference this table for more
119
131
|**401**| Unauthorized. |
120
132
|**404**| File not found. Usually this error occurs when the workspace ID isn't found. |
121
133
|**429**| The number of requests in a minute has exceeded. |
122
-
|**500** | Server error. Usually an error in the API or Microsoft Sentinel services.
134
+
|**500**| Server error. Usually an error in the API or Microsoft Sentinel services.|
123
135
124
136
The response body is an array of error messages in JSON format:
125
137
@@ -155,7 +167,7 @@ Approximately 10,000 indicators per minute is the maximum throughput before a th
155
167
```json
156
168
{
157
169
"sourcesystem": "test",
158
-
"value":[
170
+
"indicators":[
159
171
{
160
172
"type": "indicator",
161
173
"spec_version": "2.1",
@@ -242,12 +254,6 @@ If validation fails for one or more indicators, the response body is returned wi
242
254
```
243
255
The indicators are sent as an array, so the `recordIndex` begins at `0`.
244
256
257
+
## Next step
245
258
246
-
## Next steps
247
-
248
-
To learn more about how to work with threat intelligence in Microsoft Sentinel, see the following articles:
-[Work with threat indicators](work-with-threat-indicators.md)
252
-
-[Use matching analytics to detect threats](use-matching-analytics-to-detect-threats.md)
253
-
- Utilize the intelligence feed from Microsoft and [enable MDTI data connector](connect-mdti-data-connector.md)
259
+
This API is legacy. Please migrate to use the STIX objects API to upload threat intelligence. For more information, see [STIX objects API](stix-objects-api.md).
0 commit comments