Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/oasis-open/cti-python-stix2

OASIS TC Open Repository: Python APIs for STIX 2
https://github.com/oasis-open/cti-python-stix2

cti cyber-threat-intelligence json oasis python stix stix2

Last synced: 6 days ago
JSON representation

OASIS TC Open Repository: Python APIs for STIX 2

Awesome Lists containing this project

README 

        
|Build_Status| |Coverage| |Version| |Downloads_Badge| |Documentation_Status|



cti-python-stix2

================



This is an `OASIS TC Open Repository `__.

See the `Governance <#governance>`__ section for more information.



This repository provides Python APIs for serializing and de-serializing STIX2

JSON content, along with higher-level APIs for common tasks, including data

markings, versioning, and for resolving STIX IDs across multiple data sources.



For more information, see `the documentation `__ on ReadTheDocs.



Installation

------------



Install with `pip `__:



.. code-block:: bash



  $ pip install stix2



Note: The library requires Python 3.6+.



Usage

-----



To create a STIX object, provide keyword arguments to the type's constructor.

Certain required attributes of all objects, such as ``type`` or ``id``,  will

be set automatically if not provided as keyword arguments.



.. code-block:: python



    from stix2 import Indicator



    indicator = Indicator(name="File hash for malware variant",

                          indicator_types=["malicious-activity"],

                          pattern_type="stix",

                          pattern="[file:hashes.md5 = 'd41d8cd98f00b204e9800998ecf8427e']")



To parse a STIX JSON string into a Python STIX object, use ``parse()``. To serialize a STIX object, use ``serialize()``:



.. code-block:: python



    from stix2 import parse



    indicator = parse("""{

        "type": "indicator",

        "spec_version": "2.1",

        "id": "indicator--dbcbd659-c927-4f9a-994f-0a2632274394",

        "created": "2017-09-26T23:33:39.829Z",

        "modified": "2017-09-26T23:33:39.829Z",

        "name": "File hash for malware variant",

        "indicator_types": [

            "malicious-activity"

        ],

        "pattern_type": "stix",

        "pattern_version": "2.1",

        "pattern": "[file:hashes.md5 ='d41d8cd98f00b204e9800998ecf8427e']",

        "valid_from": "2017-09-26T23:33:39.829952Z"

    }""")



    print(indicator.serialize(pretty=True))



For more in-depth documentation, please see `https://stix2.readthedocs.io/ `__.



STIX 2 Technical Specification Support

--------------------------------------



This version of cti-python-stix2 brings support to `STIX Version 2.1 `__

published on 10 June 2021 currently at the Committee Specification (CS) 03 level, also know as the "OASIS Standard".



The stix2 Python library supports multiple versions of the STIX 2 Technical

Specification. The library will be updated to support new Committee

Specification Drafts (CSDs) as they are released, but modules for these

versions must be imported manually until the CSD reaches CS level. In new

major releases of stix2 the ``import stix2`` implicit import statement

will be updated to automatically load the STIX Objects equivalent to the most

recently supported CS. Please see the `library documentation `__

for details.



Governance

----------



This GitHub public repository (**https://github.com/oasis-open/cti-python-stix2**) was

`proposed `__ and

`approved `__

[`bis `__] by the

`OASIS Cyber Threat Intelligence (CTI) TC `__

as an `OASIS TC Open Repository `__

to support development of open source resources related to Technical Committee work.



While this TC Open Repository remains associated with the sponsor TC, its

development priorities, leadership, intellectual property terms, participation

rules, and other matters of governance are `separate and distinct

`__

from the OASIS TC Process and related policies.



All contributions made to this TC Open Repository are subject to open

source license terms expressed in the `BSD-3-Clause License `__.

That license was selected as the declared `"Applicable License" `__

when the TC Open Repository was created.



As documented in `"Public Participation Invited

`__",

contributions to this OASIS TC Open Repository are invited from all parties,

whether affiliated with OASIS or not. Participants must have a GitHub account,

but no fees or OASIS membership obligations are required. Participation is

expected to be consistent with the `OASIS TC Open Repository Guidelines and Procedures

`__,

the open source `LICENSE `__

designated for this particular repository, and the requirement for an

`Individual Contributor License Agreement `__

that governs intellectual property.



Maintainers

~~~~~~~~~~~



TC Open Repository `Maintainers `__

are responsible for oversight of this project's community development

activities, including evaluation of GitHub

`pull requests `__

and `preserving `__

open source principles of openness and fairness. Maintainers are recognized

and trusted experts who serve to implement community goals and consensus design

preferences.



Initially, the associated TC members have designated one or more persons to

serve as Maintainer(s); subsequently, participating community members may

select additional or substitute Maintainers, per `consensus agreements

`__.



.. _currentmaintainers:



**Current Maintainers of this TC Open Repository**



-  `Jason Keirstead `__; GitHub ID:

   https://github.com/JasonKeirstead; WWW: `IBM `__



-  `Emily Ratliff `__; GitHub ID:

   https://github.com/ejratl; WWW: `IBM `__



-  `Rich Piazza `__; GitHub ID:

   https://github.com/rpiazza; WWW: `MITRE `__



About OASIS TC Open Repositories

--------------------------------



-  `TC Open Repositories: Overview and Resources `__

-  `Frequently Asked Questions `__

-  `Open Source Licenses `__

-  `Contributor License Agreements (CLAs) `__

-  `Maintainers' Guidelines and Agreement `__



Feedback

--------



Questions or comments about this TC Open Repository's activities should be

composed as GitHub issues or comments. If use of an issue/comment is not

possible or appropriate, questions may be directed by email to the

Maintainer(s) `listed above <#currentmaintainers>`__. Please send general

questions about TC Open Repository participation to OASIS Staff at

[email protected] and any specific CLA-related questions

to [email protected].



.. |Build_Status| image:: https://github.com/oasis-open/cti-python-stix2/workflows/cti-python-stix2%20test%20harness/badge.svg

   :target: https://github.com/oasis-open/cti-python-stix2/actions?query=workflow%3A%22cti-python-stix2+test+harness%22

   :alt: Build Status

.. |Coverage| image:: https://codecov.io/gh/oasis-open/cti-python-stix2/branch/master/graph/badge.svg

   :target: https://codecov.io/gh/oasis-open/cti-python-stix2

   :alt: Coverage

.. |Version| image:: https://img.shields.io/pypi/v/stix2.svg?maxAge=3600

   :target: https://pypi.python.org/pypi/stix2/

   :alt: Version

.. |Downloads_Badge| image:: https://img.shields.io/pypi/dm/stix2.svg?maxAge=3600

   :target: https://pypi.python.org/pypi/stix2/

   :alt: Downloads

.. |Documentation_Status| image:: https://readthedocs.org/projects/stix2/badge/?version=latest

   :target: https://stix2.readthedocs.io/en/latest/?badge=latest

   :alt: Documentation Status