OASIS Open Command and Control (OpenC2) TC

 View Only

Request a TC GitHub version control instance be created for Open Command and Control (OpenC2)

  • 1.  Request a TC GitHub version control instance be created for Open Command and Control (OpenC2)

    Posted 05-07-2024 09:30
    Your name:
      David Lemire
    Project name:
      Open Command and Control (OpenC2)
    Project email address:
      OASIS-openc2@ConnectedCommunity.org
    GitHub repository name:
      openc2-cacao-ext
    Description
      OpenC2 is a suite of specifications to enable command and control (C2) of cyber defense systems and components. Collaborative Automated Course of Action Operations (CACAO) is a schema
    and taxonomy for cyber security playbooks. The CACAO specification describes how
    these playbooks can be created, documented, and shared in a structured and
    standardized way across organizational boundaries and technological solutions. This
    extension builds on existing CACAO v2.0 OpenC2 support to improve modularity and
    utilize the current OpenC2 Transfer Specifications for MQTT (v1.0) and HTTPS (v1.1).
    Purpose statement:
      This repository supports development of a standards track document to clarify and expand OpenC2 integration into the CACAO v2.0 specification.
    Maintainer(s):
      David Lemire, david.lemire@hii-tsd.com, GH: dlemire60; National Security Agency
    Duncan Sparrell, duncan@sfractal.com, GH: sparrell; sFractal Consulting LLC
    Michael Rosa, mjrosa@cyber.nsa.gov, GH: mjrosa, National Security Agency
    Approval:
      https://groups.oasis-open.org/higherlogic/ws/groups/a34c9baf-48b2-44c5-a567-018dc7d32296/ballots/ballot?id=3822
    Notes:
      Per notes in companion starter document ticket, a fifth approval vote could not be recorded due to technical issues with the new platform; see: https://groups.oasis-open.org/discussion/ext-oasis-open-command-and-control-openc2-tc-email-sent-to-voters-re-ballot-closed-approve-cacao-openc2-extension-as-a-new-work-product


    Your request automatically opens a ticket in the project administrator's JIRA issue tracker. To see the current queue of support tickets and find yours, click here.