KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #typescript #claude-code #codex #dsh #dsh-plugin #ai-agent #ai-agents #deepseek-harness #agent-skills #macos #cli

ws2-defenders

★ 67 Open GitHub ↗

Repository for CoSAI workstream 2, Preparing Defenders for a Changing Cybersecurity Landscape

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<!-- [**Note:** This template is provided to give you a good idea about the kind of information you should include in a README.md file as a best practice. You know your project inside-out. Write your readme file for someone who doesn't know anything about it. What do you want people to know about your project who are just coming across it for the first time? OASIS Staff are happy to collaborate with you as well.

Further README inspiration can be found [here](https://www.makeareadme.com/) and [here](https://github.com/hackergrrl/art-of-readme#readme).

You may copy and edit this template as you see fit for your project and your community. You are also welcome to use emojis, graphics or images in your README. This file should be reviewed regularly and kept up-to-date.]-->

## CoSAI Workstream 2: Preparing Defenders for a Changing Cybersecurity Landscape

This repository is for the work of the CoSAI Workstream 2, Preparing Defenders for a Changing Cybersecurity Landscape. CoSAI is an [OASIS Open Project](https://www.oasis-open.org/open-projects/) and an open ecosystem of AI and security experts from industry leading organizations dedicated to sharing best practices for secure AI deployment and collaborating on AI security research and product development. For more information on CoSAI, please visit the [CoSAI website](https://www.coalitionforsecureai.org/) and the [Open Project repository](https://github.com/cosai-oasis/oasis-open-project) which has information governance and the project charter.

### About this workstream
The goal of this workstream is to develop a defender’s framework to identify needed investments to address the security impacts of AI use by business applications, attackers, and defenders as well as mitigations techniques and best practices. The Defender’s framework aims to scale investments and mitigation strategies with the emergence of pivotal offensive cybersecurity advancements in AI models. Further information can be found [here](https://github.com/cosai-oasis/oasis-open-project/blob/main/WORKSTREAMS.md).

### Workstream Leads
* Josiah Hagen
* Vinay Bansal, Cisco

<!-- ## Badges [optional – TBD]

Using badges is optional, but they are a nice way to show some key facts and stats about your project at a glance. There are badges for all kinds of things relating to your repository, e.g. to show the license you're using, the programming language, the number of forks, or a CI badge to show build/test status. Be mindful not to use too many badges. You can use [Shields](http://shields.io/) to add some to your README. Many services also have instructions for adding a badge. Check out the README of the Open Cybersecurity Alliance project [Kestrel](https://github.com/opencybersecurityalliance/kestrel-lang) to see badges in action.

## Description -TBD

* State what problem(s) your project solves.
* Note its development status.
* List the most useful/innovative/noteworthy features.
* Note and briefly describe any key concepts (technical,  philosophical, or both) important to the user’s understanding.
* Link to any supplementary blog posts or project main pages.
* Compare/contrast your project with other, similar projects so the user knows how it is different from those projects.
* Highlight the technical concepts that your project demonstrates or supports. Keep it very brief.
* If available, include screenshots and demo videos.

## Repository Organization (What's Here?) - TBD

You can use this section to give a brief overview of what can be found in this repository, e.g. documentation, meeting minutes, or templates. A good example of this can be found in the README of the [OASIS OpenC2 TC repository](https://github.com/oasis-tcs/openc2-tc-ops/blob/main/README.md).
Please make sure to update it on a regular basis – when new files or folder are added to the repository.-->

## Contributing to this workstream

Check out our [onboarding guidance for new participants](https://github.com/cosai-oasis/oasis-open-project/blob/main/ONBOARDING.md) and please see the [CoSAI Contributing policy](./CONTRIBUTING.md) for more details.

<!-- ## Authors and Maintainers

Adds names / GitHub profile links for those who have contributed to this repository. If you have a maintainer's list, link to it here.-->

## Support
For issues or features, please use Github issues. You can also join the workstream mailing list by posting an empty email to [cosai-defenders-ws@lists.oasis-open-projects.org](mailto:cosai-defenders-ws@lists.oasis-open-projects.org). You can read the mailing list archive [here](https://lists.oasis-open-projects.org/g/cosai-defenders-ws/topics).

You can also join us on Slack via [this link](https://join.slack.com/t/cosai-op/shared_invite/zt-2rbgqtolg-GdajCyOiddYtGJ3cSdk1Jg) and introduce yourself in the #ws2-defenders channel.

## Governance and Licenses

CoSAI and the CoSAI workstream operates under the terms of the [Open Project Rules](https://www.oasis-open.org/policies-guidelines/open-projects-process), the [CoSAI Governance](https://github.com/cosai-oasis/oasis-open-project/blob/main/GOVERNANCE.md) and [Workstream Governance](https://github.com/cosai-oasis/oasis-open-project/blob/main/TSC-WS-GOVERNANCE.md), as well as the following the licenses:
* CC-BY 4.0 for documentation and data contributions; and
*  Apache License v2.0 for source code and models
  
The applicable license will be determined for each repository, as applicable, at the time of its creation.

ws2-defenders

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README