ThreatConnect TAXII 2.1 Server (App Version 2.0)
- 18 Dec 2024
- 1 Minute to read
-
Print
-
DarkLight
ThreatConnect TAXII 2.1 Server (App Version 2.0)
- Updated on 18 Dec 2024
- 1 Minute to read
-
Print
-
DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Note
The articles in this series describe how to use ThreatConnect TAXII 2.1 server available with version 2.0 of the ThreatConnect TAXII Server App. For instruction on using the ThreatConnect TAXII 2.1 server available with version 1.0 of the ThreatConnect TAXII Server App, see Using the ThreatConnect TAXII 2.1 Server (App Version 1.0). For instruction on using the ThreatConnect TAXII 1.x server, see Using the ThreatConnect TAXII Server.
Overview
The ThreatConnect® TAXII™ 2.1 server operates via a ThreatConnect Service App and can be used by an external TAXII client to retrieve data from your Organization, Communities, and Sources. To connect to the ThreatConnect TAXII 2.1 server, the external TAXII client will require login credentials (username and password), which are configured by creating a TAXII user.
The ThreatConnect TAXII 2.1 server supports collection and object requests. The latest version of TAXII 2.1 documentation is available at https://oasis-open.github.io/cti-documentation/resources.html#taxii-21-specification.
In This Series
- Installing and Configuring the ThreatConnect TAXII 2.1 Server (App Version 2.0): Learn how to install version 2.0 of the ThreatConnect TAXII Server Service App, configure a Service for the App, and use the ThreatConnect TAXII Server user interface.
- Creating a TAXII User for the ThreatConnect TAXII 2.1 Server (App Version 2.0): Learn how to create a TAXII user account and configure it to use the ThreatConnect TAXII 2.1 server.
- Retrieving Data From the ThreatConnect TAXII 2.1 Server (App Version 2.0): Learn how to retrieve data from the ThreatConnect TAXII 2.1 server via the TAXII REST API.
ThreatConnect® is a registered trademark of ThreatConnect, Inc.
TAXII™ is a trademark of The MITRE Corporation.
20167-01 v.01.A
Was this article helpful?