OWASP Cornucopia project

OWASP Cornucopia is a mechanism in the form of a card game to assist software development teams Identify security requirements in Agile, conventional, and formal development processes. It is language, platform, and technology agnostic. Visit: https://cornucopia.owasp.org/

The cross-references on the Web App Edition deck relate to the following versions of other OWASP and external resources:

Standards

Maturity Models

Top 10:

Guides

Other sources:

Contributing to Development

Large binary files

Please install git-lfs to ensure you can download the output files.

Install from https://git-lfs.com/

Then pull the binaries from git lfs.


git lfs pull

Using Scripts to develop and build Cornucopia

Scripts to build the Cornucopia Card Decks

Please read README.md

Additional Utility Scripts

Please read README.md

Security Scanning

First time setup:

pip install pre-commit
pre-commit install

A Bandit pre-commit hook scans Python scripts for security issues on commit. It runs automatically via pre-commit (medium severity, high confidence).

To run manually:

pre-commit run bandit --all-files

Building and Deploying the Cornucopia website

https://cornucopia.owasp.org contains the card browser for each of the cards in the cornucopia suits together with the taxonomy and in depth explaination for each of the cards in the suits.

please read README.md

Building and Deploying the Cornucopia Game Engine: Copi

Copi (https://copi.owasp.org) is an online game engine where you can play Cornucopia and Elevation of Privilege. You can play all the editions of Cornucopia (website and mobile) as well as the Elevation of Privileges game.

please read README.md

Printing

The latest printable files are released under the pre-release. Please download final printable files from there. The docx/pdf files can be easily printed by any desktop printer, but for the best quality use the idml InDesign files. When sending the files to a printing facility you may have to supply the fonts that has been used in order to create the work. In case the printing facility doesn't have the fonts at hand you'll find the installable fonts under resources/templates/Fonts in this repository. They are both open source and free for commercial use. The fonts can also be downloaded from the web. Fivo Sans: https://www.fontsc.com/font/fivo-sans Atkinson Hyperlegible: https://brailleinstitute.org/freefont

The following fonts are used:

Leaflet: Noto Sans (Light/Regular/Italic/Medium (Italic)/SemiBoldItalic/Extra Bold)
Leaflet: Noto Sans (Thin/Light (Italic)/Italic/Medium//Extra Bold)
case
- Noto Sans Condensed Bold
- Noto Sans Condensed Extra Bold
- Noto Sans Condensed Medium
- Noto Sans ExtraCondensed Extra Bold
- Noto Sans ExtraCondensed Extra Medium
Logos:
- Noto Sans Condensed Bold
- Noto Sans Condensed Extra Bold
- Noto Sans Extra Condensed Extra Bold

Dimensions

Card decks:

The "bridge" files are (2.25 x 3.5" or 56mm x 87mm) standard playing cards. The "tarot" files are (2.75 x 4.75" or 70mm x 121 mm) standard playing cards.

Cases:

The "bridge" is 60 x 89.25 mm x 27.15 mm The "tarot" is 122.2 x 73.1 x 29.1 mm

the "tarot" box has standard dimensions used by Agile Stationary to print their Cyber Security Cornucopia Edition.

Leaflets:

The "bridge" files are 56mm x 87mm The "tarot" files are (2.75 x 4.75")

The "bridge" and "tarot" version is 16-20 page spread depending on in which language you print.

Please be aware, that the table of content for the indesign leaflet has to be adjusted for all language versions before printing except for the english version!! This is because indesign does not support auto adjusting the TOC. You may need to adjust the font size to fit either a 16 or a 20 page leaflet spread. DO NOT PRINT an 18 Page leaflet! It won't look good.

Bleed:

A standard bleed set to 3mm for all 4 sides.

Paper

Use 300gsm for both the bridge cards and the tarot cards. For the case, we would recommend folding box board with anti-scuff lamination and 100gsm uncoated stock for the leaflet. The leaflets could also be laminated, but it might make them springy.

Release process

This repository follows semver approach. Release a new version means to tag commit in master branch. Please do not use same tag twice.

To avoid common mistakes there is a script which will guide you through process and push correct tag from your machine.

To release a new patch:

make release

make release-patch

To release a new minor version:

make release-minor

To release a new major version:

make release-major

Credits

Cornucopia was originally conceived and created by Colin Watson and has since had contributions from a worldwide team of volunteers. Please see About Cornucopia for more details.

cornucopia v3.5.2