You are here: Driver Reference > DNP3 Driver > Configuring a DNP3 Outstation > Define When the Session Keys Need to Change

Define When the Session Keys Need to Change

To maintain security, ClearSCADA changes the Session Keys whenever either a Change Interval or Change Count is reached (whichever is the shorter). ClearSCADA also changes the Session Keys after any communications failure.

Use the fields within the Session Keys section of the Security tab to specify the change criteria.

Ideally, the values that you specify in these fields should equate to half that of the values configured in the outstation itself. This should help to prevent the outstation from invalidating the Session Keys unnecessarily if an expected Session Key Change is delayed. In certain circumstances, Session Key Change delays can occur, for instance, when the system is exceptionally busy.

Whenever either change trigger is reached, ClearSCADA changes the Session Keys.

Should communications fail at any time, the current Session Keys will be invalidated. When the communications with the outstation are re-established, ClearSCADA will re-initialize the Session Keys.

Further Information

‘On Demand’ outstations: see Specify Whether the Direct Communications Connection is Always Online or only Available on Demand in the ClearSCADA Guide to Advanced Drivers.

‘Incoming Only’ and ‘Periodic’ communications: see Specify the Availability of Communications Between the Outstation and ClearSCADA in the ClearSCADA Guide to Advanced Drivers.


ClearSCADA 2015 R2