You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: data/BuildandDeployment.yml
+12-8Lines changed: 12 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,10 @@
2
2
sub-dimensions:
3
3
Build:
4
4
Building and testing of artifacts in virtual environments:
5
-
risk: While building and testing artifacts, third party systems, application frameworks
6
-
and 3rd party libraries are used. These might be malicious as a result of vulnerable
7
-
libraries or because they are altered during the delivery phase.
5
+
risk:
6
+
- While building and testing artifacts, third party systems, application frameworks
7
+
and 3rd party libraries are used. These might be malicious as a result of vulnerable
8
+
libraries or because they are altered during the delivery phase.
8
9
measure: Each step during within the build and testing phase is performed in a separate virtual
9
10
environments, which is destroyed afterward.
10
11
meta:
@@ -22,8 +23,9 @@ sub-dimensions:
22
23
iso27001-2017:
23
24
- 14.2.6
24
25
Defined build process:
25
-
risk: Performing builds without a defined process is error prone.
26
-
For example, as a result of incorrect security related configuration.
26
+
risk:
27
+
- Performing builds without a defined process is error prone;
28
+
for example, as a result of incorrect security related configuration.
27
29
measure: A well defined build process lowers the possibility of errors during the build
28
30
process.
29
31
evidence: The build process is defined in <a href="REPLACE-ME">REPLACE-ME Pipeline</a> in the folder <i>vars</>. Projects are using a <i>Jenkinsfile</i> to use the defined process.
@@ -149,9 +151,11 @@ sub-dimensions:
149
151
- 9.4.5
150
152
- 14.2.6
151
153
Handover of confidential parameters:
152
-
risk: Attackers who compromise a system can see confidential access information
153
-
like database credentials. Parameters are often used to set credentials, for
154
-
example by starting containers or applications. These parameters can often be
154
+
risk:
155
+
- Attackers who compromise a system can see confidential access information
156
+
like database credentials.
157
+
- Parameters are often used to set credentials, for
158
+
example by starting containers or applications; these parameters can often be
155
159
seen by any one listing running processes on the target system.
156
160
measure: By using encryption, it is harder to read credentials , e.g.
157
161
from the file system. Also, the usage of a credential management system can help
0 commit comments