cti-stix2-json-schemas - GitLite

KO | EN

gitlite — search

#javascript #python #ai #typescript #rust #linux #docker #macos #windows #awesome #kubernetes #pytorch #mcp #openai

cti-stix2-json-schemas

(★ 144)

OASIS TC Open Repository: Non-normative schemas and examples for STIX 2

파일 탐색기

최종 버전 다운로드 (.zip)

- - python-ci-tests.yml
- - apt1.json
  - poisonivy.json
- indicator-for-c2-ip-address.json
- indicator-to-campaign-relationship.json
- indicators-for-C2-with-COA.json
- infrastructure.json
- interop-objectmarking-test.json
- malicious-email-indicator-with-attachment.json
- README.md
- attack-pattern.json
- campaign.json
- core.json
- course-of-action.json
- grouping.json
- indicator.json
- infrastructure.json
- intrusion-set.json
- location.json
- malware-analysis.json
- malware.json
- note.json
- observed-data.json
- opinion.json
- relationship.json
- report.json
- sighting.json
- threat-actor.json
- tool.json
- vulnerability.json
- STIXPattern.g4
- - binary.json
  - bundle.json
  - core.json
  - cyber-observable-core.json
  - dictionary.json
  - extension-definition.json
  - extension.json
  - external-reference.json
  - granular-marking.json
  - hashes-type.json
  - hex.json
  - identifier.json
  - kill-chain-phase.json
  - language-content.json
  - marking-definition.json
  - properties.json
  - timestamp.json
  - url-regex.json
- - artifact.json
  - autonomous-system.json
  - directory.json
  - domain-name.json
  - email-addr.json
  - email-message.json
  - file.json
  - ipv4-addr.json
  - ipv6-addr.json
  - mac-addr.json
  - mutex.json
  - network-traffic.json
  - process.json
  - software.json
  - url.json
  - user-account.json
  - windows-registry-key.json
  - x509-certificate.json
- - attack-pattern.json
  - campaign.json
  - course-of-action.json
  - grouping.json
  - identity.json
  - incident.json
  - indicator.json
  - infrastructure.json
  - intrusion-set.json
  - location.json
  - malware-analysis.json
  - malware.json
  - note.json
  - observed-data.json
  - opinion.json
  - report.json
  - threat-actor.json
  - tool.json
  - vulnerability.json
- - relationship.json
  - sighting.json
CONTRIBUTING.md
LICENSE
README.md
test_examples.sh

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# cti-stix2-json-schemas

