joinus.html

---
layout: page
title: Join Us
pageHeading: Participate in OpenC2 development and Use
permalink: /joinus.html
---

<main id="main">
  <section>
    <div class="container">
      <div>
        <p>
          Cyber security professionals involved in cyber-defense
          technology development and integration are <a
          rel="noopener noreferrer" target="_blank"
          href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=openc2">encouraged
          to use</a> OpenC2 TC technical artifacts (e.g., the
          language specification and actuator profiles) when
          developing C2 capabilities for cyber-defense.
        </p>
        <p>
          <a rel="noopener noreferrer" target="_blank"
          href="https://github.com/oasis-tcs?utf8=%E2%9C%93&q=openc2&type=&language=">OpenC2
          technical artifacts</a> (AKA <a rel="noopener
          noreferrer" target="_blank"
          href="https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dWorkProduct">Work
          Products</a> under development are housed in GitHub.
        </p>
        <p>
          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.
        </p>
        <ul>
          <li><em>Overarching documents:</em> 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).</li>
          <li><em>Actuator Profiles:</em>  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. </li>
          <li><em>Transfer Specifications:</em>  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. </li>
        </ul>
        <p>
          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:
        </p>
        <ul>
          <li><a rel="noopener noreferrer" target="_blank"
          href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=openc2-actuator">OpenC2
          Actuator Profile Subcommittee</a> - <em>Defining
          actuator profiles, the OpenC2 message elements
          applicable to specific cyber defense
          functions.</em></li>
          <li><a rel="noopener noreferrer" target="_blank"
          href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=openc2-imple">OpenC2
          Implementation Considerations Subcommittee</a> -
          <em>Providing guidance for implementation aspects such
          as message transport and information
          assurance.</em></li>
          <li><a rel="noopener noreferrer" target="_blank"
          href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=openc2-lang">OpenC2
          Language Subcommittee</a> - <em>Developing,
          maintaining, and resolving comments to the OpenC2
          language documentation.</em></li>
        </ul>
      </div>
    </div>
  </section>
</main>