MISP/misp-taxonomies

Adding another taxonomy...

Closed this issue · 4 comments

OK, so I know about RTFM, but have read, re-read, re-re-read, et. al -- the documentation to determine if I was loosing it, or not.

I added a new directory under the /var/www/MISP/app/files/taxonomies directory, and clicked on 'Update Taxonomies" -- nothing. Nothing showed up.

Am I missing something here? Made it the same permissions as everything else. The taxonomy was duplicated using the TLP as its 'base' (so that should've worked). So...the question is -- what did I do wrong?

It should work. Maybe you didn't change the name space in your JSON file? I hope this helps.

Just to make sure, basically what is needed is the following:

/var/www/MISP/app/files/taxonomies/my_taxonomy directory
/var/www/MISP/app/files/taxonomies/my_taxonomy/machinetag.json file containing the taxonomy data

The new taxonomy vocabulary has to have its own unique namespace, it needs a version number and a description at the very least.

Make sure that all of it is readable by the apache user and it should work.

If you've tried all of these and are still stuck, let us know!

I figured it out (again)!

But...here's the weird thing that happened...

I found the tools' file, and had originally added the new taxonomy as "cipsector", both with its own directory (and "machinetag.json" file), and to the array within the "./tools/machinetag.py" file.

It originally did not add in the new taxonomy when I selected "Update Taxonomies".

However...

When I added it in as "cipsectors" (plural), and corrected the array within the "./tools/machinetag.py" file, somehow -- it worked!

Now...how about that for weird??? Am closing the incident...again!

-rad

P.S. I hope you're not annoyed by my comments or requests...

Not at all, thanks for all the feedback, figuring out the steps at which it goes wrong for you helps us streamline the process :)