Community and Contributing

Please don’t hesitate to contact the OWASP OT Top 10 project with your questions, comments, and ideas, either publicly by adding issues or providing commits on our github page.

Please join the OWASP OT Top 10 Slack Channel to chat. You can get a free invitation to the OWASP slack server through this website.

Until the Top 10 have stabilized, we aim to do a video conference every two weeks (typically every second and fourth monday).

OWASP OT Videocall
Monday, January 27 · 5:00 – 6:00pm
Time zone: Europe/Vienna
Google Meet joining info
Video call link: https://meet.google.com/fmu-sokc-gei
Or dial: ‪(US) +1 669-244-0206‬ PIN: ‪940 723 699‬#

How to Contribute??

We're currently discussing and selecting the potential top 10 entries and are looking for new suggestions. If you have one, please add them as new markdown file in the /docs/the-top-10/ directory and link it from within index.md's list of potential top 10.

You find the source code of the current version of the OWASP OT Top 10 in the docs/ directory within the git repository.

When you check our open issues on github, you can see that some issues are tagged with help wanted or good first issue. Choose these if you want to help out the project!

Empirical Data Contribution

The OWASP OT Top 10 are created by both discussions with experts as well as through analysis of empirical data (e.g., incident reports, vulnerability databases, etc.). We are looking for empirical data that can help us to identify the most relevant risks and vulnerabilities in the OT domain. This includes data from incident reports, vulnerability databases, and other sources that can provide insights into the security landscape of OT systems.

If you have empirical data that you would like to contribute, please contact us through email (Andreas Happe). If you are able to contribute data, please make sure that it is appropriately anonymized.

How to test your changes locally before submitting

If you can run python, you can locally run the OWASP OT Top 10 website locally. We recommend this to test your changes before pushing them to github.

To do this, we will use venv to create a local python environment to install the needed mkdocs package.

# creates and activates a new python environment in a new `venv` directory
$ python3 -m venv venv
$ source venv/bin/activate

# install the mkdocs package
$ pip install mkdocs-material

# switch into your checked-out OWASP OT Top 10 directory
$ cd owasp-ot-top10

# run the local webserver
$ mkdocs serve

# now you can point your browser to http://localhost:8000 and check
# how your changes will look like