Path: blob/master/Guided Investigation - Incident Triage.ipynb
3249 views
Guided Triage - Incidents
Data Sources Used:
Microsoft Sentinel
Incidents
Threat Intelligence Providers
VirusTotal (https://www.virustotal.com/)
XForce (https://www.ibm.com/security/xforce)
GreyNoise (https://www.greynoise.io)
This notebooks takes you through a guided triage of an Microsoft Sentinel Incident. The triage focuses on investigating the entities that attached to an Microsoft Sentinel Incident. This notebook can be extended with additional triage steps based on specific processes and workflows.
Notebook initialization
The next cell:
Checks for the correct Python version
Checks versions and optionally installs required packages
Imports the required packages into the notebook
Sets a number of configuration options.
More details...
This should complete without errors. If you encounter errors or warnings look at the following two notebooks:
If you are running in the Microsoft Sentinel Notebooks environment (Azure Notebooks or Azure ML) you can run live versions of these notebooks:
You may also need to do some additional configuration to successfully use functions such as Threat Intelligence service lookup and Geo IP lookup. There are more details about this in the ConfiguringNotebookEnvironment notebook and in these documents:
Authenticate to Microsoft Sentinel APIs and Select Subscriptions
This cell connects to the Microsoft Sentinel APIs and gets a list of subscriptions the user has access to for them to select. In order to use this the user must have at least read permissions on the Microsoft Sentinel workspace. In the drop down select the name of the subscription that contains the Microsoft Sentinel workspace you want to triage incidents from.
Now select the name of the Microsoft Sentinel workspace in the subscription you want to triage incidents from.
Authenticate to Microsoft Sentinel, TI providers and load Notebooklets
Note: you may occasionally see a JavaScript error displayed at the end of the authentication - you can safely ignore this.
On successful authentication you should see a popup schema button. To find your Workspace Id go to Log Analytics. Look at the workspace properties to find the ID.
Note that you may see a warning relating to the IPStack service when running this cell. This can be safely ignored as its not used in this case.
Authentication and Configuration Problems
Click for details about configuring your authentication parameters
The notebook is expecting your Microsoft Sentinel Tenant ID and Workspace ID to be configured in one of the following places:
config.jsonin the current foldermsticpyconfig.yamlin the current folder or location specified byMSTICPYCONFIGenvironment variable.
For help with setting up your config.json file (if this hasn't been done automatically) see the ConfiguringNotebookEnvironment notebook in the root folder of your Microsoft-Sentinel-Notebooks project. This shows you how to obtain your Workspace and Subscription IDs from the Microsoft Sentinel Portal. You can use the SubscriptionID to find your Tenant ID). To view the current config.json run the following in a code cell.
%pfile config.json
For help with setting up your msticpyconfig.yaml see the Setup section at the end of this notebook and the ConfigureNotebookEnvironment notebook
Import and initialize notebooklets
This imports the msticnb package and the notebooklets classes.
These are needed for the notebook operations
Incident Timeline
This timeline shows you all events in the selected workspace, grouped by the severity of the incident.
Select Incident to Triage
From the table below select the incident you wish to triage.
The cell below shows you key details relating to the incident, including the associated entities and the graph of the relationships between these entities.
Entity Analysis
Below is an analysis of the incident's entities that appear in threat intelligence sources.
IP Entity Analysis
Below is an analysis of all IP entities attached to the incident.
URL Entity Analysis
Below is an analysis of all URL entities attached to the incident.
User Entity Analysis
Below is an analysis of all User entities attached to the incident.
Host Entity Analysis
Below is an analysis of all Host entities attached to the incident.
Timeline of other alerts with the same entities
If there are other entity types not analyzed above, a timeline of their appearance in security alerts appears below.