*This is an [OASIS TC Open Repository](https://www.oasis-open.org/resources/open-repositories/). See the [Governance](#governance) section for more information.*

This repository contains non-normative JSON schemas and examples for STIX 2. The examples include short examples of particular objects, more complete use-case examples, and complete reports in STIX 2. The repository contains both JSON schemas and JSON STIX documents.

**NOTE:** The schemas in this repository are intended to follow the [STIX 2.1 Specification](https://www.oasis-open.org/standards#stix2.0), but some requirements of the specification cannot be enforced in JSON schema alone. As a result, these schemas are insufficient to determine whether a particular example of STIX 2.1 JSON is "valid". Additionally, though care has been taken to ensure that these schemas do not conflict with the specification, in case of conflict, the specification takes precedence.

Some of the checks the schemas do not contain:

- The 'modified' property must be later or equal to 'created'.
- Marking Definitions (both object markings and granular markings) cannot refer to themselves (no circular refs).
- IDs for custom object types must start with the name of that type.
- Granular Marking selectors must refer to properties or items actually present in the object.
- Object references in the Cyber Observable layer must be valid within the local scope.
- Custom observable objects and observable extensions must have at least one custom property.
- Values for some Cyber Observable object properties must come from official registries (eg. artifact:mime_type must be a valid IANA MIME type).
- Some Cyber Observable objects' *_ref and *_refs properties must point to specific types of objects (eg. process:image_ref must point to an object of type 'file').
- In patterns, an Observation Expression MUST NOT have more than one Qualifier of a particular type.

**NOTE:** If you need schemas for previous versions of the STIX 2 specification, see the Git branch corresponding to that version.

## Governance

This GitHub public repository ( **[https://github.com/oasis-open/cti-stix2-json-schemas](https://github.com/oasis-open/cti-stix2-json-schemas)** ) was [proposed](https://lists.oasis-open.org/archives/cti/201608/msg00050.html) and [approved](https://www.oasis-open.org/committees/ballot.php?id=2961) [[bis](https://issues.oasis-open.org/browse/TCADMIN-2424)] by the the [OASIS Cyber Threat Intelligence (CTI) TC](https://www.oasis-open.org/committees/cti/) as an [OASIS TC Open Repository](https://www.oasis-open.org/resources/open-repositories/) 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](https://github.com/oasis-open/cti-stix2-json-schemas/blob/master/CONTRIBUTING.md#governance-distinct-from-oasis-tc-process) 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](https://www.oasis-open.org/sites/www.oasis-open.org/files/BSD-3-Clause.txt). That license was selected as the declared ["Applicable License"](https://www.oasis-open.org/resources/open-repositories/licenses) when the TC Open Repository was created.

As documented in ["Public Participation Invited](https://github.com/oasis-open/cti-stix2-json-schemas/blob/master/CONTRIBUTING.md#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](https://www.oasis-open.org/policies-guidelines/open-repositories), the open source [LICENSE](https://github.com/oasis-open/cti-stix2-json-schemas/blob/master/LICENSE) designated for this particular repository, and the requirement for an [Individual Contributor License Agreement](https://www.oasis-open.org/resources/open-repositories/cla/individual-cla) that governs intellectual property.

### <a id="maintainers">Maintainers</a>

TC Open Repository [Maintainers](https://www.oasis-open.org/resources/open-repositories/maintainers-guide) are responsible for oversight of this project's community development activities, including evaluation of GitHub [pull requests](https://github.com/oasis-open/cti-stix2-json-schemas/blob/master/CONTRIBUTING.md#fork-and-pull-collaboration-model) and [preserving](https://www.oasis-open.org/policies-guidelines/open-repositories#repositoryManagement) 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](https://www.oasis-open.org/resources/open-repositories/maintainers-guide#additionalMaintainers).

**<a id="currentMaintainers">Current Maintainers of this TC Open Repository</a>**

* [Emily Ratliff](mailto:Emily.Ratliff@ibm.com); GitHub ID: [https://github.com/ejratl](https://github.com/ejratl); WWW: [IBM](http://www.ibm.com/)
 * [Rich Piazza](mailto:rpiazza@mitre.org); GitHub ID: [https://github.com/rpiazza](https://github.com/rpiazza) WWW: [MITRE](http://www.mitre.org/)
* [Alexandre Dulaunoy](mailto:alexandre.dulaunoy@circl.lu); GitHub ID: [https://github.com/adulau](https://github.com/adulau); WWW: [CIRCL](http://www.circl.lu/)
* [Christian Studer](mailto:christian.studer@circl.lu); GitHub ID: [https://github.com/chrisr3d](https://github.com/chrisr3d); WWW: [CIRCL](http://www.circl.lu/)

## <a id="aboutOpenRepos">About OASIS TC Open Repositories</a>

* [TC Open Repositories: Overview and Resources](https://www.oasis-open.org/resources/open-repositories/)
 * [Frequently Asked Questions](https://www.oasis-open.org/resources/open-repositories/faq)
 * [Open Source Licenses](https://www.oasis-open.org/resources/open-repositories/licenses)
 * [Contributor License Agreements (CLAs)](https://www.oasis-open.org/resources/open-repositories/cla)
 * [Maintainers' Guidelines and Agreement](https://www.oasis-open.org/resources/open-repositories/maintainers-guide)

## <a id="feedback">Feedback</a>

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 [repository-admin@oasis-open.org](mailto:repository-admin@oasis-open.org) and any specific CLA-related questions to [repository-cla@oasis-open.org](mailto:repository-cla@oasis-open.org).