Oasis STIX/TAXII2

introduction this guide tells you how to authenticate the oasis taxii2 connector in swimlane the connector supports http basic authentication and client certificate authentication you will configure authentication details for your taxii server, collect the required credentials, and configure the connector asset in swimlane turbine prerequisites taxii server access requirements you must have access to a taxii 2 0 or taxii 2 1 server with permissions to access taxii collections retrieve and submit stix objects use api authentication (http basic or client certificate) required credentials depending on the authentication method used, collect the following information taxii server root url username and password (for http basic authentication) client side certificate (base64 encoded) client side key (base64 encoded) taxii version indicator (taxii 2 1 enabled or disabled) authentication methods overview the oasis taxii2 connector supports the following authentication methods http basic authentication client certificate authentication taxii server setup authentication configuration depends on the taxii server implementation take the following general steps to prepare authentication access log in to your taxii server administration console create or identify a user account with access to taxii collections enable http basic authentication for the account if required if certificate authentication is used, generate a client certificate and key export the client certificate and key as base64 encoded strings confirm whether your server supports taxii 2 0 or taxii 2 1 copy the taxii server root url connector configuration in swimlane take the following steps to configure the oasis taxii2 connector asset in swimlane log in to turbine from the left hand navigation pane, click orchestration and click assets the asset homepage opens click the plus icon to open the configure your connector asset window select oasis taxii2 from the asset type list fill in the asset settings and asset input as shown below click create configuration – http basic authentication true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type configuration – client certificate authentication true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type troubleshooting if authentication fails ensure the taxii server url is correct confirm the username and password are valid verify the client certificate and key are correctly base64 encoded ensure the taxii version setting matches the server version check ssl verification and proxy settings if applicable sources oasis taxii 2 0 documentation https //docs oasis open org/cti/taxii/v2 0/ oasis taxii 2 1 documentation https //docs oasis open org/cti/taxii/v2 1/ result you have successfully authenticated the oasis taxii2 connector in swimlane