@@ -10,22 +10,43 @@ This integration works across multiple entities:
10
10
- Grouping
11
11
- Incident Response
12
12
- Malware
13
- - Campaings
13
+ - Campaigns
14
14
- Intrusion
15
15
- Request For Information
16
16
- Request For Takedown
17
17
18
18
![ simulate button] ( assets/simulate-btn.png )
19
19
20
- When you click on the simulate button, you’ll have two options :
20
+ When you click the "Simulate" button, a form will appear with the following fields :
21
21
22
- - Generate a scenario based on technical injects
23
- - Generate a scenario based on email injects, using AI to automatically generate email content
22
+ | Property | Description |
23
+ | ------------------------------------------------------------------| ---------------------------------------------------------------|
24
+ | Simulation type | Can be either "Technical" (payloads) or "Simulated" (emails) |
25
+ | Interval between injection (in minutes) | The time between each injection execution |
26
+ | Number of injects generated by attack <br />pattern and platform | |
27
+
28
+ ![ simulation simulated] ( assets/octi-form-options.png )
29
+ ![ simulation simulated] ( assets/octi-form-simulated.png )
30
+
31
+ If you choose the "Technical" (payloads) simulation type, you will also need to fill in the following fields:
32
+
33
+ | Property | Description |
34
+ | ------------------------------------------------------------------| --------------------------------------------------------------------|
35
+ | Targeted platforms | Supported platforms for executing the TTPs (Windows, Linux, macOS) |
36
+ | Targeted architecture | Supported architectures for executing the TTPs (x86_64, arm64) |
37
+
38
+ ![ simulation technical(payloads)] ( assets/octi-form-technical.png )
39
+ ![ simulation technical(payloads)] ( assets/octi-form-tech-arch.png )
40
+ ![ simulation technical(payloads)] ( assets/octi-alert-technical.png )
24
41
25
42
It’s essential to understand that a scenario creation for these entities relies on matching TTPs between OpenCTI and
26
43
OpenBAS. You’ll need to ensure that the TTPs in both platforms are aligned. For instance, if your report contains the
27
44
TTP T1059.001, a scenario can be created with an inject, provided OpenBAS also includes T1059.001.
28
45
46
+ If these TTPs are not supported by OpenBAS, you will receive an alert listing the uncovered TTPs.
47
+
48
+ ![ ttps not covered obas] ( assets/octi-ttp-not-covered.png )
49
+
29
50
When generating a scenario from OpenCTI, a scenario is created and can be accessed from the scenarios screen. The
30
51
scenario name will include a reference to OpenCTI, indicating its origin. This scenario will automatically contain
31
52
relevant sequences of injects based on the threat context identified in OpenCTI.
0 commit comments