Skip to content

Commit b6c43d2

Browse files
committed
Incorp PG feedback
1 parent 37879a7 commit b6c43d2

File tree

3 files changed

+23
-45
lines changed

3 files changed

+23
-45
lines changed

articles/sentinel/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@
8787
href: sentinel-solutions.md
8888
- name: Content hub catalog
8989
href: sentinel-solutions-catalog.md
90-
- name: Essential solutions for domain categories
91-
href: essential-solutions.md
90+
- name: ASIM-based domain solutions
91+
href: domain-based-essential-solutions.md
9292
- name: Manage custom content with repositories
9393
href: ci-cd-custom-content.md
9494
- name: OOTB content centralization changes
Lines changed: 20 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Microsoft essential solutions for Microsoft Sentinel
2+
title: ASIM-based domain solutions - Essentials for Microsoft Sentinel
33
description: Learn about the Microsoft essential solutions for Microsoft Sentinel that span across different ASIM schemas like networks, DNS, and web sessions.
44
author: cwatson-cat
55
ms.topic: conceptual
@@ -8,26 +8,25 @@ ms.author: cwatson
88
#Customer intent: As a security engineer, I want to minimize the amount of solution content I have to deploy and manage by using Microsoft essential solutions for Microsoft Sentinel.
99
---
1010

11-
# Microsoft essential solutions for Microsoft Sentinel
11+
# Microsoft essential solutions - Advanced Security Information Model (ASIM) based domain solutions for Microsoft Sentinel
1212

13-
Microsoft essential solutions are a collection of solutions that....provide centralized content for specific domain categories...? Essential solutions use the normalization technique Advanced Security Information Model (ASIM) to normalize the data at query time or ingestion time. The ingestion time normalization results can be ingested into following normalized table:
13+
Microsoft essential solutions helps you reduce the amount of content you manage in Microsoft Sentinel for specific domains like Security - Network. Essential solutions use the normalization technique Advanced Security Information Model (ASIM) to normalize the data at query time or ingestion time.
1414

15-
- [ASimDnsActivityLogs](/azure/azure-monitor/reference/tables/asimdnsactivitylogs) for the DNS schema.
16-
- [ASimNetworkSessionLogs](/azure/azure-monitor/reference/tables/asimnetworksessionlogs) for the Network Session schema
15+
## Why use ASIM-based Microsoft essential solutions
1716

18-
For more information, see [Ingest time normalization](/azure/sentinel/normalization-ingest-time).
17+
When multiple solutions in a domain category share similar detection patterns, it makes sense to have the data captured under a normalized schema like ASIM. Essential solutions makes use of this ASIM schema to detect threats at scale.
1918

20-
## Why Microsoft essential solutions
19+
- A normalized schema makes it easier for you to query incident details. You don't have to remember different vendor syntax for similar log attributes.
20+
- If you don't have to manage content for multiple solutions, it makes use case deployment and incident handling much easier.
21+
- A consolidated workbook view gives you better environment visibility and possible query time parsing with high performing ASIM parsers.
2122

22-
Today, we have over 280 product solutions in the content hub. There are multiple product solutions for different domain categories like Security - Network. For example, Azure Firewall, Palo Alto Firewall, and Corelight have product solutions for the Security-Network domain category.
23+
In the content hub, there are multiple product solutions for different domain categories like Security - Network. For example, Azure Firewall, Palo Alto Firewall, and Corelight have product solutions for the Security -Network domain category.
2324

2425
- These solutions have differing data ingest components by design. But there’s a certain pattern to the analytics, hunting, workbooks, and other content within the same domain category.
2526
- Most of the major network products have a common basic set of firewall alerts that includes malicious threats coming from unusual IP addresses. The analytic rule template is, in general, duplicated for each of the Security - Network category of product solutions. If you're running multiple network products, you need to check and configure multiple analytic rules individually, which is inefficient. You'd also get alerts for each rule configured and might end up with alert fatigue.
2627

2728
If you have duplicative hunting queries, you might have less performant hunting experiences with the run-all mode of hunting. These duplicative hunting queries also introduce inefficiencies for threat hunters to select-run similar queries.
2829

29-
Microsoft essential solution reduces the amount of content you need to manage or provides efficiencies in....
30-
3130
## ASIM schemas supported
3231

3332
The essentials solutions are currently spanned across the following different ASIM schemas that Sentinel supports:
@@ -42,44 +41,23 @@ The essentials solutions are currently spanned across the following different AS
4241

4342
For more information, see [Advanced Security Information Model (ASIM) schemas](/azure/sentinel/normalization-about-schemas).
4443

