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
Here's a sample powershell function that uses a self-signed certificate uploaded to the Entra app registration to generate the access token and authorization header:
71
+
If `accessTokenAcceptedVersion` in the app manifest is set to 1, your application receives a v1.0 access token even though it's calling the v2 token endpoint.
72
+
73
+
The resource/scope value is the audience of the token. This API only accepts the following audiences:
74
+
-`https://management.core.windows.net/`
75
+
-`https://management.core.windows.net`
76
+
-`https://management.azure.com/`
77
+
-`https://management.azure.com`
78
+
79
+
80
+
### Assemble the request message
81
+
82
+
#### Request URI
83
+
API versioning: `api-version=2024-02-01-preview`<br>
`Authorization`: Contains the OAuth2 bearer token<br>
89
+
`Content-Type`: `application/json`
90
+
91
+
#### Request body
92
+
The JSON object for the body contains the following fields:
93
+
94
+
|Field name |Data Type |Description|
95
+
|---|---|---|
96
+
|`sourcesystem` (required) | string | Identify your source system name. The value `Microsoft Sentinel` is restricted.|
97
+
|`stixobjects` (required) | array | An array of STIX objects in [STIX 2.0 or 2.1 format](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.html#_muftrcpnf89v)|
98
+
99
+
Create the array of STIX objects using the STIX format specification. Some of the STIX property specifications are expanded here for your convenience with links to the relevant STIX document sections. Also note some properties, while valid for STIX, don't have corresponding object schema properties in Microsoft Sentinel.
100
+
101
+
>[!WARNING]
102
+
>If you're using a Microsoft Sentinel Logic App to connect to the upload API, note there are three threat intelligence actions available. Only use the [**Threat Intelligence - Upload STIX Objects (Preview)**](/connectors/azuresentinel/#threat-intelligence---upload-stix-objects-(preview)). The other two will fail with this endpoint and JSON body fields.
103
+
104
+
#### Sample request message
105
+
106
+
Here's a sample PowerShell function that uses a self-signed certificate uploaded to an Entra app registration to generate the access token and authorization header:
If `accessTokenAcceptedVersion` in the app manifest is set to 1, your application receives a v1.0 access token even though it's calling the v2 token endpoint.
125
-
126
-
The resource/scope value is the audience of the token. This API only accepts the following audiences:
127
-
-`https://management.core.windows.net/`
128
-
-`https://management.core.windows.net`
129
-
-`https://management.azure.com/`
130
-
-`https://management.azure.com`
131
-
132
-
133
-
### Assemble the request message
134
-
135
-
#### Request URI
136
-
API versioning: `api-version=2024-02-01-preview`<br>
`Authorization`: Contains the OAuth2 bearer token<br>
142
-
`Content-Type`: `application/json`
143
-
144
-
#### Request body
145
-
The JSON object for the body contains the following fields:
146
-
147
-
|Field name |Data Type |Description|
148
-
|---|---|---|
149
-
|`sourcesystem` (required) | string | Identify your source system name. The value `Microsoft Sentinel` is restricted.|
150
-
|`stixobjects` (required) | array | An array of STIX objects in [STIX 2.0 or 2.1 format](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.html#_muftrcpnf89v)|
151
-
152
-
Create the array of STIX objects using the STIX format specification. Some of the STIX property specifications are expanded here for your convenience with links to the relevant STIX document sections. Also note some properties, while valid for STIX, don't have corresponding object schema properties in Microsoft Sentinel.
153
-
154
159
#### Common properties
155
160
156
161
All the objects you import with the upload API share these common properties.
0 commit comments