Skip to content
This repository was archived by the owner on Apr 4, 2025. It is now read-only.

Commit a457004

Browse files
authored
Hotfix (#41)
* Add API Documentation * Other Changes * Custom Rules * Bug solutions * Bugs solutions
1 parent a58e9ca commit a457004

File tree

6 files changed

+47
-11
lines changed

6 files changed

+47
-11
lines changed

Correlation Rules/CustomizableRules.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,21 @@ UTMStack allows users to define customizable rules to enhance the monitoring and
1212
## Follow these steps:
1313

1414
1. Access the directory where the system correlation rules are located.
15-
<img title="Menu Correleation Rules" alt="Menu Correleation Rules" src="../Images/menu_custom_rules.png">
15+
<img title="Menu Correleation Rules" alt="Menu Correleation Rules" src="../Images/menu_custom_rules.png" width="500">
16+
1617

1718
2. Select the folder named "custom", intended for custom rules.
1819
<img title="Directory Correleation Rules" alt="Directory Correleation Rules" src="../Images/directory_custom_rules.png">
1920

2021
3. Add, copy, paste or move your customized rules to this folder.
21-
<img title="Create Correleation Rules" alt="Create Correleation Rules" src="../Images/new_custom_rules.png">
22+
<img title="Create Correleation Rules" alt="Create Correleation Rules" src="../Images/new_custom_rules.png" width="500">
23+
2224

2325
4. Check that they are correctly placed and that their names match the system rules you want to modify.
2426

2527
## Modifying system rules:
28+
If you need to adjust a system rule, simply create a new custom rule with the same name as the system rule you wish to modify. This will allow your custom rule to take precedence over the original system rule. The custom rule must be placed inside the "custom" folder, and if the folder does not exist, it must be created.
2629

27-
If you need to adjust a system rule, simply create a new custom rule with the same name as the system rule you wish to modify. This will allow your custom rule to take precedence over the original system rule.
2830

2931
## Rule Priority:
3032

Images/.DS_Store

0 Bytes
Binary file not shown.

Integrations/ThreatDetectionandResponse.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -67,10 +67,10 @@ Our team is always working on a new integration, but here is the list of what we
6767
| 42 | Nginx | <img title="Nginx" alt="Nginx" src="../Images/Integrations/logonginx.svg"> |
6868
| 43 | Sophos Central | <img title="Sophos Central" alt="Sophos Central" src="../Images/Integrations/logosophoscentral.svg"> |
6969
| 44 | SentinelOne Endpoint Security | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/logosentinelone.svg"> |
70-
| 45 | PfSense | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/pfsenselogo.png"> |
71-
| 46 | IBM AIX | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/IBMAIXlogo.png.png"> |
72-
| 47 | FortiWeb | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/logofortigate.png"> |
73-
| 48 | NetFlow | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/netflowlogo.png"> |
70+
| 45 | PfSense | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/pfsenselogo.png" width="300" height="300"> |
71+
| 46 | IBM AIX | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/IBMAIXlogo.png" width="300" height="300"> |
72+
| 47 | FortiWeb | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/logofortigate.svg"> |
73+
| 48 | NetFlow | <img title="SentinelOne Endpoint Security" alt="SentinelOne Endpoint Security" src="../Images/Integrations/netflowlogo.png" width="150" height="150"> |
7474

7575

7676

QuickStart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ Add a Windows agent to forward logs and data to UTMStack.
9494
## Procedure:
9595
9696
### 1. Pre-installation Requirements:
97-
* **Compatibility:** Ensure the system runs on Windows Server version 2016 R2 or later.
97+
* **Compatibility:** Ensure that the system is running Windows 10/11, Windows Server version 2016 R2 or later.
9898
* **Network:** Ensure ports 9000 and 50051 are open.
9999
100100
### 2. Installation Steps:

Upgrade/README.md

Lines changed: 36 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,40 @@
11
---
22
layout: default
3-
title: Upgrade
3+
title: Update
44
nav_order: 5
55
has_children: true
6-
---
6+
---
7+
8+
# UTMStack Update Guide
9+
10+
Keeping your UTMSTACK software up to date is essential for maintaining system security, performance, and access to the latest features. This guide will walk you through the necessary steps to update UTMSTACK to the latest version.
11+
12+
1. Update packages list:
13+
14+
```bash
15+
sudo apt update
16+
```
17+
18+
2. Download the latest version of the installer:
19+
20+
```bash
21+
wget http://github.com/utmstack/UTMStack/releases/latest/download/installer
22+
```
23+
24+
3. Change to root user:
25+
26+
```bash
27+
sudo su
28+
```
29+
30+
4. Set execution permissions:
31+
32+
```bash
33+
chmod +x installer
34+
```
35+
36+
5. Execute the installer:
37+
38+
```bash
39+
./installer
40+
```

Upgrade/UpgradeFederationService.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: Upgrade Federation Service
4-
parent: Upgrade
4+
parent: Update
55
nav_order: 5
66
---
77

0 commit comments

Comments
 (0)