mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-28 13:17:23 +00:00
add changes from t.a.
This commit is contained in:
parent
cb932080a2
commit
6e63904025
@ -27,7 +27,7 @@ ms.date: 04/16/2018
|
||||
|
||||
>Want to experience Windows Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-bestpractices-abovefoldlink)
|
||||
|
||||
## Advanced hunting query best practices
|
||||
## Performance best practices
|
||||
The following best practices serve as a guideline of query performance best practices and for you to get faster results and be able to run complex queries.
|
||||
- Use time filters first. Azure Kusto is highly optimized to utilize time filters. For more information, see [Azure Kusto](https://docs.microsoft.com/connectors/kusto/).
|
||||
- Put filters that are expected to remove most of the data in the beginning of the query, following the time filter.
|
||||
@ -36,7 +36,27 @@ The following best practices serve as a guideline of query performance best prac
|
||||
- When joining between two tables - choose the table with less rows to be the first one (left-most).
|
||||
- When joining between two tables - project only needed columns from both sides of the join.
|
||||
|
||||
|
||||
## Query tips and pitfalls
|
||||
|
||||
### Unique Process IDs
|
||||
Process IDs are recycled in Windows and reused for new processes, so cannot serve as unique IDs for a specific process.
|
||||
To address this issue, the time the process was created for the Windows Defender ATP data. Together with the process ID, this can serve as a unique ID on a specific machine.
|
||||
|
||||
So, when you join data based on a specific process or summarize data for each process, you'll need to use a machine identifier (either MachineId or ComputerName), a process ID (ProcessId or InitiatingProcessId) and the process creation time (ProcessCreationTime or InitiatingProcessCreationTime)
|
||||
|
||||
The following example query is created to find processes that access more than 10 IP addresses over port 445 (SMB) - possibly scanning for file shares.
|
||||
|
||||
Example query:
|
||||
```
|
||||
NetworkCommunicationEvents
|
||||
| where RemotePort == 445 and EventTime > ago(12h) and InitiatingProcessId !in (0, 4)
|
||||
| summarize RemoteIPCount=dcount(RemoteIP) by ComputerName, InitiatingProcessId, InitiatingProcessCreationTime, InitiatingProcessFileName
|
||||
| where RemoteIPCount > 10
|
||||
```
|
||||
|
||||
The query summarizes by both InitiatingProcessId and InitiatingProcessCreationTime - to make sure the query looks at a single process, and not mixing multiple processes with the same process ID.
|
||||
|
||||
|
||||
|
||||
>Want to experience Windows Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-bestpractices-belowfoldlink)
|
||||
|
||||
|
@ -125,17 +125,17 @@ These steps guide you on modifying and overwriting an existing query.
|
||||
|
||||
2. Select **Delete** and confirm that you want to delete the query.
|
||||
|
||||
## Results set capabilities in advanced hunting
|
||||
## Result set capabilities in advanced hunting
|
||||
|
||||
The results set has several capabilities to provide you with effective investigation, including:
|
||||
The result set has several capabilities to provide you with effective investigation, including:
|
||||
|
||||
- Columns that return entity-related objects, such as Machine name, Machine ID, File name, SHA1, User, IP, and URL, are linked to their entity pages in the Windows Defender ATP portal.
|
||||
- You can right-click on a cell in the results set and add a filter to your written query. The current filtering options are **include**, **exclude** or **advanced filter**, which provides additional filtering options on the cell value. These cell values are part of the row set.
|
||||
- You can right-click on a cell in the result set and add a filter to your written query. The current filtering options are **include**, **exclude** or **advanced filter**, which provides additional filtering options on the cell value. These cell values are part of the row set.
|
||||
|
||||

|
||||

|
||||
|
||||
## Filter results in advanced hunting
|
||||
In advanced hunting, you can use the advanced filter on the output results set of the query.
|
||||
In advanced hunting, you can use the advanced filter on the output result set of the query.
|
||||
The filters provide an overview of the result set where
|
||||
each column has it's own section and shows the distinct values that appear in the column and their prevalence.
|
||||
|
||||
|
@ -40,7 +40,7 @@ Alerts are the starting point for automated investigations. Typically, they are
|
||||
|
||||
When an alert that contains a supported entity is seen, the automated investigation then proceeds and analyzes each entity within the alert. It determines whether an entity can be incriminated or exonerated. The outcome and details from the analysis is seen in the Automated investigation view.
|
||||
|
||||
### Details of an investigation
|
||||
### Details of an automated investigation
|
||||
As the investigation proceeds, you'll be able to view the details of the investigation. Selecting a triggering alert brings you to the investigation details view where you can pivot from the **Investigation graph**, **Alerts**, **Machines**, **Threats**, **Entities**, and **Log** tabs.
|
||||
|
||||
In the **Alerts** tab, you'll see the alert that started the investigation.
|
||||
|
Loading…
x
Reference in New Issue
Block a user