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: src/assets/YAML/default/CultureAndOrganization/Process.yaml
+4-6Lines changed: 4 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -86,12 +86,9 @@ Culture and Organization:
86
86
Not defining the protection requirement of applications can lead to wrong prioritization, delayed remediation of
87
87
critical security issues, increasing the risk of exploitation and potential damage to the organization.
88
88
measure: |-
89
-
Defining the SLA to respond to findings depending on protection requirement and the corresponding handling of vulnerabilities per severity for components like applications are aligned to SLAs.
90
-
This is performed for the hole organization and doesn't need to be broken down (yet) on team/product/application.
91
-
At least quarterly.
92
-
description: |-
89
+
Defining the protection requirement.
93
90
The protection requirements for an application should consider:
94
-
- Data criticality
91
+
- Processed data criticality
95
92
- Application accessibility (internal vs. external)
96
93
- Regulatory compliance
97
94
- Other relevant factors
@@ -101,7 +98,8 @@ Culture and Organization:
101
98
resources: 1
102
99
usefulness: 3
103
100
level: 2
104
-
dependsOn: []
101
+
dependsOn:
102
+
- uuid:2a44b708-734f-4463-b0cb-86dc46344b2f # inventory of production components
0 commit comments