Skip to content

Commit 50e62e0

Browse files
committed
What's New archival 1/5
1 parent 93ea3bb commit 50e62e0

File tree

2 files changed

+80
-80
lines changed

2 files changed

+80
-80
lines changed

articles/sentinel/whats-new-archive.md

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,86 @@ Noted features are currently in PREVIEW. The [Azure Preview Supplemental Terms](
2525
> You can also contribute! Join us in the [Azure Sentinel Threat Hunters GitHub community](https://github.com/Azure/Azure-Sentinel/wiki).
2626
2727

28+
## August 2021
29+
30+
- [Advanced incident search (Public preview)](#advanced-incident-search-public-preview)
31+
- [Fusion detection for Ransomware (Public preview)](#fusion-detection-for-ransomware-public-preview)
32+
- [Watchlist templates for UEBA data](#watchlist-templates-for-ueba-data-public-preview)
33+
- [File event normalization schema (Public preview)](#file-event-normalization-schema-public-preview)
34+
- [New in docs: Best practice guidance](#new-in-docs-best-practice-guidance)
35+
36+
### Advanced incident search (Public preview)
37+
38+
By default, incident searches run across the **Incident ID**, **Title**, **Tags**, **Owner**, and **Product name** values only. Azure Sentinel now provides [advanced search options](investigate-cases.md#search-for-incidents) to search across more data, including alert details, descriptions, entities, tactics, and more.
39+
40+
For example:
41+
42+
:::image type="content" source="media/investigate-cases/advanced-search.png" alt-text="Screenshot of the Incidents page advanced search options.":::
43+
44+
For more information, see [Search for incidents](investigate-cases.md#search-for-incidents).
45+
46+
### Fusion detection for Ransomware (Public preview)
47+
48+
Azure Sentinel now provides new Fusion detections for possible Ransomware activities, generating incidents titled as **Multiple alerts possibly related to Ransomware activity detected**.
49+
50+
Incidents are generated for alerts that are possibly associated with Ransomware activities, when they occur during a specific time-frame, and are associated with the Execution and Defense Evasion stages of an attack. You can use the alerts listed in the incident to analyze the techniques possibly used by attackers to compromise a host / device and to evade detection.
51+
52+
Supported data connectors include:
53+
54+
- [Azure Defender (Azure Security Center)](connect-defender-for-cloud.md)
55+
- [Microsoft Defender for Endpoint](./data-connectors-reference.md#microsoft-defender-for-endpoint)
56+
- [Microsoft Defender for Identity](./data-connectors-reference.md#microsoft-defender-for-identity)
57+
- [Microsoft Cloud App Security](./data-connectors-reference.md#microsoft-defender-for-cloud-apps)
58+
- [Azure Sentinel scheduled analytics rules](detect-threats-built-in.md#scheduled)
59+
60+
For more information, see [Multiple alerts possibly related to Ransomware activity detected](fusion.md#fusion-for-ransomware).
61+
62+
### Watchlist templates for UEBA data (Public preview)
63+
64+
Azure Sentinel now provides built-in watchlist templates for UEBA data, which you can customize for your environment and use during investigations.
65+
66+
After UEBA watchlists are populated with data, you can correlate that data with analytics rules, view it in the entity pages and investigation graphs as insights, create custom uses such as to track VIP or sensitive users, and more.
67+
68+
Watchlist templates currently include:
69+
70+
- **VIP Users**. A list of user accounts of employees that have high impact value in the organization.
71+
- **Terminated Employees**. A list of user accounts of employees that have been, or are about to be, terminated.
72+
- **Service Accounts**. A list of service accounts and their owners.
73+
- **Identity Correlation**. A list of related user accounts that belong to the same person.
74+
- **High Value Assets**. A list of devices, resources, or other assets that have critical value in the organization.
75+
- **Network Mapping**. A list of IP subnets and their respective organizational contexts.
76+
77+
For more information, see [Create watchlists in Microsoft Sentinel](watchlists-create.md) and [Built-in watchlist schemas](watchlist-schemas.md).
78+
79+
80+
81+
### File Event normalization schema (Public preview)
82+
83+
The Azure Sentinel Information Model (ASIM) now supports a File Event normalization schema, which is used to describe file activity, such as creating, modifying, or deleting files or documents. File events are reported by operating systems, file storage systems such as Azure Files, and document management systems such as Microsoft SharePoint.
84+
85+
For more information, see:
86+
87+
- [Azure Sentinel File Event normalization schema reference (Public preview)](file-event-normalization-schema.md)
88+
- [Normalization and the Azure Sentinel Information Model (ASIM)](normalization.md)
89+
90+
91+
### New in docs: Best practice guidance
92+
93+
In response to multiple requests from customers and our support teams, we added a series of best practice guidance to our documentation.
94+
95+
For more information, see:
96+
97+
- [Prerequisites for deploying Azure Sentinel](prerequisites.md)
98+
- [Best practices for Azure Sentinel](best-practices.md)
99+
- [Azure Sentinel workspace architecture best practices](best-practices-workspace-architecture.md)
100+
- [Design your Azure Sentinel workspace architecture](design-your-workspace-architecture.md)
101+
- [Azure Sentinel sample workspace designs](sample-workspace-designs.md)
102+
- [Data collection best practices](best-practices-data.md)
103+
104+
> [!TIP]
105+
> You can find more guidance added across our documentation in relevant conceptual and how-to articles. For more information, see [Best practice references](best-practices.md#best-practice-references).
106+
>
107+
28108
## July 2021
29109

30110
- [Microsoft Threat Intelligence Matching Analytics (Public preview)](#microsoft-threat-intelligence-matching-analytics-public-preview)

articles/sentinel/whats-new.md

Lines changed: 0 additions & 80 deletions
Original file line numberDiff line numberDiff line change
@@ -754,86 +754,6 @@ You'll only see the storage types that you actually have defined resources for.
754754

755755
:::image type="content" source="media/whats-new/storage-diagnostics.png" alt-text="Screenshot of Azure Storage diagnostics configuration.":::
756756

757-
## August 2021
758-
759-
- [Advanced incident search (Public preview)](#advanced-incident-search-public-preview)
760-
- [Fusion detection for Ransomware (Public preview)](#fusion-detection-for-ransomware-public-preview)
761-
- [Watchlist templates for UEBA data](#watchlist-templates-for-ueba-data-public-preview)
762-
- [File event normalization schema (Public preview)](#file-event-normalization-schema-public-preview)
763-
- [New in docs: Best practice guidance](#new-in-docs-best-practice-guidance)
764-
765-
### Advanced incident search (Public preview)
766-
767-
By default, incident searches run across the **Incident ID**, **Title**, **Tags**, **Owner**, and **Product name** values only. Azure Sentinel now provides [advanced search options](investigate-cases.md#search-for-incidents) to search across more data, including alert details, descriptions, entities, tactics, and more.
768-
769-
For example:
770-
771-
:::image type="content" source="media/investigate-cases/advanced-search.png" alt-text="Screenshot of the Incidents page advanced search options.":::
772-
773-
For more information, see [Search for incidents](investigate-cases.md#search-for-incidents).
774-
775-
### Fusion detection for Ransomware (Public preview)
776-
777-
Azure Sentinel now provides new Fusion detections for possible Ransomware activities, generating incidents titled as **Multiple alerts possibly related to Ransomware activity detected**.
778-
779-
Incidents are generated for alerts that are possibly associated with Ransomware activities, when they occur during a specific time-frame, and are associated with the Execution and Defense Evasion stages of an attack. You can use the alerts listed in the incident to analyze the techniques possibly used by attackers to compromise a host / device and to evade detection.
780-
781-
Supported data connectors include:
782-
783-
- [Azure Defender (Azure Security Center)](connect-defender-for-cloud.md)
784-
- [Microsoft Defender for Endpoint](./data-connectors-reference.md#microsoft-defender-for-endpoint)
785-
- [Microsoft Defender for Identity](./data-connectors-reference.md#microsoft-defender-for-identity)
786-
- [Microsoft Cloud App Security](./data-connectors-reference.md#microsoft-defender-for-cloud-apps)
787-
- [Azure Sentinel scheduled analytics rules](detect-threats-built-in.md#scheduled)
788-
789-
For more information, see [Multiple alerts possibly related to Ransomware activity detected](fusion.md#fusion-for-ransomware).
790-
791-
### Watchlist templates for UEBA data (Public preview)
792-
793-
Azure Sentinel now provides built-in watchlist templates for UEBA data, which you can customize for your environment and use during investigations.
794-
795-
After UEBA watchlists are populated with data, you can correlate that data with analytics rules, view it in the entity pages and investigation graphs as insights, create custom uses such as to track VIP or sensitive users, and more.
796-
797-
Watchlist templates currently include:
798-
799-
- **VIP Users**. A list of user accounts of employees that have high impact value in the organization.
800-
- **Terminated Employees**. A list of user accounts of employees that have been, or are about to be, terminated.
801-
- **Service Accounts**. A list of service accounts and their owners.
802-
- **Identity Correlation**. A list of related user accounts that belong to the same person.
803-
- **High Value Assets**. A list of devices, resources, or other assets that have critical value in the organization.
804-
- **Network Mapping**. A list of IP subnets and their respective organizational contexts.
805-
806-
For more information, see [Create watchlists in Microsoft Sentinel](watchlists-create.md) and [Built-in watchlist schemas](watchlist-schemas.md).
807-
808-
809-
810-
### File Event normalization schema (Public preview)
811-
812-
The Azure Sentinel Information Model (ASIM) now supports a File Event normalization schema, which is used to describe file activity, such as creating, modifying, or deleting files or documents. File events are reported by operating systems, file storage systems such as Azure Files, and document management systems such as Microsoft SharePoint.
813-
814-
For more information, see:
815-
816-
- [Azure Sentinel File Event normalization schema reference (Public preview)](file-event-normalization-schema.md)
817-
- [Normalization and the Azure Sentinel Information Model (ASIM)](normalization.md)
818-
819-
820-
### New in docs: Best practice guidance
821-
822-
In response to multiple requests from customers and our support teams, we added a series of best practice guidance to our documentation.
823-
824-
For more information, see:
825-
826-
- [Prerequisites for deploying Azure Sentinel](prerequisites.md)
827-
- [Best practices for Azure Sentinel](best-practices.md)
828-
- [Azure Sentinel workspace architecture best practices](best-practices-workspace-architecture.md)
829-
- [Design your Azure Sentinel workspace architecture](design-your-workspace-architecture.md)
830-
- [Azure Sentinel sample workspace designs](sample-workspace-designs.md)
831-
- [Data collection best practices](best-practices-data.md)
832-
833-
> [!TIP]
834-
> You can find more guidance added across our documentation in relevant conceptual and how-to articles. For more information, see [Best practice references](best-practices.md#best-practice-references).
835-
>
836-
837757
## Next steps
838758

839759
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)