-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: rename signatures to TTPs and update the docs
- Loading branch information
Showing
6 changed files
with
37 additions
and
8 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,19 @@ | ||
# Intezer Anomali Integration | ||
[Intezer Analyze](https://analyze.intezer.com) integration with anomali provide hash enrichment. | ||
The [Intezer Analyze](https://analyze.intezer.com) integration with Anomali provides enrichment data for hash observables. | ||
|
||
## How does it work? | ||
The integration will take the hash and query it in Intezer Analyze for the last analysis. | ||
The integration will take the hash and query it in Intezer Analyze for the latest analysis. | ||
If an analysis is not found, the integration will try and analyze the hash in case the file is available in Intezer Analyze. | ||
|
||
## Setup | ||
To activate the Intezer Analyze enrichment: | ||
1. Log in to the ThreatStream user interface. | ||
2. In the top navigation bar, click the App Store. | ||
2. Navigate to APP Store > APP Store. | ||
3. Search for Intezer Analyze, and click "Get Access". | ||
4. Click "I have already registered" and enter your Intezer API Key found in [account details](https://analyze.intezer.com/account-details). | ||
5. Configure additional parameters: | ||
* Timeout waiting for an analysis to finish in seconds (optional, max is 25), the default is to wait 25 seconds. | ||
* Should the querying of the latest analysis only return private analysis, default is false. | ||
* Analysis Timeout in Seconds: Timeout waiting for an analysis to finish in seconds (optional, max is 25), the default is to wait 25 seconds. | ||
* Private Analysis: Should the querying of the latest analysis only return private analysis, default is false. | ||
Use this to avoid consuming quota everytime you query a hash. | ||
6. If errors occur, contact [email protected] for assistance. | ||
|
||
|
@@ -22,15 +22,39 @@ To activate the Intezer Analyze enrichment: | |
## Integration Capabilities | ||
The integration will show Intezer verdict and analysis details first: | ||
![Analysis details](.artwork/analysis_details.png) | ||
Fields description: | ||
* **Analysis Id**: A unique identifier assigned to the results of this analysis. | ||
* **Analysis Time**: The date that the analysis was executed. | ||
* **Analysis Url**: A link to a web page in the Intezer Analyze web interface. | ||
* **Family Name**: The name of the family of this file. For example, WannaCry, Lazarus, Magic Hound or zlib. | ||
* **Family Id**: A uuid identifier of the family. | ||
* **Labels**: Labels set to this file, either ones set by Intezer, or ones set by the user. | ||
* **Is Private**: Specifies that the genes of this analyzed file also run against your private Genome Database. | ||
* **Sha256**: The SHA256 Hash of the file. | ||
* **Verdict**: The result of the analysis. For example, Malicious, Trusted, Unknown or Suspicious. | ||
* **Sub Verdict**: Additional details about the verdict. | ||
|
||
### Network IOCs | ||
Network indicators are composed of IPs, domains and URLs collected during the analysis from multiple different sources. These include addresses that were contacted during dynamic execution and addresses that were extracted from an embedded malware configuration. | ||
![Network IOCs](.artwork/network_iocs.png) | ||
|
||
Notable columns: | ||
* **Source Type**: specifies where each indicator was retrieved from. | ||
* **Classification**: The verdict and, if relevant, the malware family known to be associated with this address. | ||
|
||
|
||
### Files IOCs | ||
File indicators are SHA256 hashes of files collected during the analysis from various sources such as static unpacking and collected dropped files. The classification shown is the one that was assigned to each file from genetic analysis. | ||
![Files IOCs](.artwork/files_iocs.png) | ||
|
||
### Signatures | ||
![Signatures](.artwork/signatures.png) | ||
### TTPs | ||
Tactics, Techniques, and Procedures (TTPs) allows analysts to understand how the analyzed file operates, and the possible risk posed by it. | ||
The TTPs feature expands the static analysis context by focusing on the actual actions performed during dynamic execution. | ||
![Signatures](.artwork/ttps.png) | ||
Notable columns: | ||
* **MITRE ATT&CT**: [MITRE ATT&CK](https://attack.mitre.org/) Technique Detection name. | ||
* **Technique**: The technique seen in the dynamic execution. | ||
* **Details**: more details on each TTP, including process information, URLs and more. | ||
|
||
## Integration Details | ||
### Supported entities | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters