-
-
Notifications
You must be signed in to change notification settings - Fork 325
Creating v4-dev branch #417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
vbakke
wants to merge
24
commits into
devsecopsmaturitymodel:v4-dev
Choose a base branch
from
vbakke:v4-dev
base: v4-dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
e48ec9f
Merge branch 'v4-base'
vbakke a363b28
Linting
vbakke d138f65
Removed obsolete files
vbakke 7788142
Install: Remove empty lines
vbakke a7fee25
Support deployments to URL subfolders
vbakke 63999ef
Dependency: Smaller panel, in center
vbakke 7945999
Dependency: Include dependents, as well as dependsOn
vbakke 6fc3242
Dependency: Add boxes based on text width
vbakke eef6df4
Dependency: Improve layout
vbakke 9934322
Linting
vbakke 3548fd2
Fixed unit test
vbakke 91c17ba
Merge pull request #1 from vbakke/v4-feat/dependancy-graph
vbakke 49b558e
Activities: Updated to v4 level 1 review
391fa0a
Dependency: Fixed nfOnChange
vbakke 1eef470
Linting
vbakke f4d77d9
Renamed variables
vbakke 8b75cef
Remove unused variable
vbakke f4e232c
Removed experimental code
vbakke 5e617ba
Updated url links
vbakke e8d7bb2
Dependency: Support dark mode
vbakke a416f31
Dependency: Swap uuids with activity names
vbakke cd6b6b6
Dependency: Added unit test for substituting dependsOn uuid
vbakke f0447d0
Dependency: Make node clickable, for navigation
vbakke c4b8d66
Updated roadmap
vbakke File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,8 @@ | ||
{ | ||
"root": true, | ||
"ignorePatterns": [ | ||
"projects/**/*" | ||
"projects/**/*", | ||
"*.css" | ||
], | ||
"overrides": [ | ||
{ | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | ||
|
||
[](https://pagel.pro) | ||
|
||
[](https://apiiro.com/) | ||
|
||
[](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 | ||
``` | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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` | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.