Skip to content

srrelitz2/casp

 
 

Repository files navigation

logo


Announcement

The next CASP event will be a 2-day Cybersecurity Automation Village in Virginia in April,2024. For more info, see Next Village and participate in the CASP mailing list.

The most recent plugfest was held at USC in June, 2023. See USC Plugfest for more details.

Test Planning

Because plugfests exercise interworking among independent implementations, it's helpful for participants to register interest in testing specific protocols with other participants. If you are considering participating, please use the CASP mailing list or GitHub issue to request to be added to the test matrix, or edit it directly and submit a GitHub pull request.


OCA CASP Sub-project

The Open Cybersecurity Alliance (OCA) Cybersecurity Automation SubProject (CASP) is composed of like-minded global cybersecurity vendors, end users, thought leaders and individuals who are interested in cybersecurity automation.

It is a forum where vendors, researchers, and software publishers can freely exchange product information, insights, and reference implementations via commonly developed code and tooling, using mutually agreed upon technologies, specifications, and procedures.

OCA is an OASIS Open Project. For more information on OCA, see https://opencybersecurityalliance.org/.

For more information on CASP, see:

For more information on the goals of this effort, see the project charter.

General questions about OASIS Open Projects may be directed to OASIS staff at project-admin@lists.oasis-open-projects.org

Other assets

In addition to this GitHub organization, this project also makes use of other assets. As a subproject of OCA, CASP operates under OCA Governance, PGB, and TSC.

Contributing

Please read CONTRIBUTING.md for details how to join the project, contribute changes to our repositories and communicate with the rest of the project contributors. Please become familiar with and follow the code of conduct.

Governance

OCA (and therefore CASP) operates under the terms of the Open Project Rules and the applicable license(s) specified in LICENSE.md. Further details can be found in GOVERNANCE.md.

CLA & Non-assert signatures required

All technical contributions must be covered by a Contributor's License Agreement. This requirement allows our work to advance through OASIS standards development stages and potentially be submitted to de jure organizations such as ISO. You will get a prompt to sign this document when you submit your first pull request to a project repository, or you can sign here. If you are contributing on behalf of your employer, you must also sign the ECLA here.

Releases

No releases published

Packages

No packages published

Languages

  • Python 100.0%