Skip to content

Commit f1c38d7

Browse files
update legacy upload API
1 parent d38f695 commit f1c38d7

File tree

3 files changed

+64
-25
lines changed

3 files changed

+64
-25
lines changed
11.3 KB
Loading

articles/sentinel/stix-objects-api.md

Lines changed: 40 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,9 @@ Structured Threat Information Expression (STIX) is a language for expressing cyb
2525

2626
For more information, see [Introduction to STIX](https://oasis-open.github.io/cti-documentation/stix/intro.html).
2727

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+
2831
## Call the API
2932

3033
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`.
270273

271274
### Other samples
272275

273-
#### Stix Indicator
276+
#### Sample indicator
274277

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.
276279

277280
```json
278281
{
@@ -340,7 +343,17 @@ In this example, the indicator is marked with green TLP and uses extension attri
340343
"phase_name": "reconnaissance"
341344
}
342345
]
343-
},
346+
}
347+
]
348+
}
349+
```
350+
351+
#### Sample attack pattern
352+
353+
```json
354+
{
355+
"sourcesystem": "TestStixObjects",
356+
"stixobjects": [
344357
{
345358
"type": "attack-pattern",
346359
"spec_version": "2.1",
@@ -394,8 +407,18 @@ In this example, the indicator is marked with green TLP and uses extension attri
394407
"alias_1",
395408
"alias_2"
396409
]
397-
},
398-
{
410+
}
411+
]
412+
}
413+
```
414+
415+
#### Sample relationship with threat actor and identity
416+
417+
```json
418+
{
419+
"sourcesystem": "TestStixObjects",
420+
"stixobjects": [
421+
{
399422
"type": "identity",
400423
"spec_version": "2.1",
401424
"id": "identity--733c5838-34d9-4fbf-949c-62aba761184c",
@@ -552,8 +575,18 @@ In this example, the indicator is marked with green TLP and uses extension attri
552575
"lang": "en"
553576
}
554577
]
555-
},
556-
{
578+
}
579+
]
580+
}
581+
```
582+
583+
#### Sample using STIX 2.0
584+
585+
```json
586+
{
587+
"sourcesystem": "TestStixObjects",
588+
"stixobjects": [
589+
{
557590
"type": "indicator",
558591
"spec_version": "2.0",
559592
"id": "indicator--10000001-71a2-445c-ab86-927291df48f8",

articles/sentinel/upload-indicators-api.md

Lines changed: 24 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,20 @@
11
---
2-
title: Import threat intelligence with the upload indicators API
2+
title: Reference the legacy upload indicators API
33
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.
55
author: austinmccollum
66
ms.topic: reference
77
ms.date: 05/23/2023
88
ms.author: austinmc
99
---
1010

11-
# Reference the upload indicators API (Preview) to import threat intelligence to Microsoft Sentinel
11+
# Reference the legacy upload indicators API
1212

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.
1414

1515
> [!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.
1718
>
1819
1920
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
6263

6364

6465
### 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.":::
69+
70+
1. Connector action name: **Threat Intelligence - Upload Indicators of Compromise (Deprecated)**
71+
- Endppoint: `https://sentinelus.azure-api.net/{workspaceId}/threatintelligence:upload-indicators`
72+
- array of indicators name: `value`
73+
74+
1. Connector action name: **Threat Intelligence - Upload Indicators of Compromise (V2) (Preview)**
75+
- Endpoint: `https://sentinelus.azure-api.net/{workspaceId}/threatintelligenceindicators:upload`
76+
- array of indicators name: `indicators`
6577

6678
#### Request URI
67-
API versioning: `api-version=2022-07-01`<br>
68-
Endpoint: `https://sentinelus.azure-api.net/{workspaceId}/threatintelligence:upload-indicators?api-version=2022-07-01`<br>
79+
API versioning: `api-version=2022-12-01`<br>
80+
Endpoint: `https://sentinelus.azure-api.net/{workspaceId}/threatintelligenceindicators:upload?api-version=2022-12-01`<br>
6981
Method: `POST`<br>
7082

7183
#### Request header
@@ -78,7 +90,7 @@ The JSON object for the body contains the following fields:
7890
|Field name |Data Type |Description|
7991
|---|---|---|
8092
|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) |
8294

8395
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.
8496

@@ -119,7 +131,7 @@ The response header contains an HTTP status code. Reference this table for more
119131
|**401** | Unauthorized. |
120132
|**404** | File not found. Usually this error occurs when the workspace ID isn't found. |
121133
|**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. |
123135

124136
The response body is an array of error messages in JSON format:
125137

@@ -155,7 +167,7 @@ Approximately 10,000 indicators per minute is the maximum throughput before a th
155167
```json
156168
{
157169
"sourcesystem": "test",
158-
"value":[
170+
"indicators":[
159171
{
160172
"type": "indicator",
161173
"spec_version": "2.1",
@@ -242,12 +254,6 @@ If validation fails for one or more indicators, the response body is returned wi
242254
```
243255
The indicators are sent as an array, so the `recordIndex` begins at `0`.
244256

257+
## Next step
245258

246-
## Next steps
247-
248-
To learn more about how to work with threat intelligence in Microsoft Sentinel, see the following articles:
249-
250-
- [Understand threat intelligence](understand-threat-intelligence.md)
251-
- [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

Comments
 (0)