Skip to content

Commit 1ddb59e

Browse files
committed
use 5 levels and adopt levels of activities
add coaching
1 parent ec7286e commit 1ddb59e

File tree

12 files changed

+8406
-36
lines changed

12 files changed

+8406
-36
lines changed

README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,6 @@ You can download your current state from the circular headmap and mount it again
6666

6767
This approach also allows teams to perform self assessment with changes tracked in a repository.
6868

69-
7069
## Amazon EC2 Instance
7170

7271
1. In the _EC2_ sidenav select _Instances_ and click _Launch Instance_

src/assets/YAML/default/BuildAndDeployment/Build.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ Build and Deployment:
127127
time: 2
128128
resources: 2
129129
usefulness: 4
130-
level: 3
130+
level: 5
131131
implementation:
132132
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/docker-content-trust
133133
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/in-toto
@@ -151,7 +151,7 @@ Build and Deployment:
151151
time: 2
152152
resources: 2
153153
usefulness: 3
154-
level: 3
154+
level: 4
155155
implementation:
156156
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/signing-of-commits
157157
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/signing-of-commits-protection

src/assets/YAML/default/BuildAndDeployment/Deployment.yaml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Build and Deployment:
1111
time: 2
1212
resources: 1
1313
usefulness: 2
14-
level: 4
14+
level: 5
1515
implementation:
1616
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/blue-green-deploymen
1717
dependsOn:
@@ -223,7 +223,7 @@ Build and Deployment:
223223
time: 2
224224
resources: 1
225225
usefulness: 4
226-
level: 3
226+
level: 4
227227
implementation:
228228
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/docker
229229
dependsOn:
@@ -248,7 +248,7 @@ Build and Deployment:
248248
time: 1
249249
resources: 1
250250
usefulness: 2
251-
level: 3
251+
level: 4
252252
implementation:
253253
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/docker
254254
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/martin-feature-toggles

src/assets/YAML/default/CultureAndOrganization/Design.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ Culture and Organization:
151151
time: 2
152152
resources: 1
153153
usefulness: 4
154-
level: 4
154+
level: 5
155155
dependsOn:
156156
- Creation of simple abuse stories
157157
implementation:

src/assets/YAML/default/CultureAndOrganization/EducationAndGuidance.yaml

Lines changed: 21 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,30 @@ Culture and Organization:
2424
isImplemented: false
2525
evidence: ""
2626
comments: ""
27+
Security Coaching:
28+
risk: Even if security practices are understood, it doesn't mean that they get implemented.
29+
measure: By coaching teams, teams are getting a better understanding and adoptiing security practices.
30+
difficultyOfImplementation:
31+
knowledge: 4
32+
time: 2
33+
resources: 1
34+
usefulness: 3
35+
implementation:
36+
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/sammancoaching
37+
level: 3
38+
references:
39+
samm2:
40+
- G-EG-3-B
41+
iso27001-2017:
42+
- 7.1.1
43+
isImplemented: false
44+
evidence: ""
45+
comments: ""
2746
Aligning security in teams:
2847
risk: The concept of Security Champions might suggest that only he/she is responsible
2948
for security. However, everyone in the project team should be responsible
3049
for security.
31-
measure: By aligning security SME with project teams, a higher security standard
50+
measure: By aligning security Subject Matter Experts with project teams, a higher security standard
3251
can be achieved.
3352
difficultyOfImplementation:
3453
knowledge: 4
@@ -80,7 +99,7 @@ Culture and Organization:
8099
time: 2
81100
resources: 1
82101
usefulness: 3
83-
level: 3
102+
level: 5
84103
implementation: []
85104
references:
86105
samm2:

src/assets/YAML/default/CultureAndOrganization/Process.yaml

Lines changed: 1 addition & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -65,27 +65,5 @@ Culture and Organization:
6565
isImplemented: false
6666
evidence: ""
6767
comments: ""
68-
Prevention of unauthorized installation:
69-
risk: Unapproved components are used.
70-
measure: Components must be whitelisted. Regular scans on the docker infrastructure
71-
(e.g. cluster) need to be performed, to verify that only standardized base
72-
images are used.
73-
difficultyOfImplementation:
74-
knowledge: 2
75-
time: 1
76-
resources: 1
77-
usefulness: 3
78-
level: 3
79-
implementation:
80-
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/example-all-docker
81-
comment: By preventing teams from trying out new components, innovation might
82-
be hampered
83-
references:
84-
samm2: []
85-
iso27001-2017:
86-
- 12.5.1
87-
- 12.6.1
88-
isImplemented: false
89-
evidence: ""
90-
comments: ""
68+
9169
...

src/assets/YAML/default/Implementation/DevelopmentAndSourceControl.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Implementation:
1010
time: 1
1111
resources: 1
1212
usefulness: 2
13-
level: 4
13+
level: 5
1414
description: ""
1515
implementation:
1616
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/stylecop

src/assets/YAML/default/Implementation/InfrastructureHardening.yaml

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,29 @@
11
---
22
Implementation:
33
Infrastructure Hardening:
4+
Prevention of unauthorized installation:
5+
risk: Unapproved components are used.
6+
measure: Components must be whitelisted. Regular scans on the docker infrastructure
7+
(e.g. cluster) need to be performed, to verify that only standardized base
8+
images are used.
9+
difficultyOfImplementation:
10+
knowledge: 2
11+
time: 1
12+
resources: 1
13+
usefulness: 3
14+
level: 3
15+
implementation:
16+
- $ref: src/assets/YAML/default/implementations.yaml#/implementations/example-all-docker
17+
comment: By preventing teams from trying out new components, innovation might
18+
be hampered
19+
references:
20+
samm2: []
21+
iso27001-2017:
22+
- 12.5.1
23+
- 12.6.1
24+
isImplemented: false
25+
evidence: ""
26+
comments: ""
427
2FA:
528
risk: One factor authentication is more vulnerable to brute force attacks and
629
is considered less secure.

src/assets/YAML/default/InformationGathering/Monitoring.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ Information Gathering:
190190
time: 3
191191
resources: 2
192192
usefulness: 5
193-
level: 4
193+
level: 5
194194
dependsOn:
195195
- Grouping of metrics
196196
implementation: []

src/assets/YAML/default/implementations.yaml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -705,3 +705,9 @@ implementations:
705705
url: https://github.com/falcosecurity/falco
706706
description: |
707707
Falco makes it easy to consume kernel events, and enrich those events with information from Kubernetes and the rest of the cloud native stack.
708+
sammancoaching:
709+
name: sammancoaching
710+
tags: [documentation, coaching, education]
711+
url: https://sammancoaching.org/
712+
description: |
713+
Security coaches work with software development teams to help them adopt better security practices.

0 commit comments

Comments
 (0)