|
| 1 | +Implementation: |
| 2 | + Development & Source Control: |
| 3 | + Local development linting & style checks performed: |
| 4 | + risk: |
| 5 | + - Creating and developing code that contains code smells and quality issues. |
| 6 | + measure: | |
| 7 | + Integration of quality and linting plugins with interactive development environment (IDEs). |
| 8 | + difficultyOfImplementation: |
| 9 | + knowledge: 1 |
| 10 | + time: 1 |
| 11 | + resources: 1 |
| 12 | + usefulness: 2 |
| 13 | + level: 1 |
| 14 | + md-description: | |
| 15 | + |
| 16 | + implementation: |
| 17 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/stylecop |
| 18 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/sonarqube |
| 19 | + samm2: V-ST-A-1-1 |
| 20 | + iso27001-2017: |
| 21 | + |
| 22 | + Local development security checks performed: |
| 23 | + risk: |
| 24 | + - Creating and developing code contains code smells and quality issues. |
| 25 | + measure: | |
| 26 | + Integration of quality and linting plugins with interactive development environment (IDEs). |
| 27 | + difficultyOfImplementation: |
| 28 | + knowledge: 2 |
| 29 | + time: 1 |
| 30 | + resources: 1 |
| 31 | + usefulness: 4 |
| 32 | + level: 2 |
| 33 | + md-description: | |
| 34 | + |
| 35 | + implementation: |
| 36 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/fortify-vscode-extension |
| 37 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/checkmarx-vscode-extension |
| 38 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/appscan-vscode-extension |
| 39 | + samm2: V-ST-A-1-1 |
| 40 | + iso27001-2017: |
| 41 | + - hardening is not explicitly covered by ISO 27001 - too specific |
| 42 | + - 13.1.3 |
| 43 | + |
| 44 | + Source Control Protection: |
| 45 | + risk: Unapproved code in important branches like master. |
| 46 | + measure: Enabled protections on the source code management system preventing committed directly to an important branch. |
| 47 | + difficultyOfImplementation: |
| 48 | + knowledge: 2 |
| 49 | + time: 1 |
| 50 | + resources: 2 |
| 51 | + usefulness: 4 |
| 52 | + level: 1 |
| 53 | + iso27001-2017: |
| 54 | + - peer review - four eyes principle is not explicitly required by ISO 27001 |
| 55 | + - 6.1.2 |
| 56 | + - 14.2.1 |
| 57 | + implementation: |
| 58 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/azuredevops |
| 59 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/github-policies |
| 60 | + samm2: O-EM-1-C |
| 61 | + Pre-Commit checks & validations: |
| 62 | + risk: |
| 63 | + - Using an insecure application might lead to a compromised application. This |
| 64 | + might lead to total data theft or data modification. |
| 65 | + measure: | |
| 66 | + Implement pre-commit validations to prevent secrets & other security issues being commit to source code. |
| 67 | + difficultyOfImplementation: |
| 68 | + knowledge: 4 |
| 69 | + time: 4 |
| 70 | + resources: 2 |
| 71 | + usefulness: 4 |
| 72 | + level: 2 |
| 73 | + implementation: |
| 74 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/pre-commit-microsoft |
| 75 | + - $ref: data/dimensions-subdimensions-activities/implementations.yaml#/implementations/pre-commit-synopsis |
| 76 | + samm2: V-ST-A-1-1 |
| 77 | + iso27001-2017: |
| 78 | + |
0 commit comments