{"id":8230,"date":"2026-03-22T20:43:15","date_gmt":"2026-03-22T18:43:15","guid":{"rendered":"https:\/\/scalemedia.co.za\/cybermedia\/?post_type=docs&p=8230"},"modified":"2026-03-24T20:48:23","modified_gmt":"2026-03-24T18:48:23","password":"","slug":"lab-building-series-ep6","status":"publish","type":"docs","link":"https:\/\/scalemedia.co.za\/cybermedia\/docs\/lab-building-series-ep6\/","title":{"rendered":"Lab Building Series: Ep6"},"content":{"rendered":"\n

I will show you how to integrate Cortex & MISP with TheHive, The integration allows TheHive to directly trigger analysis in Cortex and MISP, receive threat alerts from MISP and send gathered intelligence back to MISP for sharing. When a security incidents occur response time are key and therefore integrating and automating our SOCK as much as possible is a key to reduce time and we can focus on the interestings things. To make possible to complete some basic configurations in both MISP and Cortex, Open your terminal where your server is running and ssh into it.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

First check if the Docker containers are online by running the docker up command<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Let’s access TheHive using our default user name and password, Next if you go to the platform management setting you’ll see we’re using the community license.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Now go to MISP dashboard in my case the IP address is 10.0.3.9, After login change your password. Next let’s create a new organisation and a new user, We can head over to Administration > Add Organisation. You can name it any name you want, I’ll name mine to IT Department and clik submit. Next step we need to create a user account that is tied to the IT Department organisation. Go to Administration > Add user. The user name must be in an email format. After you are done click on Create User<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

The final step of the configuration in MISP is to create a Auth key, a Auth key is what make all this integration between TheHive and Cortext. In order to set up a Auth key click on the little view icon.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Now click on the Auth keys and select Add authentication key. Select our user and click submit, Don’t forget to save your auth key because we’ll use it again.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Now let’s open Cortex and follow similar steps, Cortext IP Address 10.0.3.9:9001, Next click on Add Organization and give it a name and save.<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Now let’s add a user and create an API key that we’ll use later, go over to users and click on Add user.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Next we need to set up password for this user click on New password and put your password, and create an API key, Copy the API key.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

Next we need to put our docker compose offline to make changes to the docker-composer.yaml file<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Let’s open the yaml file by typing sudo nano docker-compose.yml<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Replace this key to your Cortex key<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Now we need to add our MISP API key, open Thehive and navigate to platform management, go to Cortex tab and you can see we have our Cortex set up, if you open it you can see all the information including our API key. <\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

Next click on MISP and change the setting make sure you include your MISP API key, And click Update<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

You should see the Cortex icon and the MISP icon in green which means both servers are online.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Let’s create an organisation and a user, click on organisation, give it a name and click on confirm.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

To create a user is the same process click on users and add user and give it a name, you need to create a password for our new user by clicking on preview<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Let’s login with our new user.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Great all the best for the next series\u00a0\ud83d\ude42<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

I will show you how to integrate Cortex & MISP with TheHive, The integration allows TheHive to directly trigger analysis in Cortex and MISP, receive threat alerts from MISP and send gathered intelligence back to MISP for sharing. When a security incidents occur response time are key and therefore integrating and automating our SOCK as…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"doc_category":[47],"doc_tag":[],"class_list":["post-8230","docs","type-docs","status-publish","hentry","doc_category-cyber-security-lab-building"],"year_month":"2026-04","word_count":554,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"admin","author_nicename":"admin","author_url":"https:\/\/scalemedia.co.za\/cybermedia\/author\/admin\/"},"doc_category_info":[{"term_name":"Cyber Security lab building","term_url":"https:\/\/scalemedia.co.za\/cybermedia\/docs-category\/cyber-security-lab-building\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/docs\/8230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/comments?post=8230"}],"version-history":[{"count":10,"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/docs\/8230\/revisions"}],"predecessor-version":[{"id":8285,"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/docs\/8230\/revisions\/8285"}],"wp:attachment":[{"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/media?parent=8230"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/doc_category?post=8230"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/scalemedia.co.za\/cybermedia\/wp-json\/wp\/v2\/doc_tag?post=8230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}