Requirements for Use Control

Requirements for Use Control
Security Component
Required to Meet IEC-62443-4-2 SL 1
Details
Studio 5000 Logix Designer®
 application
May be required based on system design, threat model, and risk assessment.
Configure the controller project in the Logix Designer application to use these user access methods:
  • License-based source protection limits access to projects to only users with the required license. Users without the required license cannot open the project or import components that are protected by the license.
  • License-based execution protection allows execution of the component only on a specific controller family, or only on controllers in a specific controller family that contain the execution license.
  • Password-based protection uses a source key (password) to help protect source logic. All source keys are stored in the sk.dat file.
  • The Logix Designer application has two tag attributes that control access to tag data. The External Access attribute controls how external applications can access tags. The Constant attribute value determines if controller logic can change a tag.
For more information, see Logix 5000 Controllers Security Programming Manual, 1756-PM016 .
FactoryTalk® Security
 software
Studio 5000 Logix Designer®
 application
Yes
Configure
FactoryTalk® Security
 to define policies, user groups, and other permission sets.
  • The Logix Designer application enforces the policy based on the access policies that are provided to it by
    FactoryTalk® Security
     for the software authenticated user. Once authenticated, the Logix Designer application acts as your interface to the controller, including all protected
    CIP™
     communication to the controller, whether from Ethernet, backplane, or USB.
  • The
    FactoryTalk® Services Platform
     offers feature access control to manage user access to product features, such as controller download, project import, project create, and firmware update.
  • In
    FactoryTalk® Security
    , define which users can change controller modes and download projects to the controller.
  • Security authority binding restricts the controller to a specific
    FactoryTalk® Security
     instance. This binding reduces the attack surface for security server spoofing because the client software and the security software determine the identity of the security authority responsible for controlling access.
For more information, see Configure System Security Features User Manual, SECURE-UM001 .
Controller mode switch position
May be required based on system design, threat model, and risk assessment.
Place the mode switch in the RUN position to help prevent unauthorized remote configuration changes to the controller and restrict some communication services.
IMPORTANT:
 Do not apply a new security policy while the controller is in RUN mode. RUN mode does not help prevent updates to the security policy, and a policy change has the potential to disrupt a running control system.
Disable the controller Ethernet ports
May be required based on system design, threat model, and risk assessment.
The Ethernet ports are enabled by default. Disable the Ethernet ports if required by the system design, threat model, or risk assessment.
Disable Simple Network Management Protocol (SNMP) on the controller
May be required based on system design, threat model, and risk assessment.
SNMP is disabled by default. If SNMP has been enabled, disable SNMP if required by the system design, threat model, or risk assessment.
Disable the controller
CIP Security™
 ports
May be required based on system design, threat model, and risk assessment.
CIP Security™
 ports on the controller are enabled by default. Disable the
CIP Security™
 ports if required by the system design, threat model, or risk assessment.
Disable the controller USB port
May be required based on system design, threat model, and risk assessment.
The USB port on the controller is enabled by default. Disable the USB port if required by the system design, threat model, or risk assessment.
For more information, see Disable the Controller USB Port.
Disable the controller SD card
May be required based on system design, threat model, and risk assessment.
The SD card is enabled by default. Disable the SD card if required by the system design, threat model, or risk assessment.
For more information, see Disable the Controller SD Card.
Disable controller webpages
May be required based on system design, threat model, and risk assessment.
Controller webpages for diagnostics are read-only. With
Studio 5000 Logix Designer®
 application version 33 or later, controller webpages are disabled by default. Disable the controller webpages if required by the system design, threat model, or risk assessment.
For more information, see Disable Controller Web Pages.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal