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://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=a34c9baf-48b2-44c5-a567-018dc7d32296">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>
                  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 <a href="https://docs.oasis-open.org/openc2/oc2ls/v1.0/oc2ls-v1.0.html" target="_blank">Language Specification</a> and the 
                      <a href="https://docs.oasis-open.org/openc2/oc2arch/v1.0/cs01/oc2arch-v1.0-cs01.html" target="_blank">OpenC2  Architecture</a>.
                  </li>
                  <li><em>Actuator Profiles:</em> these map the OpenC2
                      language to the capabilities associated with specific
                      cyber-defense functions. The OpenC2 TC has published an
                      OASIS Committee Specification for the 
                      <a href="https://docs.oasis-open.org/openc2/oc2slpf/v1.0/oc2slpf-v1.0.html" target="_blank">Stateless Packet Filtering AP</a>, 
                      and several more are <a href="https://github.com/orgs/oasis-tcs/repositories?language=&q=openc2-ap&type=all" target="_blank">in development</a>. 
                  </li>
                  <li><em>Transfer Specifications:</em>  these document
                      how OpenC2 messages are moved between Producers and
                      Consumers using industry-standard protocols. The OpenC2 TC has
                      published OASIS Committee Specifications for message transfer via
                      <a href="https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/transf-mqtt-v1.0.html" target="_blank">MQTT</a> and 
                      <a href="https://docs.oasis-open.org/openc2/open-impl-https/v1.1/cs01/open-impl-https-v1.1-cs01.html" target="_blank">HTTPS</a>. 
                  </li>
              </ul>
              <p>
                  OpenC2 technical artifacts (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 
                  <a href="https://github.com/orgs/oasis-tcs/repositories?language=&q=openc2&type=all" target="_blank">GitHub</a>.
              </p>
          </div>
      </div>
  </section>
</main>