SOC-Automation-Project

Objective

The Soc Automation Project aimed to establish a full SOAR solution incorporating Wazuh instance with Source Integration along with functional case managment using TheHive.

Skills Learned

• Security Automation with Shuffle SOAR
• Incident Respone Planning and Execution
• Case Management with TheHive
• Scripting and Automation for Threat Mitigation

Tools Used

• Network diagram tools (such as Draw.io)
• Virtualization software VirtualBox
• Cloud Virtualization with Azure
• System Monitor for log collection(Sysmon)
• Security Incident Response (TheHive)
• OpenSource NoSQL Database (Cassandra)
• Search and analytics engine (Elasticsearch)
• SOAR (Shuffle)
• Email fo Online Dinamyc Analisis (SquareX)

Steps

Step 1 - Desing a diagram

Network Diagram

This diagram have 8 events

1. Wazuh Agent send Events to Wazuh Manager throught Internet (Green link = Send & Receive Events over Wazuh Manager)
2. Wazuh Manager receive events sent for Wazuh Agent
3. Wazuh Manager eventually would create an alert and send it to Shuffle (Red link = Send Alerts)
4. Enrich IOCS and send it back to shuffle
5. Shuffle send alert to TheHive
6. Shuffle send email to SOC Analyst containing details of the alert (Grey link= Send and Receive email)
7. SOC Analyst send response action over Shuffle, then over Wazuh Manager, and finally to Windows Client to perform that action
8. Windows Client perfome response action

Workflow

Step 2 - Install Components

Start making the Network

1. Virtualize Windows10 with VirtualBox

2. Install Sysmon

3. Install Wazuh

curl -sO https://packages.wazuh.com/4.7/wazuh-install.sh && sudo bash ./wazuh-install.sh -a

Extract Wazuh Credentials sudo tar -xvf wazuh-install-files.tar

4. Install TheHive dependences

Dependences apt install wget gnupg apt-transport-https git ca-certificates ca-certificates-java curl software-properties-common python3-pip lsb-release

Install Java wget -qO- https://apt.corretto.aws/corretto.key | sudo gpg --dearmor -o /usr/share/keyrings/corretto.gpg echo "deb [signed-by=/usr/share/keyrings/corretto.gpg] https://apt.corretto.aws stable main" | sudo tee -a /etc/apt/sources.list.d/corretto.sources.list sudo apt update sudo apt install java-common java-11-amazon-corretto-jdk echo JAVA_HOME="/usr/lib/jvm/java-11-amazon-corretto" | sudo tee -a /etc/environment export JAVA_HOME="/usr/lib/jvm/java-11-amazon-corretto"

Install Cassandra wget -qO - https://downloads.apache.org/cassandra/KEYS | sudo gpg --dearmor -o /usr/share/keyrings/cassandra-archive.gpg echo "deb [signed-by=/usr/share/keyrings/cassandra-archive.gpg] https://debian.cassandra.apache.org 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list sudo apt update sudo apt install cassandra

Install ElasticSearch wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo gpg --dearmor -o /usr/share/keyrings/elasticsearch-keyring.gpg sudo apt-get install apt-transport-https echo "deb [signed-by=/usr/share/keyrings/elasticsearch-keyring.gpg] https://artifacts.elastic.co/packages/7.x/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-7.x.list sudo apt update sudo apt install elasticsearch

OPTIONAL ELASTICSEARCH Create a jvm.options file under /etc/elasticsearch/jvm.options.d and put the following configurations in that file. -Dlog4j2.formatMsgNoLookups=true -Xms2g -Xmx2g

5. Install TheHive

wget -O- https://archives.strangebee.com/keys/strangebee.gpg | sudo gpg --dearmor -o /usr/share/keyrings/strangebee-archive-keyring.gpg echo 'deb [signed-by=/usr/share/keyrings/strangebee-archive-keyring.gpg] https://deb.strangebee.com thehive-5.2 main' | sudo tee -a /etc/apt/sources.list.d/strangebee.list sudo apt-get update sudo apt-get install -y thehive

Default Credentials on port 9000 credentials are 'admin@thehive.local' with a password of 'secret'

6. Configure TheHive

Configure Cassandra nano /etc/cassandra/cassandra.yaml cluster_name: 'Test Cluster' >> 'SocProject' #Optional listen_addres: localhost >> <PUBLIC_IP> TheHive rpc_adres: localhost >> <PUBLIC_IP> TheHive seed_provider:

