Project

General

Profile

Improvement #6546

Prevent the modification of setting parameters

Added by Michael Haecker 7 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Category:
Solved / Missunderstanding
Start date:
10/20/2023
Due date:
% Done:

100%

Estimated time:
ID:
Source:
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Standard(s):
Needs More Information:
No
Assigned TF:
61850-7-2

Description

Setting parameters (SE, SG) can be modified online using the services of the setting group control block model.
Based on ACSI services, the SGCB services cannot be blocked.

Users want to be able to prevent from unwanted modification of setting parameters.

Proposal descriptions

Create a means for a user to block/unblock the 'ConfirmEditSGValues' service.

Side note: Discuss the effect of changing the active setting group. Changing the active setting group is an operative measure. Nevertheless, it can lead to a malfunction when changing to another SG and hence activating an unappropriate setting value.

#1

Updated by Carlos Rodriguez del Castillo 6 months ago

  • Discuss in Upcoming Meeting changed from No to Yes
#2

Updated by Vladan Cvejic 6 months ago

  • Tracker changed from Bug to Improvement
  • Category set to Solved / Missunderstanding
  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • Discuss in Upcoming Meeting changed from Yes to No

Discussion and conclusion: This shall be a matter of cybersecurity and not of a core model change. Thus, if it is needed to prevent unwanted setting changes - it shall be a question of RBAC application. For example, protection role shall have rights to change settings related to protection etc.
For general offline blocking - valKind is an option.

Also available in: Atom PDF