45-
## Connectors not included
46-
47-
The essential solutions don't have a connector of their own. They depend on the source specific connectors to pull in the logs. Then the solutions use the ASIM parsers in their built in analytic rules, hunting queries, and workbooks to identify anomalies. The ASIM parsers provide a consolidated report or dashboard view for all the source specific solutions that were part of prerequisite lists.
48-
49-
## Network session essentials solution
50-
51-
One of the first solutions available in the essentials series is the network session essential solution. This solution doesn't have a connector of its own. Instead, it uses the ASIM parsers for query time parsing. This solution comes with seven analytic rules, four hunting queries, one playbook, one workbook, and watchlists.
44+
## Ingestion time normalization
5245

53-
Analytics rules included:
46+
The ingestion time normalization results can be ingested into following normalized table:
5447

55-
- Network session traffic anomaly
56-
- Anomaly in port usage
57-
- More than defined port usage
58-
- Excessive number of failed connections from a Single source
59-
- Detect possible flooding
60-
- Possible external to internal port sweep
61-
- Possible port scan
62-
- Potential Beaconing activity
63-
- TI map IP entity to Network Session Events
48+
- [ASimDnsActivityLogs](/azure/azure-monitor/reference/tables/asimdnsactivitylogs) for the DNS schema.
49+
- [ASimNetworkSessionLogs](/azure/azure-monitor/reference/tables/asimnetworksessionlogs) for the Network Session schema
6450

65-
Hunting queries included:
51+
For more information, see [Ingest time normalization](/azure/sentinel/normalization-ingest-time).
6652

67-
- Detect Anomaly in port usage
68-
- Detect More than defined port usage
69-
- Detect multiple users with same MAC address
70-
- Destination App and associated standard port mismatch
53+
## Connectors not included
7154

72-
Playbook: Summarization playbook
55+
The essential solutions don't have a connector of their own. They depend on the source specific connectors to pull in the logs. Then the solutions use the ASIM parsers in their built in analytic rules, hunting queries, and workbooks to identify anomalies. The ASIM parsers provide a consolidated report or dashboard view for all the source specific solutions that were part of prerequisite lists.
7356

74-
- The playbook summarizes end point security events and stores them in a pre-defined table.
75-
- This playbook is helpful where you have a high number of end points security events. For example, you might have a high number of events in a large organization where network traffic is being monitoring by multiple source specific network solutions.
57+
## Network session essentials solution
7658

77-
- By default, this playbook is available as a template. If you have a high number of end point security events on your network and you notice a performance issue when loading the workbook, then enable the playbook template.
59+
One of the first solutions available in the essentials series is the network session essential solution. This solution doesn't have a connector of its own. Instead, it uses the ASIM parsers for query time parsing. For more information about this solution, see (Marketplace listing)
7860

79-
Workbook:
80-
The workbook covers details for the following listed events.
61+
## Next steps
8162

82-
- Traffic visibility
83-
- Security visibility
84-
- Policy rule
85-
- Network security event viewer
63+
- [Using the Advanced Security Information Model (ASIM)](/azure/sentinel/normalization-about-parsers)

articles/sentinel/sentinel-solutions-catalog.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ When you deploy a solution, the security content included with the solution, suc
3030
| **[Microsoft Defender for IoT](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-unifiedmicrosoftsocforot?tab=Overview)** | [Analytics rules, playbooks, workbook](iot-advanced-threat-monitoring.md) | Internet of Things (IoT), Security - Threat Protection | Microsoft |
3131
|**[Maturity Model for Event Log Management M2131](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-maturitymodelforeventlogma?tab=Overview)** | [Analytics rules, hunting queries, playbooks, workbook](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/modernize-log-management-with-the-maturity-model-for-event-log/ba-p/3072842) | Compliance | Microsoft|
3232
|**[Microsoft 365 Insider Risk Management](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-insiderriskmanagement?tab=Overview)** (IRM) |[Data connector](data-connectors/microsoft-365-insider-risk-management.md), [workbook, analytics rules, hunting queries, playbook](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/announcing-the-microsoft-sentinel-microsoft-insider-risk/ba-p/2955786) |Security - Insider threat | Microsoft|
33-
|**Network Session Essential Solutions**|[Analytics rules, hunting queries, playbooks, workbook](essential-solutions.md)|Security - Network | Microsoft|
33+
|**Network Session Essential Solution**|[Analytics rules, hunting queries, playbooks, workbook](essential-solutions.md)|Security - Network | Microsoft|
3434
|**[NIST SP 800-53](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-nistsp80053?tab=Overview)**|[Workbooks, analytic rules, playbooks](https://techcommunity.microsoft.com/t5/public-sector-blog/microsoft-sentinel-nist-sp-800-53-solution/ba-p/3401307)|Security - Threat Protection|Microsoft|
3535
|**[Security Threat Essentials](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-securitythreatessentialsol?tab=Overview)**|Analytic rules, Hunting queries|Security - Others|Microsoft|
3636
|**[Zero Trust (TIC 3.0)](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-zerotrust?tab=Overview)** |[Analytics rules, playbook, workbooks](/security/zero-trust/integrate/sentinel-solution) |Compliance, Identity, Security - Others |Microsoft |

0 commit comments

Comments
 (0)