Software Process and Device Authentication

From attackics
Jump to navigation Jump to search
Software Process and Device Authentication
Mitigation
ID M0813
NIST SP 800-53 Rev. 4 IA-9
IEC 62443-3-3:2013 SR 1.2
IEC 62443-4-2:2019 CR 1.2

Description

Require the authentication of devices and software processes where appropriate. Devices that connect remotely to other systems should require strong authentication to prevent spoofing of communications. Furthermore, software processes should also require authentication when accessing APIs.


Techniques Addressed by Mitigation

NameUse
Activate Firmware Update ModeAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Brute Force I/ODevices should authenticate all messages between master and outstation assets.
Change Operating ModeAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Data Historian CompromiseAll communication sessions with the historian should be authenticated to prevent unauthorized access.
Detect Operating ModeAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Device Restart/ShutdownAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Man in the MiddleTo protect against MITM, authentication mechanisms should not send credentials across the network in plaintext and should also implement mechanisms to prevent replay attacks (such as nonces or timestamps). Challenge-response based authentication techniques that do not directly send credentials over the network provide better protection from MITM.
Modify Alarm SettingsAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Module FirmwareAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Point & Tag IdentificationDevices should authenticate all messages between master and outstation assets.
Program DownloadAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Program UploadAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Remote ServicesAll communication sessions to remote services should be authenticated to prevent unauthorized access.
Rogue MasterDevices should authenticate all messages between master and outstation assets.
Spoof Reporting MessageDevices should authenticate all messages between master and outstation assets.
System FirmwareAuthenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.
Unauthorized Command MessageDevices should authenticate all messages between master and outstation assets.
Wireless CompromiseEnsure wireless networks require the authentication of all devices, and that all wireless devices also authenticate network infrastructure devices (i.e., mutual authentication). For defense-in-depth purposes, utilize VPNs or ensure that application-layer protocols also authenticate the system or device. Use protocols that provide strong authentication (e.g., IEEE 802.1X), and enforce basic protections, such as MAC filtering, when stronger cryptographic techniques are not available.