• class_name: org.apache.cassandra.locator.SimpleSeedProvider parameters:
  • seeds: "127.0.0.1:7000" >> <PUBLIC_IP>:7000 TheHive Stop cassandra service, delete old files rm -rf /var/lib/cassandra/* Start cassandra service

Configure elasticsearch nano /etc/elasticsearch/elasticsearch.yml #cluster.name : my-application >> cluster.name: thehive #node.name: node-1 >> node.name: node-1 #network.host: 192.168.0.1 >> network.host: <PUBLIC_IP> TheHive #http.port: 9200 >> http.port: 9200 #cluster.initial_master_nodes: ["node-1","node-2"] >> cluster.initial_master_nodes: ["node-1"]

Now we can start the service "systemctl start elasticsearch" and then enable it "systemctl enable elasticsearch"

At this moment we start configuring TheHive First of all, we have to change the permissions of the hive in /opt/thp "chown -R thehive:thehive /opt/thp" Now we can configure thehhive applicattion conf nano /etc/thehive/application.conf db.janusgraph hostname = ["127.0.0.1"] >>> <PUBLIC_IP> TheHive cluster-name = thp >> SocProject index.seach hostname = ["127.0.0.1"] >>> <PUBLIC_IP> TheHive application.baseUrl = "http://localhost:9000" >>> <PUBLIC_IP>:9000 TheHive

Now we can start the service "systemctl start thehive" and then enable it "systemctl enable thehive"

7. Configure Wazuh

To log in Wazuh-Manager we need the admin credentials, for this we found it going to "cd/wazuh-install-files" where we find wazuh-passwords.txt

Click on Add agent, select OS system of the new agent (in this case W10), server addres = <PUBLIC_IP> Wazu, and Run the following command on the Windows machine and the start the server.

At this moment we can query events.

8. Windows telemetry

Config ossec.conf C:...\ProgramFiles(x86)\ossec-agent make log analysis with sysmon Microsoft-Windows-Sysmon/Operational (operational channel) <log_format>syslog</log_format> Restart Wazu.svc

9. Wazuh Dashboard configuration alert

On Wazuh Machine enable logs alert nano /var/ossec/etc/ossec.conf <ossec_config> ... no >> yes Making that wazuh put all logs in /var/ossec/logs/archives/archives/

At this moment we need to enable the filebeat module of archives to make that wazuh can save the logs in archives nano/etc/filebeat/filebeat.yml .... filebeat.modules_ -module: wazuh .... archives: enables: false >> enables: true

Create a new index for archives under wazuh-alerts Define an index pattern = wazu-archives-** Timefiled = timestamp

Only logs that trigger the rules will show up, for that we need to configure to show all logs if you want. For probe this rule we can execute mikmikatz in our W10 Client and grep the archives to see if its triggering. So execute mimikatz and then in /var/ossec/logs/archives cat archives.json | grep -i mimikatz If mimikatz display in the json but isnt in wazuhManager, can be enforced restarting wazuhManager service. To make a rule to trigger mimikatz we can use the originalFileName, because if we use the image the attaker can change the name and easily bypass the rule

To create a rule in Wazuh manager > Managment > Rules

ManageRules > search "sysmon" > "0800-sysmon_id_1.xml" (id_1 is process creation) We go here only to make a copy of a rule for our CustomRule

Go to Custom Rules and edit local_rules.xml Paste the rule that we copy and modify

Custom rules start in 100000 and the levels of priority are 1 to 15, where 15 has the mayor priority Save it and restart the manager.

To probe the rule we can change ne name of mimikatz in our w10 client and try to trigger it.

10: Configure Shuffle Their workflow will be

• Mimikatz Alert Sent to Shuffle
• Shuffle Receives Mimikatz Alert, extract SHA256 hash from file
• Check Reputation Score w/VirusTotal
• Send Detail to TheHive to Create Alert
• Send Email to SOC Analyst to Begin Investigation

Go to the website shuffle.io and create or ouw workflow. At this moment we start adding our applications, go to triggers and select Webhook and copy the WebhookURI. Click on Change Me Icon. On Find Actions = Repeat back to me and on Call click on "+" button and selec execution argument. On wazuhManager machine we need to configure to connect with shuffle nano /var/ossec/etc/oseec.conf

Under global tag paste the WebhookURI

Keep in mind the identation Replace hook_url including id and the copy WebhookURI, change the level tag to ruleId tag = <rule_id>10002</rule_id> Then restart the service and run mimikatz on the client to chekck if its working, will have all te information.

On Change Me in Find Actions tipe Regex and select Regex capture group and on input data click on "+" button, execution argument and select "hashes". Then in Regex we need to create a regex to parse the sha256 value, so we will use ChatGPT.

Now, we going to use virustotal, first create an accoutn and copy your API key. On shuffle seach for virustotal, activate and drag to the workflow. On Find Actions select Get a hash report, paste your API Key, and copy the regex command of Change Me. Primary virustotal dont show anything because, it go to /files/report so we need to fix this. So go to Apps in workflow, select the open new windows of virustotal, click on fork to edit it, go for "GET a hash report".

*change URL path/ Curl Statement to /files/{id} sumbit and save it.

Now, we start with TheHive, click en apps, search thehive, activate it and drag it to workflow. LogIn TheHive with default credentials, the create a new organisation, click into it, add two users, one as normal with analyst profile, and the other (SOAR) as service and profile as analyst. Create and API key for SOAR user. In shuffle select TheHive, and click on "+" in authenticate section and paste te SOAR APIkey, in url <PUBLIC_IP> TheHive, onfind actions change it to create alert, go to "Date" "+" button and execution argument "utcTime", on Description "Mimikatz Detected on host: "+" button and select host option, from user: "+" button and select user option, flag = false, PAP = 2, Source = Wazuh, Sourceref = "Rule:10002", Status = New, Summary Mimikatz Detected on host: "+" button and select host option on process ID: "+" button and select process_id option, Tittle = "+" button and select title option, Tlp (Trafic light protocol) = 2, Type = Internal

If we test the workflow we can see an alert in TheHive like this:

Next step "Send Emal"

Type in apps "email" and select email option, for avoid the use of our personal email we can use SquareX as describes itself "SquareX's browser extension keeps you safe from malicious activity online. However, unlike existing products that block access to files and websites, SquareX allows you to open even suspicious or malicious resources fearlessly! " so we can browse to the suspicius site safety and acquire the information for the investigation.

Well, select email in Recipients = SquareX email, Subject = Mimikatz Detected, Body = Time = "+" button and select utctime option / Tittle = "+" button and select title option /host: "+" button and select host option.

For the response setup we need to create a VM on cloud and create a rule that allow all tcp connections. We can run "iptables -P INPUT ACCEPT" to accept all the traffic Or in this case we are going to use port 55000 so we can run "iptables -I INPUT -p tcp -m tcp --dport 55000 -j ACCEPT && service iptables sav" or we can flush it So we can flush al iptables: iptables -F iptables -X iptables -t nat -F iptables -t nat -X iptables -t mangle -F iptables -t mangle -X iptables -t raw -F iptables -t raw -X iptables -t security -F iptables -t security -X iptables -P INPUT ACCEPT iptables -P FORWARD ACCEPT iptables -P OUTPUT ACCEPT

Then iptables -A INPUT -i lo -j ACCEPT -m comment --comment "Allow all loopback traffic" iptables -A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT -m comment --comment "Drop all traffic to 127 that doesn't use lo" iptables -A OUTPUT -j ACCEPT -m comment --comment "Accept all outgoing" iptables -A INPUT -j ACCEPT -m comment --comment "Accept all incoming" iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -m comment --comment "Allow all incoming on established connections" iptables -A INPUT -j REJECT -m comment --comment "Reject all incoming" iptables -A FORWARD -j REJECT -m comment --comment "Reject all forwarded"

And finally save it with "iptables-save > /etc/network/iptables.rules" #Or wherever your iptables.rules file is

Then go to Apps search for Http select it and drag it, in find actiones select Curl, Statement = curl -u USER:PASSWORD>WazuhAPIuser> -k -x GET "https://<PUBLIC_IP>WAZUH-IP:55000/security/user/authenticate?raw=true We need this to get de API capability for get JsonWebToken.

In Shuffle apps search Wazuh select it and drag it in Find Actions = Run Command, APIkey "+" button and select GETAPI option (this option was created previously), URL = <WAZUH_PUBLIC_IP>, AgentID "+" button and select agent_id option. On WazuhManager Console nano /var/ossec/etc/ossec.conf go to the bottom and search "Active response", uncomment active-response section.

On Shuffle select Wazuh, Command = firewall-drop0 (0 because timeout=no), Alert {"data":{"script":"$exec.all_fields.data.scrip"}}

Now Set Up an User Input

On Email <SQUAREX_EMAIL>, Description = Would you like block this source IP: $exec.all_fields.data.scrip

At this moment, everything should work