This repository has been archived by the owner. It is now read-only.
OASIS TC Open Repository: Prototype for processing granular data markings in STIX
Python
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
examples
stixmarker
test
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE
README.md
requirements.txt
setup.py
tox.ini

README.md

cti-marking-prototype

N.B. Archived Repository. At the request of the OASIS Cyber Threat Intelligence (CTI) TC (TC Chair, GitHub Repository Maintainers, GitHub Repository Technical Leads), the cti-marking-prototype public GitHub repository was scheduled for archiving on Tuesday, March 27, 2018. Per OASIS TC Open Repository rules for Repository Lifecycle and Archival Permanence, the repository content is now preserved as a read-only resource, with the expectation that the repository will not be re-opened.


This is an OASIS Open Repository. See the Governance section for more information.

The marking-prototype is a prototype implementation of granular data markings in STIX. It provides a potential API that can be used to create and process the markings, in order to examine the utility, usability, and completeness of how the granular data markings are specified. After the markings are added to the STIX specification, the code in this library may be used as reference, or incorporated directly into other libraries, but is not intended to be released as a standalone tool or library.

Supports both object markings and granular markings.

Requirements

  • Python 2.7.6+ or Python 3.5.0+
  • six 1.10.0

Governance

This GitHub public repository ( https://github.com/oasis-open/cti-marking-prototype ) was proposed and approved [bis] by the OASIS Cyber Threat Intelligence (CTI) TC as an OASIS Open Repository to support development of open source resources related to Technical Committee work.

While this 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 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 Open Repository was created.

As documented in "Public Participation Invited", contributions to this OASIS 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 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

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.

Current Maintainers of this Open Repository

About OASIS Open Repositories

Feedback

Questions or comments about this 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. Please send general questions about Open Repository participation to OASIS Staff at repository-admin@oasis-open.org and any specific CLA-related questions to repository-cla@oasis-open.org.