User authentication and authorization in SCADA systems - Step-by-Step Execution

Process Flow - User authentication and authorization

User submits credentials

↓

System verifies identity

↓

Check user rights

↓

Authorization granted?

↓

Access SCADA

↓

Log user activity

User provides credentials, system checks identity (authentication), then checks permissions (authorization) before granting access.

Execution Sample

SCADA systems

1. User inputs username and password
2. System checks credentials against database
3. If valid, system checks user role
4. If role permits, access granted
5. Else, access denied

This process verifies user identity and permissions before allowing SCADA system access.

Process Table

Step	Action	Input	Check/Condition	Result	Next Step
1	Receive credentials	username=operator, password=1234	None	Credentials received	Verify credentials
2	Verify credentials	operator/1234	Match in user database?	Yes	Check authorization
3	Check authorization	User role=operator	Role has access rights?	Yes	Grant access
4	Grant access	N/A	N/A	Access granted to SCADA system	Log activity
5	Log activity	User=operator, action=login	N/A	Login recorded	End
6	End	N/A	N/A	Process complete	N/A

💡 Process ends after logging user activity or denying access if checks fail

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
username	None	operator	operator	operator	operator	operator
password	None	1234	1234	1234	1234	1234
credentials_valid	False	False	True	True	True	True
user_role	None	None	operator	operator	operator	operator
access_granted	False	False	False	True	True	True

Key Moments - 3 Insights

Why does the system check authorization after authentication?

Authentication confirms identity (Step 2), but authorization (Step 3) checks if the user has permission to access specific SCADA functions. Both are needed to secure the system.

What happens if credentials do not match the database?

If credentials fail verification (Step 2), the process stops and access is denied. This is why 'credentials_valid' remains False and no further steps occur.

Why is user activity logged after access is granted?

Logging (Step 5) records who accessed the system and when, helping track usage and detect unauthorized actions later.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'credentials_valid' after Step 2?

A False

B None

C True

D operator

💡 Hint

Check the 'Result' column at Step 2 and variable_tracker for 'credentials_valid' after Step 2

At which step does the system decide if the user can access the SCADA system?

A Step 3

B Step 5

C Step 1

D Step 6

💡 Hint

Look at the 'Action' and 'Result' columns in the execution_table for where access is granted

If the user role did not have access rights, what would happen in the execution table?

A Access would be granted at Step 4

B Process would stop after Step 3 with access denied

C User credentials would be rechecked

D User activity would be logged before access check

💡 Hint

Refer to the flow in concept_flow and the 'Check authorization' step in execution_table

Concept Snapshot

User authentication verifies identity by checking credentials.
Authorization checks if the user has permission to access resources.
Both steps are required before granting access.
Logging user activity helps track system usage.
If authentication or authorization fails, access is denied.

Full Transcript

User authentication and authorization in SCADA systems involves first receiving user credentials like username and password. The system then verifies these credentials against a user database to confirm identity. If the credentials are valid, the system checks the user's role to determine if they have permission to access the SCADA system. If authorized, access is granted and the user's login activity is logged for security tracking. If any check fails, access is denied and the process stops. This ensures only valid and permitted users can operate the SCADA system.