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
*[Import the OpenTelemetry Bills of Materials (BOM)](https://opentelemetry.io/docs/zero-code/java/spring-boot-starter/getting-started/).
104
+
* Add the [Spring Cloud Azure Starter Monitor](https://mvnrepository.com/artifact/com.azure.spring/cloud-starter-azure-monitor) dependency.
105
+
* Follow [these instructions](/azure//developer/java/spring-framework/developer-guide-overview#configuring-spring-boot-3) for the Azure SDK JAR (Java Archive) files.
106
+
107
+
For Quarkus native applications:
108
+
* Add the [Quarkus OpenTelemetry Exporter for Azure](https://mvnrepository.com/artifact/io.quarkiverse.opentelemetry.exporter/quarkus-opentelemetry-exporter-azure) dependency.
109
+
95
110
#### [Node.js](#tab/nodejs)
96
111
97
112
Install these packages:
@@ -202,6 +217,11 @@ Point the Java virtual machine (JVM) to the jar file by adding `-javaagent:"path
202
217
> [!TIP]
203
218
> If you develop a Spring Boot application, you can optionally replace the JVM argument by a programmatic configuration. For more information, see [Using Azure Monitor Application Insights with Spring Boot](./java-spring-boot.md).
204
219
220
+
221
+
##### [Java-Native](#tab/java-native)
222
+
223
+
Several automatic instrumentations are enabled through configuration changes; no code changes are required
224
+
205
225
##### [Node.js](#tab/nodejs)
206
226
207
227
```typescript
@@ -222,7 +242,7 @@ from azure.monitor.opentelemetry import configure_azure_monitor
222
242
# Import the tracing api from the `opentelemetry` package.
223
243
from opentelemetry import trace
224
244
225
-
# Configure OpenTelemetry to use Azure Monitor with the
245
+
# Configure OpenTelemetry to use Azure Monitor with the
- To review the source code, see the [Azure Monitor Java autoinstrumentation GitHub repository](https://github.com/Microsoft/ApplicationInsights-Java).
347
-
- To learn more about OpenTelemetry and its community, see the [OpenTelemetry Java GitHub repository](https://github.com/open-telemetry/opentelemetry-java-instrumentation).
348
-
- To enable usage experiences, see [Enable web or browser user monitoring](javascript.md).
349
-
- See the [release notes](https://github.com/microsoft/ApplicationInsights-Java/releases) on GitHub.
370
+
- Review the source code in the [Azure Monitor Java autoinstrumentation GitHub repository](https://github.com/Microsoft/ApplicationInsights-Java).
371
+
- Learn more about OpenTelemetry and its community in the [OpenTelemetry Java GitHub repository](https://github.com/open-telemetry/opentelemetry-java-instrumentation).
372
+
- Enable usage experiences by seeing [Enable web or browser user monitoring](javascript.md).
373
+
- Review the [release notes](https://github.com/microsoft/ApplicationInsights-Java/releases) on GitHub.
374
+
375
+
### [Java Native](#tab/java-native)
376
+
- See [Add and modify Azure Monitor OpenTelemetry](opentelemetry-add-modify.md) for details on adding and modifying Azure Monitor OpenTelemetry.
377
+
- Review the source code in the [Azure Monitor OpenTelemetry Distro in Spring Boot native image Java application](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/spring/spring-cloud-azure-starter-monitor) and [Quarkus OpenTelemetry Exporter for Azure](https://github.com/quarkiverse/quarkus-opentelemetry-exporter/tree/main/quarkus-opentelemetry-exporter-azure).
378
+
- Learn more about OpenTelemetry and its community in the [OpenTelemetry Java GitHub repository](https://github.com/open-telemetry/opentelemetry-java-instrumentation).
379
+
- Learn more features for Spring Boot native image applications in [OpenTelemetry SpringBoot starter](https://opentelemetry.io/docs/zero-code/java/spring-boot-starter/.)
380
+
- Learn more features for Quarkus native applications in [Quarkus OpenTelemetry Exporter for Azure](https://quarkus.io/guides/opentelemetry).
381
+
- Review the [release notes](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/spring/spring-cloud-azure-starter-monitor/CHANGELOG.md) on GitHub.
350
382
351
383
### [Node.js](#tab/nodejs)
352
384
@@ -359,18 +391,18 @@ Azure Monitor OpenTelemetry sample applications are available for all supported
359
391
360
392
### [Python](#tab/python)
361
393
362
-
-For details on adding and modifying Azure Monitor OpenTelemetry, see [Add and modify Azure Monitor OpenTelemetry](opentelemetry-add-modify.md).
363
-
-To review the source code and extra documentation, see the [Azure Monitor Distro GitHub repository](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-opentelemetry/README.md).
364
-
-To see extra samples and use cases, see[Azure Monitor Distro samples](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/monitor/azure-monitor-opentelemetry/samples).
365
-
-See the [changelog](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-opentelemetry/CHANGELOG.md) on GitHub.
366
-
-To install the PyPI package, check for updates, or view release notes, see the [Azure Monitor Distro PyPI Package](https://pypi.org/project/azure-monitor-opentelemetry/) page.
367
-
-To become more familiar with Azure Monitor Application Insights and OpenTelemetry, see the [Azure Monitor Example Application](https://github.com/Azure-Samples/azure-monitor-opentelemetry-python).
368
-
-To learn more about OpenTelemetry and its community, see the [OpenTelemetry Python GitHub repository](https://github.com/open-telemetry/opentelemetry-python).
369
-
-To see available OpenTelemetry instrumentations and components, see the [OpenTelemetry Contributor Python GitHub repository](https://github.com/open-telemetry/opentelemetry-python-contrib).
370
-
-To enable usage experiences, [enable web or browser user monitoring](javascript.md).
394
+
-See [Add and modify Azure Monitor OpenTelemetry](opentelemetry-add-modify.md) for details on adding and modifying Azure Monitor OpenTelemetry.
395
+
-Review the source code and extra documentation in the [Azure Monitor Distro GitHub repository](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-opentelemetry/README.md).
396
+
-See extra samples and use cases in[Azure Monitor Distro samples](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/monitor/azure-monitor-opentelemetry/samples).
397
+
-Review the [changelog](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-opentelemetry/CHANGELOG.md) on GitHub.
398
+
-Install the PyPI package, check for updates, or view release notes on the [Azure Monitor Distro PyPI Package](https://pypi.org/project/azure-monitor-opentelemetry/) page.
399
+
-Become more familiar with Azure Monitor Application Insights and OpenTelemetry in the [Azure Monitor Example Application](https://github.com/Azure-Samples/azure-monitor-opentelemetry-python).
400
+
-Learn more about OpenTelemetry and its community in the [OpenTelemetry Python GitHub repository](https://github.com/open-telemetry/opentelemetry-python).
401
+
-See available OpenTelemetry instrumentations and components in the [OpenTelemetry Contributor Python GitHub repository](https://github.com/open-telemetry/opentelemetry-python-contrib).
402
+
-Enable usage experiences by [enabling web or browser user monitoring](javascript.md).
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/enable-permissions-management.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ author: Elazark
4
4
ms.author: elkrieger
5
5
description: Learn how to enable Permissions Management for better access control and security in your cloud infrastructure.
6
6
ms.topic: how-to
7
-
ms.date: 05/07/2024
7
+
ms.date: 06/09/2024
8
8
#customer intent: As a cloud administrator, I want to learn how to enable permissions (CIEM) in order to effectively manage user access and entitlements in my cloud infrastructure.
9
9
---
10
10
@@ -54,7 +54,7 @@ List of Azure recommendations:
54
54
55
55
- Azure over-provisioned identities should have only the necessary permissions
56
56
57
-
-Unused identities in your Azure environment should be revoked/removed
57
+
-Permissions of inactive identities in your Azure subscription should be revoked
58
58
59
59
- Super identities in your Azure environment should be revoked/removed
60
60
@@ -99,7 +99,7 @@ List of AWS recommendations:
99
99
100
100
- AWS over-provisioned identities should have only the necessary permissions
101
101
102
-
-Unused identities in your Azure environment should be revoked/removed
102
+
-Permissions of inactive identities in your Azure subscription should be revoked
103
103
104
104
## Enable Permissions Management (CIEM) for GCP
105
105
@@ -145,10 +145,11 @@ List of GCP recommendations:
145
145
146
146
- GCP over-provisioned identities should have only necessary permissions
147
147
148
-
-Unused identities in your GCP environment should be revoked/removed
148
+
-Permissions of inactive identities in your GCP project should be revoked
149
149
150
150
- Super identities in your GCP environment should be revoked/removed
151
151
152
152
## Next step
153
153
154
-
Learn more about [Microsoft Entra Permissions Management](/entra/permissions-management/).
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/recommendations-reference-aws.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Reference table for all security recommendations for AWS resources
3
3
description: This article lists all Microsoft Defender for Cloud security recommendations that help you harden and protect your Amazon Web Services (AWS) resources.
4
4
ms.topic: reference
5
-
ms.date: 03/13/2024
5
+
ms.date: 06/09/2024
6
6
ms.custom: generated
7
7
ai-usage: ai-assisted
8
8
---
@@ -1147,9 +1147,9 @@ Secrets Manager can rotate secrets. You can use rotation to replace long-term se
1147
1147
1148
1148
**Severity**: Medium
1149
1149
1150
-
### [Unused identities in your AWS environment should be removed](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/71016e8c-d079-479d-942b-9c95b463e4a6)
1150
+
### [Permissions of inactive identities in your AWS account should be revoked](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/71016e8c-d079-479d-942b-9c95b463e4a6)
1151
1151
1152
-
**Description**: Inactive identities are human and non-human entities that haven't performed any action on any resource in the last 90 days. Inactive IAM identities with high-risk permissions in your AWS account can be prone to attack if left as is and leave organizations open to credential misuse or exploitation. Proactively detecting and responding to unused identities helps you prevent unauthorized entities from gaining access to your AWS resources.
1152
+
**Description**: Microsoft Defender for Cloud discovered an identity that has not performed any action on any resource within your AWS account in the past 45 days. It is recommended to revoke permissions of inactive identities, in order to reduce the attack surface of your cloud environment.
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/recommendations-reference-gcp.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Reference table for all security recommendations for GCP resources
3
3
description: This article lists all Microsoft Defender for Cloud security recommendations that help you harden and protect your Google Cloud Platform (GCP) resources.
4
4
ms.topic: reference
5
-
ms.date: 03/13/2024
5
+
ms.date: 06/09/2024
6
6
ms.custom: generated
7
7
ai-usage: ai-assisted
8
8
---
@@ -983,9 +983,9 @@ GCP facilitates up to 10 external service account keys per service account to fa
983
983
984
984
**Severity**: High
985
985
986
-
### [Unused identities in your GCP environment should be removed](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/257e9506-fd47-4123-a8ef-92017f845906)
986
+
### [Permissions of inactive identities in your GCP project should be revoked](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/257e9506-fd47-4123-a8ef-92017f845906)
987
987
988
-
**Description**: It's imperative to identify unused identities as they pose significant security risks. These identities often involve bad practices, such as excessive permissions and mismanaged keys that leave organizations open to credential misuse or exploitation and increases your resource`s attack surface. Inactive identities are human and nonhuman entities that haven't performed any action on any resource in the last 90 days. Service account keys can become a security risk if not managed carefully.
988
+
**Description**: Microsoft Defender for Cloud discovered an identity that has not performed any action on any resource within your GCP project in the past 45 days. It is recommended to revoke permissions of inactive identities, in order to reduce the attack surface of your cloud environment.
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/recommendations-reference.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1841,9 +1841,9 @@ Learn more in [Introduction to Microsoft Defender for Key Vault](defender-for-ke
1841
1841
1842
1842
**Severity**: Medium
1843
1843
1844
-
### [Unused identities in your Azure environment should be removed (Preview)](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/7af29efb-41cc-47b6-81b8-800a0888f9a2)
1844
+
### [Permissions of inactive identities in your Azure subscription should be revoked](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/7af29efb-41cc-47b6-81b8-800a0888f9a2)
1845
1845
1846
-
**Description**: Inactive Identities are the identities that have not performed any action on any infrastructure resources in the last 90 days. Inactive identities pose a significant risk to your organization as they could be used by attackers to gain access and execute tasks in your environment.
1846
+
**Description**: Microsoft Defender for Cloud discovered an identity that has not performed any action on any resource within your Azure subscription in the past 45 days. It is recommended to revoke permissions of inactive identities, in order to reduce the attack surface of your cloud environment.
Copy file name to clipboardExpand all lines: articles/sentinel/entities-reference.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,22 +4,24 @@ description: This article displays the Microsoft Sentinel entity types and their
4
4
author: yelevin
5
5
ms.author: yelevin
6
6
ms.topic: reference
7
-
ms.date: 10/15/2023
7
+
ms.date: 06/09/2024
8
8
---
9
9
10
10
# Microsoft Sentinel entity types reference
11
11
12
-
This document contains two sets of information regarding entities and entity types in Microsoft Sentinel.
13
-
- The [**Entity types and identifiers**](#entity-types-and-identifiers) table shows the different types of entities that can be used in [entity mapping](map-data-fields-to-entities.md) in both [analytics rules](detect-threats-custom.md) and [hunting](hunting.md). The table also shows, for each entity type, the different identifiers that can be used to identify an entity.
14
-
- The [**Entity schema**](#entity-type-schemas) section shows the data structure and schema for entities in general and for each entity type in particular, including some types that are not represented in the entity mapping feature.
12
+
This document contains two sets of information regarding entities and entity types in Microsoft Sentinel and the [Microsoft unified security operations platform](microsoft-sentinel-defender-portal.md).
13
+
- The [**Entity types and identifiers**](#entity-types-and-identifiers) table shows the different types of [entities](entities.md) that can be identified in alerts and incidents, allowing you to [track and investigate them](entity-pages.md). The table also shows, for each entity type, the different identifiers that can be used to identify an entity.
14
+
- The [**Entity schema**](#entity-type-schemas) section shows the data structure and schema for entities in general and for each entity type in particular.
The following table shows the **entity types**currently available for mapping in Microsoft Sentinel, and the **attributes**available as **identifiers** for each entity type. Nearly all of these attributes appear in the **Identifiers** drop-down list in the [entity mapping](map-data-fields-to-entities.md) section of the [analytics rule wizard](detect-threats-custom.md) (see footnotes for exceptions).
20
+
The following table shows the **entity types**that can be recognized by Microsoft Sentinel, and the **attributes**that can be used as **identifiers** for each entity type.
19
21
20
-
You can use up to three identifiers for a single entity mapping. **Strong identifiers** alone are sufficient to uniquely identify an entity, whereas **weak identifiers** can do so only in combination with other identifiers.
22
+
Microsoft Sentinel recognizes entities in alerts and incidents that are created by [entity mapping](map-data-fields-to-entities.md) in [analytics rules](threat-detection.md). It also recognizes entities already identified in alerts ingested from other sources.
21
23
22
-
Learn more about [strong and weak identifiers](entities.md#strong-and-weak-identifiers).
24
+
You can currently use up to three identifiers for a given entity when creating an entity mapping in Microsoft Sentinel. **Strong identifiers** alone are sufficient to uniquely identify an entity, whereas **weak identifiers** can do so only in combination with other identifiers. Learn more about [strong and weak identifiers](entities.md#strong-and-weak-identifiers). Most but not all identifiers in this table can be used when creating entity mappings in Microsoft Sentinel (see footnotes).
0 commit comments