Cyber security professionals involved in cyber-defense technology development and integration are encouraged to use OpenC2 TC technical artifacts (e.g., the language specification and actuator profiles) when developing C2 capabilities for cyber-defense.

OpenC2 technical artifacts (AKA Work Products under development are housed in GitHub.

You can also get involved in the OASIS OpenC2 technical committee to contribute to the on-going development and evolution of the standards. OpenC2 is documented using three types of documents.

• Overarching documents: describe the broad capabilities of OpenC2 and the approach to using it. These are the Language Specification (published as an OASIS Committee Specification) and the OpenC2 Architecture (work-in-progress).
• Actuator Profiles: these map the OpenC2 language to the capabilities associated with specific cyber-defense functions. One has been published as an OASIS Committee Specification and several more are in development.
• Transfer Specifications: these document how OpenC2 messages are moved between Producers and Consumers using industry-standard protocols. One has been published as an OASIS Committee Specification and several more are in development.

When the OpenC2 TC was established, three subcommittees were created to develop the three types of documents. The TC has now consolidated its process to a combined weekly working meeting, but information about the subcommittees is available at OASIS to preserve the history:

• OpenC2 Actuator Profile Subcommittee - Defining actuator profiles, the OpenC2 message elements applicable to specific cyber defense functions.
• OpenC2 Implementation Considerations Subcommittee - Providing guidance for implementation aspects such as message transport and information assurance.
• OpenC2 Language Subcommittee - Developing, maintaining, and resolving comments to the OpenC2 language documentation.