Skip to content
Open
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .eslintrc.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
{
"root": true,
"ignorePatterns": [
"projects/**/*"
"projects/**/*",
"*.css"
],
"overrides": [
{
Expand Down
2 changes: 1 addition & 1 deletion .prettierrc.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,6 @@
"arrowParens": "avoid",
"trailingComma": "es5",
"bracketSameLine": true,
"printWidth": 80,
"printWidth": 100,
"endOfLine": "auto"
}
149 changes: 149 additions & 0 deletions INSTALL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,149 @@
# Install DSOMM
The DSOMM application is frontend only. Data is only stored in server side YAML files, and in the localStorage im the user's browser.

The application can be deployed in many ways. using a number of Docker, Amazon AWS and a standalone Angular service.

## Get the Activities

The _DSOMM activities_ are maintained in a separate GitHub repository. For the latest version, get it from:
- https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data


## Docker
1. Install [Docker](https://www.docker.com)
1. Download and run DSOMM: \
`docker pull wurstbrot/dsomm:latest` \
`docker run --rm -p 8080:8080 wurstbrot/dsomm:latest`
1. Open DSOMM on http://localhost:8080
- If you are using docker-machine instead of the native docker installation on Windows or macOs: open <http://192.168.99.100:8080> instead
If you want to override the default `generated.yaml` you can mount this file when starting the docker command.

`docker run --rm --volume $PWD/generated.yaml:/srv/assets/YAML/generated/generated.yaml -p 8080:8080 wurstbrot/dsomm`

**NB!** Note that the docker command requires an absolute path to the local file. (Hence, the use of the `$PWD` variable. On Windows, substitute `$PWD` with `%CD%`.)



## Amazon EC2 Instance

1. In the _EC2_ sidenav select _Instances_ and click _Launch Instance_
2. In _Step 1: Choose an Amazon Machine Image (AMI)_ choose an _Amazon
Linux AMI_ or _Amazon Linux 2 AMI_
3. In _Step 3: Configure Instance Details_ unfold _Advanced Details_ and
copy the script below into _User Data_
4. In _Step 6: Configure Security Group_ add a _Rule_ that opens port 80
for HTTP
5. Launch your instance
6. Browse to your instance's public DNS

```bash
#!/bin/bash
service docker start
docker run -d -p 80:8080 wurstbrot/dsomm:latest
```


## Any web server - Angular build
Since DSOMM is a frontend only application, any web server can host DSOMM.
- Clone the DSOMM repo

- **NB!** The DSOMM activities are maintained separately. Download the `generated.yaml` and put it in the required folder
```
git clone https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel.git
cd DevSecOps-MaturityModel
npm install
curl https://raw.githubusercontent.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data/main/src/assets/YAML/generated/generated.yaml -o src/assets/YAML/generated/generated.yaml
ng build
```
The files that were created in the subfolder `dist`

## Teams and Groups
To customize these teams, you can create your own [meta.yaml](src/assets/meta.yaml) file with your unique team definitions.

Assessments within the framework can be based on either a team or a specific application, which can be referred to as the context. Depending on how you define the context or teams, you may want to group them together.

Here are a couple of examples to illustrate this, in breakers the DSOMM word:
- Multiple applications (teams) can belong to a single overarching team (application).
- Multiple teams (teams) can belong to a larger department (group).

Feel free to create your own [meta.yaml](src/assets/meta.yaml) file to tailor the framework to your specific needs and mount it in your environment (e.g. kubernetes or docker).
Here is an example to start docker with customized meta.yaml:
```
# Customized meta.yaml
cp src/assets/YAML/meta.yaml .
docker run -v $(pwd)/meta.yaml:/srv/assets/YAML/meta.yaml -p 8080:8080 wurstbrot/dsomm

# Customized meta.yaml and generated.yaml
cp src/assets/YAML/meta.yaml .
cp $(pwd)/src/assets/YAML/generated/generated.yaml .
docker run -v $(pwd)/meta.yaml:/srv/assets/YAML/meta.yaml -v $(pwd)/generated.yaml:/srv/assets/YAML/generated/generated.yaml -p 8080:8080 wurstbrot/dsomm
```

In the corresponding [dimension YAMLs](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data/tree/main/src/assets/YAML/default), use:
```
[...]
teamsImplemented:
Default: false
B: true
C: true
teamsEvidence:
B: All team members completed OWASP Secure Coding Dojo training on 2025-01-11.
C: |
The pentest report from 2025 has been split into Jira tasks under
[TODO-123](https://jira.example.com/issues/TODO-123).

_2025-04-01:_ All fixes of **critical** findings are deployed to production.
```
The `|` is yaml syntax to indicate that the evidence spans multiple lines. Markdown
syntax can be used. The evidence is currently visible on the activity from the Matrix page.

# Back link

- [OWASP DevSecOps maturity model page](https://dsomm.timo-pagel.de/)
- [OWASP DevSecOps project page](https://owasp.org/www-project-devsecops-maturity-model/)
- [OWASP](https://owasp.org)

# Your help is needed to perform

* Adding a manual on how to use DSOMM
* Integration of Incident Response
* DevSecOps Toolchain Categorization
* App Sec Maturity Models Mapping
* CAMS Categorization
* Adding assessment questions

# Multi-language support
Multi-language support is not currently planned.

# Sponsors

[![Timo Pagel IT-Consulting](https://raw.githubusercontent.com/DefectDojo/Documentation/master/doc/img/timo-pagel-logo.png)](https://pagel.pro)

[![Apprio Inc](https://github.com/wurstbrot/DevSecOps-MaturityModel/raw/master-old/assets/images/Apiiro_black_logo.png)](https://apiiro.com/)

[![Heroku (hosting)](https://github.com/wurstbrot/DevSecOps-MaturityModel/raw/master/src/assets/images/sponsors/heroku.png)](https://www.heroku.com/open-source-credit-program)

# Donations

If you are using the model or you are inspired by it, want to help but don't want to create pull requests? You can donate at the [OWASP Project Wiki Page](https://owasp.org/donate/?reponame=www-project-devsecops-maturity-model&title=OWASP+Devsecops+Maturity+Model). Donations might be used for the design of logos/images/design or travels.

# License

This program is free software: you can redistribute it and/or modify it under the terms of the [GPL 3](https://www.gnu.org/licenses/) license.

The intellectual property (content in the _data_ folder) is licensed under Attribution-ShareAlike.
An example attribution by changing the content:
> This work is based on the [OWASP DevSecOps Maturity Model](https://dsomm.timo-pagel.de).

The OWASP DevSecOps Maturity Model and any contributions are Copyright © by Timo Pagel 2017-2025.


For customized DSOMM, take a look at https://github.com/wurstbrot/DevSecOps-MaturityModel-custom.

You can download your current state from the circular heatmap and mount it again via

```bash
wget https://raw.githubusercontent.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data/main/src/assets/YAML/generated/generated.yaml # or go to /circular-heatmap and download edited yaml (bottom right)
docker run -p 8080:8080 -v /tmp/generated.yaml:/srv/assets/YAML/generated/generated.yaml wurstbrot/dsomm:latest
```

59 changes: 59 additions & 0 deletions Issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
# Changing team names has no effect

## Expected outcome
* Updating the teams names and groups in `meta.yaml` should be visible in the browser after a refresh

## Actual outcome

## Steps to reproduce
1) Clone the repo \
`git clone https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel.git`

2) Install dependencies \
`cd DevSecOps-MaturityModel` \
`npm install`

3) Download the default teams setup \
`curl https://raw.githubusercontent.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data/main/src/assets/YAML/generated/generated.yaml -o src/assets/YAML/generated/generated.yaml`

4) Start the web server \
`ng server` (or maybe `npx ng server`)

5) Open *incognito mode* os a web browser and visit \
http://localhost:4200/circular-heatmap

6) Verify that the teams are 'Default', 'B' and 'C'

7) Fill in data for some of the teams
- Click on a sector in the circle (e.g. *Build* Level 1)
- Expand *Defined build process*
- Tick all three teams
- Click on another sector in the circle (e.g. *Deployment* Level 1)
- Expand *Defined deployment process*
- Tick 'Default' and 'B' only

8) Download `generated.yaml`

### Change names of teams
9) Open `src\assets\YAML\meta.yaml`
10) Edit team names in 'meta'
- Rename `Default` to `A` in `teams` and `teamGroups`
- Add `D` on `teams` and `teamGroups.GroupA`
- Add `GroupD: ['C', 'D']` under `teamGroups`
11) Update team names in 'generated'
- Rename all `Default:` to `A:` in the downloaded `generated.yaml`
- Add `D: true` on line 130 for *Defined build process*

12) Replace `src/assets/YAML/generated/generated.yaml` with the newly modified version

### Verify data in your browser
13) Refresh your browser
* The team filters are showing the new names
* But expanding the activity cards only show `B` and `C`







40 changes: 40 additions & 0 deletions TODO.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# File issue:
- UI not responsive to screen size
- Changing team names has no effect
- Default installation (no generated.yaml) does not work
- Filter illogical / not working as expected


# ToDo
- App: Alert when generated.yaml is not found
- App: Filter radio buttons: Default, no selections: meaning all selected
- App: Make radio button, and use Ctrl-Click to multiple (hold click on mobile)
- App: Fix bug, that greys out all sectors on startup
- App: Onboarding: Define teams, Setup generated.yaml (is 'generated.yaml' a good name?)

- Heatmap: TeamGroup filter: No selection means all selected
- Heatmap: TeamGroup filter: Fix removing last filter
- Heatmap: Add Reset data under settings
- Heatmap: Highlight selected sector
<use id="cursor" href="#segment-Build-Level-2" fill="red" stroke-width="5" stroke="red"></use>
- Heatmap: Alter current bright yellow hover

- Heatmap modal: Default: Close some tabs
- Heatmap modal: Store opened/closed tabs in local storage

- Mapping: Add "Sort by:"
- Mapping: Fix: Sort by ISO 2017 is DESC (and 12.2)

- Matrix: Make radio button, and use Ctrl-Click to multiple (hold click on mobile)

# Doing
- Heatmap: Fix color calculations, to base on TeamVisible
- Heatmap: Allow non-standard team names and groups

# Done
- Heatmap: Make heatmap the start page
- Heatmap: Center labels on sectors
- Heatmap: Fix calculations of heatmap dimension
- Heatmap: Toggle filters' visibility
- Heatmap: (Re)move Reset button
- Heatmap: Fix responsive layout
Loading