• Home
• org.mitre
• stix
• 1.2.0.1
• source code
• README.md

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

schemas.v1.2.0.README.md Maven / Gradle / Ivy

# STIX Schema Development

**NOTE:** If you are looking for official releases of STIX, please see
http://stix.mitre.org/language/ . The schemas in this respository (even the
[tagged releases](https://github.com/STIXProject/schemas/releases)) are NOT
OFFICIAL, as there are a couple post-processing steps not covered in the files
in this repository.  If there are any inconsistencies between the files in this
repository and the files on stix.mitre.org, the files there take precedence.

## About STIX

Structured Threat Information eXpression (STIX) is a collaborative community-driven effort to define and develop a standardized language to represent structured cyber threat information. The STIX Language intends to convey the full range of potential cyber threat information and strives to be fully expressive, flexible, extensible, automatable, and as human-readable as possible. All interested parties are welcome to participate in evolving STIX as part of its open, collaborative community.

Please visit the [STIX Web Site](http://stix.mitre.org) for more information about the STIX Language.

The STIX Language operates under the [STIX Terms of Use](http://stix.mitre.org/about/termsofuse.html).

## Getting Help

[![Join the public chat](https://badges.gitter.im/gitterHQ/gitter.png)](https://gitter.im/STIXProject/schemas)

E-mail the developers at 

[Get started with a STIX tutorial](http://stixproject.github.io/getting-started/)

## Cloning the repository

This STIX schemas repository uses [git submodules](http://git-scm.com/book/en/Git-Tools-Submodules) in order to include the CybOX schemas (which are a dependency of the STIX schemas).

A straight `git clone` command will not retrieve these automatically, you'll end up with an empty cybox directory rather than the schemas. To fix this you need to initialize and then update the submodules by running:

    git submodule init
    git submodule update

Alternatively, using the `--recursive` flag when cloning the repository will automatically initialize and update the submodules.

Finally, any time you see that the cybox directory has been modified (when merging or pulling updates) you will need to run `git submodule update` again to actually update the schemas themselves.