Skip to content

Commit a75a137

Browse files
Update security analysis guidelines with examples (#641)
Clarify the purpose of security analysis for features and components. Signed-off-by: Chidananda Swamy R <chidananda.swamy@ltts.com>
1 parent c7d63de commit a75a137

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

process/process_areas/security_analysis/guidance/security_analysis_guideline.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -151,9 +151,9 @@ The analysis is done by as described in the flowchart :ref:`platform_security_an
151151
Examples for Security Analysis at feature level
152152
===============================================
153153

154-
future PR (https://github.com/eclipse-score/process_description/issues/409).
154+
The security analysis shall be used to analyze whether the security goals of a feature can be compromised. This could be an unauthorized tranimission of a control message between two components of feature, for example due to missing authentication or insufficient access control.
155155

156156
Examples for Security Analysis at component level
157157
=================================================
158158

159-
future PR (https://github.com/eclipse-score/process_description/issues/409).
159+
The security analysis shall be used to analyze whether the vulnerabilities within the component can be exploited. This could be unintended privilege escalation between two sub-components, allowing unauthorized access to senstive data or security-critical functions.

0 commit comments

Comments
 (0)