Plugins

Plugins

At NCSC, we use our own fork on top of the public Taranis release. This has only one reason: that code is very, very bound to our own environment. Only a few of Taranis' components are nicely pluggable. Other changes can get their place in your own fork of this project.

How to create plugins

The few components which support pluggable code do support your private namespace. At the moment, there are two of those: for sub-commands of bin/taranis, and for the REST server. Configure local_package_base in the taranis.conf.xml file.

For instance, we use NCSC_NL which will try to load additional components from the NCSC/Command/*.pm (new sub-commands for the 'taranis' command) and NCSC_NL/REST/*.pm (additional REST server calls).

NCSC extensions

When you start developing your own plugins, you may want to have a look at our extensions as example. That's the only reason to list them here.

1. an additional step after sending advisory emails, to publish them to the website.
2. import constituent groups (organizations) and their individuals (contact persons) into Taranis automatically
3. publish selected items to Confluence