Scalance CST
Scalance CST
Preface
___________________
Introduction and basics 1
Configuring with the Security
___________________
Configuration Tool 2
SIMATIC NET
Creating modules and
___________________
setting network parameters 3
Industrial Ethernet Security
Security basics and application 4
___________________
Configure the firewall
Configuring additional
___________________
module properties 5
Configuration Manual
Secure communication in the
___________________
VPN via an IPsec tunnel 6
Router and firewall
___________________
redundancy 7
___________________
SOFTNET Security Client 8
Online functions -
___________________
diagnostics and logging 9
___________________
Appendix A
___________________
References B
04/2017
C79000-G8976-C286-08
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Preface
SCALANCE S V1/V2 modules are no longer supported as of SCT V5.0 and can no longer be
inserted in SCT projects. SCALANCE S V1/V2 modules from projects of older SCT versions
are simply displayed with their module properties. These properties cannot, however, be
edited. Downloading, diagnostics and firmware updates of SCALANCE S V1/V2 devices are
also not possible. All the functions described for SCALANCE S modules relate to the
firmware versions as of V3.
To retain the configuration data, SCALANCE S V1/V2 modules can be replaced in SCT with
SCALANCE S modules with a higher firmware version, see section Replacing a module
(Page 24).
This manual is valid for the following SIMATIC NET configuration tools:
Audience
This manual is intended for persons setting up the Industrial Ethernet security functions in a
network.
Security recommendations
To prevent unauthorized access, note the following security recommendations.
General
● You should make regular checks to make sure that this product meets these
recommendations and/or other internal security guidelines.
● Evaluate your plant as a whole in terms of security. Use a cell protection concept with
suitable products.
● Keep the software you are using up to date. Check regularly for security updates of the
product.
You will find information on this at http://www.siemens.com/industrialsecurity.
● Only activate protocols you require to operate your devices.
● Whenever possible, always use the variants of protocols that provide greater security
(e.g. SNMPv3, NTP (secure) etc.).
● Restrict access to the Security Configuration Tool to qualified personnel.
Passwords
● Define guidelines for the use of the software and assignment of passwords.
● Regularly update passwords and keys to increase security.
● Change default passwords for users before you use the software.
● Only use passwords with a high password strength. Avoid weak passwords for example
password1, 123456789, abcdefgh.
● Make sure that all passwords are protected and inaccessible to unauthorized personnel.
● Do not use the same password for different users and systems or after it has expired.
Trademarks
The following and possibly other names not identified by the registered trademark sign ® are
registered trademarks of Siemens AG:
C-PLUG, CP 343-1, CP 443-1, SCALANCE, SIMATIC, SOFTNET
The chapter described / the section described / the line described is only relevant for
SCALANCE S as of V4.0.
The chapter described / the section described / the line described is only relevant for
SCALANCE S.
The chapter described / the section described / the line described is relevant for SCALANCE
M only.
The chapter described / the section described / the line described is relevant for all modules
except SCALANCE M875.
The chapter described / the section described / the line described is relevant for all modules
except SCALANCE M.
The chapter described / the section described / the line described is relevant for all security
modules except SCALANCE S602.
The chapter described / the section described / the line described is relevant only for
SCALANCE S602 as of V3.1.
The chapter described / the section described / the line described is relevant for SCALANCE
S623 only.
The chapter described / the section described / the line described is relevant for SCALANCE
S627-2M only.
The chapter described / the section described / the line described is relevant for SCALANCE
S623 and SCALANCE S627-2M only.
The chapter described / the section described / the line described is relevant only for
SCALANCE S623 as of V4.0 and SCALANCE S627-2M as of V4.0.
The chapter described / the section described / the line described is only relevant for S7
CPs.
The chapter described / the section described / the line described is relevant for all security
modules except the S7 CPs.
The chapter described / the section described / the line described is only relevant for PC
CPs.
The chapter described / the section described / the line described is relevant for all security
modules except the PC CPs.
The chapter described / the section described / the line described is relevant for all S7 CPs
and PC CPs.
The chapter described / the section described / the line described is relevant for all security
modules except the CPs.
The chapter described / the section described / the line described is only relevant for CP
x43-1 Adv.
The chapter described / the section described / the line described is only relevant for CP
443-1 OPC UA.
The chapter described / the section described / the line described is relevant for all security
modules except CP 443-1 OPC UA.
The chapter described / the section described / the line described is only relevant for the
VPN device.
This symbol indicates that detailed help texts are available in the context help. You can call
this with the F1 key or using the "Help" button in the relevant dialog.
References /.../
References to other documentation are shown in slashes /.../. Based on these numbers, you
can find the title of the documentation in the references at the end of the manual.
See also
Customer Support pages (https://support.industry.siemens.com/cs/us/en/ps/15326)
Preface ................................................................................................................................................... 3
1 Introduction and basics ......................................................................................................................... 17
1.1 Important information ..............................................................................................................17
1.2 Product characteristics............................................................................................................20
1.2.1 Introduction and basics ...........................................................................................................20
1.2.2 Overview of the functions .......................................................................................................20
1.2.3 Configuration limits .................................................................................................................22
1.2.4 Rules for user names, roles and passwords ..........................................................................23
1.2.5 Replacing a module ................................................................................................................24
1.3 Using the SOFTNET Security Client.......................................................................................26
1.4 Use of SCALANCE S602 ........................................................................................................27
1.5 Use of SCALANCE S612, S623 and S627-2M ......................................................................30
1.6 Use of the DMZ interface of SCALANCE S623 and SCALANCE S627-2M...........................33
1.7 Use of the media module ports of a SCALANCE S627-2M....................................................37
1.8 Use of the CP 343-1 Advanced and CP 443-1 Advanced ......................................................38
1.9 Use of CP 1628 .......................................................................................................................41
1.10 Use of CP 443-1 OPC UA ......................................................................................................43
1.11 Configuration and administration ............................................................................................44
2 Configuring with the Security Configuration Tool ................................................................................... 45
2.1 Overview - Range of performance and how it works ..............................................................45
2.2 Installation of the Security Configuration Tool ........................................................................47
2.2.1 Supported operating systems .................................................................................................47
2.3 User interface and menu commands ......................................................................................49
2.4 Creating and managing projects .............................................................................................55
2.4.1 Security Configuration Tool (standalone variant) ...................................................................55
2.4.2 Security Configuration Tool in STEP 7 ...................................................................................56
2.4.3 Migrating STEP 7 data ............................................................................................................60
2.4.4 Overview .................................................................................................................................61
2.4.5 Specifying general object properties.......................................................................................66
2.4.6 Specifying default initialization values for a project ................................................................66
2.4.7 Consistency checks ................................................................................................................66
2.4.8 You can assign symbolic names for IP / MAC addresses. .....................................................67
2.5 Managing users ......................................................................................................................70
2.5.1 Overview of user management ...............................................................................................70
2.5.2 Create users ...........................................................................................................................72
2.5.3 Creating roles ..........................................................................................................................73
2.5.4 Managing rights ......................................................................................................................75
General
Note
Protection from unauthorized access
Make sure that the configuration computer (PC/PG) or the project are protected from
unauthorized access.
Note
Disabling the guest account
Make sure that the guest account is disabled on the configuration computer.
Note
Current date and current time of day on the security modules
When using secure communication (for example HTTPS, VPN...), make sure that the
security modules involved have the current time of day and the current date. Otherwise the
certificates used will not be evaluated as valid and the secure communication will not work.
Note
Up-to-date anti-virus software
We recommend that up-to-date anti-virus software is always installed and active on all
configuration computers.
Note
FTPS
Where the term "FTPS" is used in this documentation, FTPS in the explicit mode is meant
(PTPES).
Note
No return to standard mode possible
If you switch to the advanced mode for the current project, you cannot switch back.
Remedy for SCT Standalone: Close the project without saving and open it again.
Note
Additional security measures when using the SOFTNET Security Client
The SOFTNET Security Client provides a solution for secure communication with automation
cells via VPN. For self-protection of the PC/PG and the corresponding automation cell, it is
advisable to use additional measures such as a virus scanner and the Windows firewall.
In Windows 7, the firewall of the operating system must be enabled so that VPN tunnel
establishment works.
CP x43-1 Adv.
Note
Additional security settings
To avoid unauthorized configuration data being downloaded to the CP, you will need to
make additional security settings in the firewall of the CP (e.g. blocking S7 communication or
only allowing tunneled communication) or take external security measures.
STEP 7
Note
"Save and compile" after changes
To have the security settings adopted in the corresponding (offline) system data blocks, after
making changes, select the "Station" > "Save and Compile" menu in HW Config or "Network"
> "Save and Compile" in NetPro.
Note
Opening a station with the Security Configuration Tool open
Close the Security Configuration Tool before you open another station with the SIMATIC
Manager or NetPro.
Note
STEP 7 multiprojects in connection with security
For each multiproject in STEP 7 only one security configuration is supported.
Note
Logging off from the security project.
Logging off from the security project is achieved by closing HW Config. Closing the Security
Configuration Tool within HW Config is not adequate.
Note
This manual describes all functions. Based on the following table, note which functions are
relevant for the security module you are using.
You should also note the additional information in the titles of the sections.
DHCP server - - - x
Firewall
Local firewall rules x - x x
Global firewall rule sets x - x x
User-specific IP rule sets - - - x
IPsec
Establishment of IPsec tunnels x - x x
User management
User management x x x x
Migration of the current user x - - x
management
User authentication using a - - - x
RADIUS server
Supported protocols
SNMPv3 x x x x
HTTPS server x x - x
FTPS server x - - -
FTPS client x - - -
NTP client x x x x
NTP client (secure) x x x x
PPPoE client - - - x
DDNS client / DNS client - - - x
LLDP x x - x
MRP/HRP client - - - x
Logging
Logging system events x x x x
x Function supported
- Function not supported
Note
You will find a complete overview of the permitted configuration limits on the Internet at the
following address: (https://support.industry.siemens.com/cs/us/en/view/58217657).
Permitted characters The following characters from the ANSI X 3.4-1986 character
set are permitted:
0123456789
A...Z a...z
!#$%&()*+,-./:;<=>?@ [\]_{|}~^
Characters not allowed "'`§
Length of the user name (authenti- 1 ... 32 characters
cation method "password")
Length of the user name (authenti- 1 ... 255 characters
cation method "RADIUS")
Length of the password 8 ... 32 characters
Length of the role name 1 ... 32 characters
Maximum number of users per 128
project
Maximum number of users on one 32 + 1 administrator when creating the project
security module
Maximum number of roles per pro- 128 (122 user-defined + 6 system-defined)
ject
Maximum number of roles on one 37 (31 user-defined + 6 system-defined)
security module
Note
User names and passwords
As an important measure for increasing security, always make sure that user names and
passwords are as long as possible and include special characters, upper and lowercase
letters and numerals.
Using password policies, you can further narrow down the restrictions listed above for
passwords. How to define password policies is described in the section:
Configuring password policies (Page 80)
Password strength
When a new password is entered, its password strength is checked. The following levels are
distinguished for the password strength:
● Very weak
● Weak
● Medium
● Good
● Strong
● Very strong
Note
Checking the password strength of existing users
Check the password strength
• of users already in the project,
• of the first user created in STEP 7,
• of migrated users,
by selecting the relevant user in the "User" tab of the user management and clicking the
"Edit..." button.
Note
Replacing CPs
You will find information about replacing CPs in the relevant device manual.
x Without losses
! Possibly with losses
- The module type and the firmware version are not changed.
See also
User interface and menu commands (Page 49)
/2/ (Page 292)
Security functions
● Firewall
– IP firewall with stateful packet inspection (layer 3 and 4)
– Firewall also for Ethernet "non-IP" frames according to IEEE 802.3
(Layer 2 frames: does not apply if router mode is used);
– Bandwidth limitation
– Global firewall rule sets
– User-specific IP rule sets
All network nodes located in the internal network segment of a SCALANCE S are
protected by its firewall.
● Router mode
By operating the SCALANCE S as a router, you separate the internal network from the
external network. The internal network connected over SCALANCE S therefore becomes
a separate subnet; SCALANCE S must be addressed explicitly as a router using its IP
address.
● Protection for devices and network segments
The firewall protective function can be applied to the operation of single devices, several
devices, or entire network segments.
● No repercussions when included in flat networks (bridge mode)
This means that when a SCALANCE S602 is installed in an existing network
infrastructure, the settings of end devices do not need to be made again.
● Security module and internal node as one unit (ghost mode)
When communicating with external stations, the security module uses the IP address of
the internal node and the MAC address of the security module.
● NTP (secure)
For secure time-of-day synchronization and transmission.
● PPPoE
Point-to-Point Protocol over Ethernet (RFC 2516) for obtaining IP addresses
automatically from the provider so that the use of a separate DSL router is not necessary.
● User authentication using a RADIUS server
User names, passwords and roles of users can be stored centrally on a RADIUS server.
These users are then authenticated by a RADIUS server.
● SNMPv3
For secure transmission of network analysis information safe from eavesdropping.
Note
The internal network is considered to be secure (trustworthy).
Connect an internal network segment to the external network segments only over
SCALANCE S.
There must be no other paths connecting the internal and external network!
All-round protection - the job of SCALANCE S612, SCALANCE S623 and SCALANCE S627-2M
With a combination of different security measures such as firewall, NAT/NAPT routers and
VPN (Virtual Private Network) via IPsec tunnels, the security modules SCALANCE S612,
SCALANCE S623 and SCALANCE S627-2M protect individual devices or even entire
automation cells from:
● Data espionage
● Data manipulation
● Unwanted access
SCALANCE S allows this protection flexibly, without repercussions, protocol-independent (as
of Layer 2 according to IEEE 802.3) and without complicated handling.
SCALANCE S and SOFTNET Security Client are configured with the Security Configuration
Tool.
Figure 1-2 Network configuration with SCALANCE S612, SCALANCE S623 and SCALANCE S627-2M
Security functions
● Firewall
– IP firewall with stateful packet inspection (layer 3 and 4)
– Firewall also for Ethernet "non-IP" frames according to IEEE 802.3
(Layer 2 frames; not available if router mode is used)
– Bandwidth limitation
– Global firewall rule sets
– User-specific IP rule sets
All network nodes located in the internal network segment of a SCALANCE S are
protected by its firewall.
● Communication made secure by IPsec tunnels
SCALANCE S can be grouped together with other security modules during configuration.
IPsec tunnels are created between all security modules of a group (VPN, Virtual Private
Network). All internal nodes of these security modules can communicate securely with
each other through these tunnels.
● Protocol-independent
Tunneling also includes Ethernet frames according to IEEE 802.3 (layer 2 frames; does
not apply if router mode is used).
Both IP and non-IP packets are transferred through the IPsec tunnel.
● PPPoE
Point-to-Point Protocol over the Ethernet (RFC 2516) for obtaining IP addresses
automatically from the provider so that the use of a separate DSL router is not necessary.
● Client for dynamic DNS (DDNS client)
Dynamic Domain Name Service for the use of dynamic IP addresses when a SCALANCE
S is used as a VPN server in remote maintenance scenarios in conjunction with the
SOFTNET Security Client, SCALANCE M modules, SCALANCE S modules or other VPN
clients.
● SNMPv3
For secure transmission of network analysis information safe from eavesdropping.
● Router mode
By operating the SCALANCE S as a router, you connect the internal network with the
external network. The internal network connected by SCALANCE S therefore becomes a
separate subnet.
● Protection for devices and network segments
The firewall and VPN protective function can be applied to the operation of single
devices, several devices, or entire network segments.
● Additional DMZ interface
In a demilitarized zone (DMZ), servers can be placed for which access to other networks
(non-secure external network, secure internal network) can be controlled and restricted.
This means that the two networks can have services and data made available securely
without the two networks having direct communication between them.
● No repercussions when included in flat networks (bridge mode)
Internal network nodes can be found without configuration. This means that when a
SCALANCE S is installed in an existing network infrastructure, the end devices do not
need to be reconfigured.
The security module attempts to find internal nodes; internal nodes that cannot be found
in this way must nevertheless be configured.
● User authentication using a RADIUS server
User names, passwords and roles of users can be stored centrally on a RADIUS server.
These users are then authenticated by a RADIUS server.
● NTP (secure)
For secure time-of-day synchronization and transmission.
Note
The networks connected to the internal interface are considered as being secure
(trustworthy).
Connect an internal network segment with network segments with a different security
level (external network, DMZ network) only via SCALANCE S.
There must be no other connection paths between the internal network and a network
with a different security level.
Setting up a DMZ
With the SCALANCE S623 and the SCALANCE S627-2M, a DMZ (Demilitarized Zone) can
be set up on the additional interface. The DMZ is often used when services for an insecure
network need to be available and the secure network that supplies data for these services
needs to remain separated from the insecure network.
The DMZ, for example, can include terminal servers with installed maintenance and
diagnostic software which can be used by authorized users from the external network.
In typical DMZ applications, the user should configure the firewall rules so that (external)
access from the Internet to the server in the DMZ is possible (optionally further secured by a
VPN tunnel) but not to devices in the secure area (internal).
An example of a configuration in which the DMZ interface is used to set up a DMZ can be
found in section "4.2 SCALANCE S as firewall between external network and DMZ" of the
"SIMATIC NET Industrial Ethernet Security - Getting started" manual.
An example of a configuration in which the DMZ interface is used as the end point of a VPN
tunnel can be found in section "5.2 VPN tunnel between SCALANCE S623 and SCALANCE
S612" of the "SIMATIC NET Industrial Ethernet Security - Getting started" manual.
Security functions
● Firewall
– IP firewall with stateful packet inspection (layer 3 and 4)
– Firewall also for Ethernet "non-IP" frames according to IEEE 802.3 (layer 2)
– Bandwidth limitation
– Global firewall rule sets
All network nodes located in the internal network segment of a CP x43-1 Adv. are
protected by its firewall.
● Communication made secure by IPsec tunnels
The CP x43-1 Adv. can be grouped together with other security modules during
configuration. IPsec tunnels are created between all security modules of a VPN group. All
internal nodes of these security modules can communicate securely with each other
through these tunnels.
● Logging
To allow monitoring, events can be stored in log files that can be read out using the
configuration tool or can be sent automatically to a syslog server.
● HTTPS
For the encrypted transfer of Web pages, for example in process control.
● FTPS
For encrypted transfer of files.
● NTP (secured)
For secure time-of-day synchronization and transmission.
● SNMPv3
For secure transmission of network analysis information safe from eavesdropping.
● Protection for devices and network segments
The firewall and VPN protective function can be applied to the operation of single
devices, several devices, or entire network segments.
Note
The internal network is considered to be secure (trustworthy).
Connect an internal network segment to the external network segments only over
CP x43-1 Adv..
There must be no other paths connecting the internal and external network.
Security functions
● Firewall
– IP firewall with stateful packet inspection (layer 3 and 4)
– Firewall also for Ethernet "non-IP" frames according to IEEE 802.3 (layer 2)
– Bandwidth limitation
– Global firewall rules
● Communication made secure by IPsec tunnels
The CP 1628 can be grouped together with other security modules during configuration.
IPsec tunnels are created between all security modules of a group (VPN, Virtual Private
Network).
● Logging
To allow monitoring, events can be stored in log files that can be read out using the
configuration tool or can be sent automatically to a syslog server.
● NTP (secured)
For secure time-of-day synchronization and transmission.
● SNMPv3
For secure transmission of network analysis information safe from eavesdropping.
Further information
How to configure modules and IPsec tunnels is described in detail in the next sections of this
manual.
You will find detailed information on the dialogs and parameter settings in the online help.
You can call this with the F1 key or using the "Help" button in the relevant dialog.
Scope of performance
You use the Security Configuration Tool for the following tasks:
● Configuration of the security modules
● Configuration of SOFTNET Security Client
● Creating VPN configuration data for SCALANCE M / SCALANCE S615
● Creating VPN configuration files for VPN devices and software from third-party
manufacturers
● Test and diagnostic functions, status displays
Note
Before you install the Security Configuration Tool, make sure that you read the
"README.htm" file on the DVD. This file contains important notes and any late
modifications.
① Navigation panel:
• Global firewall rule sets
The object contains the configured global firewall rule sets. Other folders:
– Firewall IP rule sets
– Firewall MAC rule sets
• User-specific IP rule sets
• All modules
The object contains all the configured modules and SOFTNET configurations of the project.
• VPN groups
③ Details window:
The Details window contains additional information about the selected object and allows the
configuration of VPN properties for specific connections in the relevant context of a VPN group.
The Details window can be hidden and shown using the "View" menu.
④ Status bar:
The status bar displays operating states and current status messages. This includes:
• The current user and user type
• The operator view - standard mode/advanced mode
• The mode - online/offline
Toolbar
Below, you will find an overview of the icons you can select in the toolbar and their meaning.
Save the open project in the current path and under the current project name.
Download the configuration to the selected security modules or create configuration data
for SOFTNET Security Client / SCALANCE M / VPN device / NCP VPN client (Android).
Menu bar
Below, you will see an overview of the available menu commands and their meaning.
Transfer ▶… Note
When an object is selected, you can also activate
some of the functions in the shortcut menu.
To module(s)... Download the configuration to the selected security
module(s) or create configuration data for SOFTNET
Security Client / SCALANCE M / VPN devices / NCP
VPN clients (Android).
Note: Only consistent project data can be download-
ed.
For CPs: Project data can only be downloaded using
STEP 7.
To all modules... Download configuration to all security modules.
Note: Only consistent project data can be download-
ed.
Configuration status... The configuration status of the configured security
modules is shown in a list.
Transfer firmware ... Download new firmware to the selected security
module.
For S7-CPs: The firmware is loaded on the CP via
the update center of Web diagnostics.
View ▶…
Advanced mode Switch over from the standard (default) to the ad- Ctrl + E
vanced mode.
Note
If you switch to the advanced mode for the current
project, you cannot switch back.
Show Details window Show and hide additional details about the selected Ctrl + Alt + D
object.
Offline Default. Switch over to the offline configuration view. Ctrl + Shift key + D
Online Switch over to the online diagnostics view. Ctrl + D
Options ▶…
IP services... Open a dialog for service definitions for IP firewall
rules.
The menu command is only visible in advanced
mode.
MAC services... Open a dialog for service definitions for MAC firewall
rules.
The menu command is only visible in advanced
mode.
Network adapter... The SCALANCE S is assigned an IP address via the
selected network adapter.
Help ▶…
Contents... Help on the functions and parameters in the SCT. F1
About... Information on the version and revision of the SCT.
Project engineering
The Security Configuration Tool in STEP 7 is used to create security projects in which
security modules are configured that need to be created and configured in STEP 7. All
security modules of the standalone variant are also supported.
As soon as you enable the security functions for a security module in STEP 7, an SCT
project is created automatically in which the data of the security configuration is stored and
managed. All the data for the security configuration is processed internally by the SCT and
the result is returned to STEP 7.
① If you make security settings using STEP 7, SCT is called because the data for securi-
ty is maintained and managed there.
If specified connections are configured in NetPro, firewall rules are created in SCT
automatically for these after saving and compiling.
② You then make further security settings in SCT. SCT processes the data internally and
returns the result to STEP 7.
③ Actions such as "Save as" and "Compile" are performed in STEP 7. The security data
is stored as an SCT project under an automatically assigned name in a subfolder of
the STEP 7 project. The name and storage location must not be changed. Precisely
one SCT project can be created for a STEP 7 project. An SCT project created in
STEP 7 with the Security Configuration Tool cannot be opened with the Security Con-
figuration Tool in standalone mode.
④ The configured security data of the CP is downloaded to the module using STEP 7.
Which data is migrated to SCT from STEP 7 and displayed in the content area?
The following configuration data created in STEP 7 is automatically adopted by SCT but it
cannot be modified there:
● Device name
● IP address PROFINET IO
● IP address Bit
● IP address OPC UA
● Subnet mask PROFINET IO
● Subnet mask Gbit
● Subnet mask OPC UA
● MAC address PROFINET IO
● MAC address Gbit
● MAC address OPC UA
● Standard router
With specified connections configured in STEP 7, firewall rules are automatically created in
SCT that allow connection establishment. For more detailed information, refer to the
following section:
● Connection-related automatic firewall rules (Page 152).
With unspecified connections, you need to configure firewall rules that allow connection
establishment in SCT. For more detailed information, refer to the following section:
● Firewall in advanced mode (Page 136).
● Directly in SCT
You call SCT in STEP 7 using the "Edit" > "Security Configuration Tool" menu. In addition
to the settings in the tabs of the object properties, here you can create for example VPN
groups or add SCALANCE S modules. Although you can configure and download the
SCALANCE S modules in SCT, the data is not returned to STEP 7. When SCT is exited,
the modules are also not displayed in STEP 7.
Note
You will find more detailed information in the STEP 7 and SCT online help.
You will find general information on STEP 7 in /9/ (Page 294).
Action Description
Adopt as... The user is migrated to the SCT user management under a differ-
ent name. Enter the name in the "Migrated user name" column. The
migrated user is assigned an automatically generated role in SCT.
Merge If a user with the same name has already been created in the SCT
project, the two users are merged. The role of the user is expanded
by the rights selected for the migrated user.
Do not adopt The user of the security module is not migrated to the SCT user
management. Migration at a later point in time is not possible.
Note
The following data is not migrated
• Passwords of users already created in STEP 7. For all users, you should therefore select
how they will be migrated and assign a new password using the "Assign password"
button.
• The system-defined user "everybody" available in STEP 7. This user's rights are not
adopted for migrated users.
Note
The users and their roles can be adapted after migration in the user management of the
Security Configuration Tool.
See also
Time-of-day synchronization (Page 198)
Configuring the access list (Page 121)
2.4.4 Overview
General contents
Both in the standalone version of the Security Configuration Tool, as well as in the version
integrated in STEP 7, you will be prompted to assign a user name and a password when
creating a new project. The user you create here is of the type "administrator". After making
this entry, you can create the configurations in the project.
● Certificate manager
All the certificates of the project and the security modules it contains are managed in the
certificate management.
● User management
In the user management, you can manage all users of the project and their rights and the
password policies.
● Symbolic names
In a project, you can assign symbolic names in a table that stand for IP and MAC
addresses.
Module-specific settings
Most of the functions are configured in the tabs of the properties dialog that can be called up
for a selected security module with the command "Edit" > "Properties...". In the properties
dialog, the individual tabs can be arranged as required by dragging them with the mouse.
The following table contains the functional descriptions of the individual tabs.
Time-of-day synchronization X X
Here, you specify the type of synchronization for the date and
time.
For CPs: Time-of-day synchronization can only be configured in
SCT if the expanded NTP configuration was enabled in STEP 7.
Log settings - X
Here you can specify the recording and storage mode of log
events in greater detail and configure the transfer to a Syslog
server.
MRP/HRP X X
In this tab, select the parameters for connecting the security
module to MRP/HRP rings.
RADIUS X X
In this tab, assign a RADIUS server to the security module that
will authenticate users when activating user-specific IP rule sets
instead of the security module.
VPN groups specify which security modules, SOFTNET Security Clients and SCALANCE M
modules, VPN devices and NCP VPN clients (Android) communicate with each other via an
IPsec tunnel.
By assigning these network nodes to a VPN group, you can establish a VPN (Virtual Private
Network) communications tunnel.
Only modules of the same VPN group can communicate securely via tunnels, however the
modules can belong to several VPN groups at the same time.
See also
Configuring additional module properties (Page 173)
Overview
The Security Configuration Tool distinguishes between:
● Local consistency checks
● Project-wide consistency checks
The checked rules where care is required when you enter them can be found in the relevant
dialog descriptions under the keyword "Consistency check".
Note
You can only download configuration data when the entire project is consistent.
This makes it simpler and more reliable when configuring the individual services.
Symbolic names within the project are taken into account by the following functions and can
be used during their configuration:
● Firewall
● NAT/NAPT router
● Syslog
● DHCP
● NTP
See also
Consistency checks (Page 66)
DNS compliance (Page 287)
Users already created in STEP 7 can be migrated to SCT. When doing this, new passwords
have to be assigned.
You will find more detailed information in the online help.
You can call this with the F1 key or using the "Help" button in the relevant SCT dialog.
Note
Make sure that you keep your user passwords safe.
If you forget your user passwords, you can no longer access the relevant project or the
security module involved.
In this case, you need to create a new project and reset to factory defaults. You will,
however, lose the configuration.
Note
If the authentication settings are changed, the configuration must be downloaded to the
security modules again before the settings (for example, new users, password changes)
become active on the security modules.
Parameter Meaning
User name Freely selectable user name.
Authentication method • Password: Use this authentication method for users that edit and
download the SCT project and that are intended to run diagnostics
on the security module. The authentication of the user is performed
by the security module when user-specific IP rule sets are activated.
• RADIUS : The authentication of the user is performed by a
RADIUS server when user-specific IP rule sets are activated.
The password of the user is not configured in SCT when using this
authentication method but must be stored on the RADIUS server.
Only use this authentication method for users that only need to log
on to the Web page of a security module. A user with the "RADIUS"
authentication method cannot log on to SCT projects.
Password (only with the Entry of the password for the user. When it is entered, the password
"Password" authentication strength is checked. For more detailed information on password
method) strength, refer to the following section:
Rules for user names, roles and passwords (Page 23)
Repeat password (only Repeat the entered password.
with the "Password" au-
thentication method)
Comment Entry of additional comments.
Maximum time of the ses- Entry of the time after which a user logged on to the Web page for user-
sion specific IP rule sets of SCALANCE S modules is automatically logged
off. The time entered here starts after the logon and after renewing the
session on the Web page of the security module.
• Default setting: 30 minutes
• Minimum value: 5 minutes
• Maximum value: 480 minutes
Assigned role Depending on the assignment made.
System-defined roles
The following system-defined roles are predefined. Certain rights are assigned to the roles
that are the same on all modules and that the administrator can neither change nor delete.
Managing rights (Page 75)
● administrator
Default role when creating new SCT project.
Unrestricted access rights to all configuration data.
● standard
Role with restricted access rights.
● diagnostics
Default role when creating new user.
Read-only access.
● remote access
No rights except for logging on to the Web page for user-specific firewall rule sets.
● radius
Role that can be used to activate user-specific IP rule sets with authentication using a
RADIUS server.
Read-only access.
● administrator (radius)
Role that can be used to activate user-specific IP rule sets with authentication using a
RADIUS server.
Access rights to all configuration data except SNMP MIBs.
Note
For more detailed information on user-specific IP rule sets, refer to the following section:
User-specific IP rule sets (Page 149)
Note
For more detailed information on authentication using a RADIUS server, refer to the
following section:
Authentication using a RADIUS server (Page 81)
User-defined role
In addition to the system-defined roles, you can create user-defined roles. For a user-defined
role, select the configuration or module rights and specify the appropriate rights for every
security module used in the project. You assign the user-defined roles to the relevant user
manually.
Parameter Meaning
Role name Freely selectable role name.
Comment Entry of additional comments.
Maximum time of the ses- Entry of the time after which a user with the assignment role is automat-
ically logged off from the Web page for user-specific IP rule sets of
sion
SCALANCE S modules. The time entered here starts after the logon
and after renewing the session on the Web page of the security module.
• Default setting: 30 minutes
• Minimum value: 5 minutes
• Maximum value: 480 minutes
Configuration rights
Depending on the role type, the following configuration rights are available for selection for
each security project:
x Right is enabled
- Right is disabled
Module rights
The "Service" column displays the system that is influenced by the particular right.
Depending on the role type, the following module rights are available for selection for each
security project:
x Right is enabled
- Right is disabled
x Right is enabled
- Right is disabled
* To be able to use the function, the module right "Web: Access Web diagnostics and CP
file system" must be enabled as well.
** To be able to use the function, the module right "FTP: Read files from CP file system"
must be enabled as well.
*** To be able to use the function, the module right "FTP: Write files to CP file system"
must be enabled as well.
**** To use the function, the configuration right "Diagnose security" must also be enabled.
x Right is enabled
- Right is disabled
x Right is enabled
- Right is disabled
Setting module rights before and after creating the security modules
Within a user-defined role, the module rights for each security module are defined
separately. If a security module was created for which module rights will be defined within a
role before the role was added, the module rights for this security module will be set
automatically according to the selected rights template and can, if necessary, be adapted. If
a security module was added after creating a role, SCT does not set any rights. In this case,
you will need to set all module rights for the security module yourself.
You can also transfer existing module rights to another security module by copying and, if
necessary, adapting them there. To do this, select a security module in the shortcut menu in
the module rights and select the "Copy rights" or "Paste rights" menu command.
Meaning
Using the password policies, specifications can be defined that need to be taken into
account when assigning passwords to new users.
Parameter Meaning
Minimum password length Minimum number of characters that passwords are required
to contain. The corresponding check box is enabled as
default and cannot be disabled.
• Minimum value: 8 characters
• Maximum value: 32 characters
Minimum number of digits Minimum number of digits that passwords are required to
contain.
• Minimum value: 1 digit
• Maximum value: 32 digits
Minimum number of special characters Minimum number of special characters that passwords are
required to contain. A special character is any character that
is neither a letter nor digit.
• Minimum value: 1 special character
• Maximum value: 32 special characters
Number of passwords blocked for further use Number of the most recently used passwords that are not
available for use as a new password if the password is
changed.
• Minimum value: 1 password
• Maximum value: 10 passwords
At least one uppercase and lowercase character If you select this check box, passwords must contain at least
one uppercase and one lowercase letter.
2.5.6.1 Overview
Meaning
RADIUS (Remote Authentication Dial-In User Service) is a protocol for authenticating users
by servers on which user data can be stored centrally. The use of RADIUS servers can
increase the protection of user names, assigned roles and passwords.
1 Entry of the user data on the Web page of the security module
2 Authentication by RADIUS server and activation of the user-specific IP rule set
3 Access to an automation cell
The network setup shown above is simply an example. The RADIUS server can also be
located in the internal network or in the DMZ network of the security module.
For the configuration options described below, it is assumed that a RADIUS server is
configured in SCT and was assigned to the relevant security module. In addition to this, one
user or role must be configured with the "RADIUS" authentication method. For more detailed
information, refer to the following sections:
● Defining a RADIUS server (Page 83)
● Assigning a RADIUS server to a security module (Page 84)
● Create users (Page 72)
● Creating roles (Page 73)
For general information on user-specific IP rule sets, refer to the following section:
● User-specific IP rule sets (Page 149)
Configuration options
To authenticate the user using a RADIUS server, there are two configuration options
available:
● The user and the user's role are known on the security module, only the password
management for the user is performed on the RADIUS server. The user and the
password are configured on the RADIUS server.
– A user with the "RADIUS" authentication method is configured.
– The user is assigned to the user-specific IP rule set.
Result:
– When a user logs on to the Web page of the security module, the authentication query
is forwarded to the RADIUS server.
– The RADIUS server runs a password check and signals the result back to the security
module.
– If the password check is passed successfully, the user-specific IP rule set is activated.
● The role is known on the security module, user management is via the RADIUS server.
The user and the password are configured on the RADIUS server.
– A user-defined role or a system-defined role is assigned to the user-specific IP rule
set.
– In the "RADIUS" tab of the security module, the "Allow RADIUS authentication of non-
configured users" and the "Filter ID is required for authentication" check boxes are
enabled.
Result:
– When a user logs on to the Web page of the security module, the authentication and
authorization query is forwarded to the RADIUS server.
– The RADIUS server runs a password check and signals the result back to the security
module.
– Case a: If, in addition to this, the role name is configured on the RADIUS server:
The RADIUS server returns the role name assigned to the user to the security module.
– Case b: If the role name is not configured on the RADIUS server:
The security module assigns the user the system-defined role "radius".
– If the password check is passed successfully, the user-specific IP rule set is activated.
Meaning
Before authentication by a RADIUS server is possible, this first needs to be stored in the
SCT project. Following this, you assign the defined RADIUS server to the security module for
which the RADIUS server will handle user authentication.
Procedure
1. Select the "Options" > "Configuration of the RADIUS server..." menu command.
2. Click the "Add..." button.
3. Enter the required parameters according to the following table.
Parameter Meaning
Name Freely selectable name for the RADIUS server.
IP address / FQDN IP address or FQDN of the RADIUS server.
Port UDP port via which the RADIUS server can be
reached. As default, authentication data is re-
ceived at port 1812.
Shared secret Entry of the password that will be used when
transferring the logon data between the
RADIUS server and security modules for en-
cryption.
The following characters from the ANSI X 3.4-
1986 character set are permitted:
0123456789
A...Z a...z
!#$%&()"*'+`,-./:;<=>?@ [\]_{|}~^
Length of the shared secret: 1 ... 31 characters
Parameter Meaning
Repeat shared secret Confirmation of the password
Authentication method Display of the method used to check the user
data. Only the "PAP" method (Password Au-
thentication Protocol) is supported.
Comment Entry of freely selectable, optional comments.
Result
You have defined a RADIUS server and can now assign this to the required security
modules.
Requirement
You have defined a RADIUS server.
Procedure
1. Select the security module to which you want to assign a RADIUS server.
2. Select the "Edit" > "Properties..." menu command.
3. Select the "RADIUS" tab.
4. Select the "Enable RADIUS authentication" check box.
Note
Changing the method of authentication with the Web server on the security module
If RADIUS authentication is enabled on the security module, the method for
authentication with the Web server is changed from "Digest Access Authentication" to
"Basic Access Authentication".
5. In the "RADIUS timeout" input box, enter the maximum time in seconds that the security
module will wait for a response from the RADIUS server.
6. In the "RADIUS retries" input box, enter the number of connection establishment attempts
with the RADIUS server.
7. Select the "Allow RADIUS authentication of non-configured users" check box if the user-
specific IP rule to be activated was assigned a role instead of a user.
8. Select the "Filter ID is required for authentication" check box if the assigned role is a user-
defined role.
See also
Create users (Page 72)
2.6.1 Overview
Note
Downloading the project
After replacing or renewing certificates, the project must be downloaded to the relevant
security module.
After replacing or renewing CA certificates, the project must be downloaded to all security
modules.
Note
Current date and current time of day on the security modules
When using secure communication (for example HTTPS, VPN...), make sure that the
security modules involved have the current time of day and the current date. Otherwise the
certificates used will not be evaluated as valid and the secure communication will not work.
Button Description
Import... / Export... Import / export of device certificates or CA certificates that were
not created in SCT. The certificates are transferred to the security
module. The following formats are permitted:
*.pem
*.crt
*.p12
*.der
*.cer
Note
• Users with the system-defined "diagnostics" role must not use
the export function.
Display... Opens the certificate dialog of Windows where you will see an
overview of all certificate data.
The imported third-party certificate is transferred to all the CPs managed in the SCT project.
The security module can then identify itself with this certificate, for example when accessing
an FTPS server. The SCT configuration itself does not use the imported certificate.
Display of the certification authorities required for verification of external services such as
providers of dyn. DNS by the security modules.
Meaning
In this dialog, you renew CA certificates and device certificates.
Parameter Options
Signing • Self-signed
• Signed by a certification authority: Only certification authorities located in the certificate
memory of the SCT project can be selected.
Applicant Depending on the certificate to be renewed, enter the following values for the applicant:
• CA certificate of the project: [name of the CA certificate]
• CA certificate of VPN group [name of the CA certificate]
• SSL certificate for S7 CP [name of the security module]
• SSL certificate for PC CP [name of the security module]
• SSL certificate for SCALANCE S, SCALANCE M and SOFTNET Security Client [name
of the security module]
• OPC UA client/server certificate of the module: [name of the security module]
• VPN group certificate of a security module: [name of the VPN group cerrtificate]
Valid from / to Validity period of the certificate. Validity data after 2037 is not supported.
Alternative applicant name Depending on the certificate to be renewed, enter the following values for the alternative
applicant name:
• SSL certificate for S7 CP:
For CP x43-1 Adv.: IP:[IP address of the gigabit interface],IP:[IP address of the
PROFINET interface]
Meaning
In the dialog, replace the existing CA certificate of the project or CA certificate of a VPN
group with a new one.
Further information
You will find detailed information on the dialogs and parameter settings in the online help.
You can call this with the F1 key or using the "Help" button in the relevant SCT dialog.
Note
Performance features and device types
Note which functions the device type you are using supports.
See also
Online functions - diagnostics and logging (Page 273)
Parameter Meaning
Product type Product type used when a new module is created.
SCALANCE S
SCALANCE M
SOFTNET Configuration (SOFTNET Security Client, VPN de-
vice, NCP VPN client)
Parameter Meaning
Module Depending on the selected product type, you can select the
module type here that will be used when you create a new mod-
ule.
Select the option "NCP VPN client for Android" to insert a VPN
client device as proxy for a device with NCP Secure VPN Client
for Android software installed.
Select the "VPN device" option to insert a VPN client device as
proxy for a device from another manufacturer.
Select the option "SCALANCE M-800" to insert a SCALANCE
M-800 configuration that can also be used for SCALANCE S615.
Note
The checked out configuration file simply provides help on the
configuration of the VPN connection, but is no guarantee for
compatibility with products of other manufacturers.
Firmware release You can specify the firmware/software versions here for the
SCALANCE S modules and the SOFTNET Security Client.
Name of the module Freely selectable name for the module.
MAC address Entry of the MAC address of the module.
IP address (ext.) IP address for the external interface.
The IP address consists of four decimal numbers with the range
from 0 to 255, each number separated by a period, example:
141.80.0.16
Subnet mask (ext.) Range of values for subnet mask. Is proposed according to the
IP address entered.
The subnet mask consists of four decimal numbers with the
range from 0 to 255, each number separated by a period; exam-
ple: 255.255.0.0
Interface routing external/internal Selecting the mode for the security module. The following
modes are available for SCALANCE S:
• Bridge mode
• Routing mode
When selecting routing mode, you need to configure an IP ad-
dress and a subnet mask for the internal interface of the security
module.
IP address (int.) IP address for the internal interface.
Only needs to be specified when The IP address consists of four decimal numbers with the range
routing mode is enabled from 0 to 255, each number separated by a period; example:
141.90.10.10
Parameter Meaning
Subnet mask (int.) Range of values for subnet mask. The subnet mask is proposed
Only needs to be specified when according to the entered IP address.
routing mode is enabled The subnet mask consists of four decimal numbers with the
range from 0 to 255, each number separated by a period; exam-
ple: 255.255.0.0
Save selection If you enable this function, the currently set configuration is
adopted in the default initialization values. When you insert new
modules the "Selection of a module or software configuration"
dialog is no longer opened and a module is inserted in the pro-
ject according to the settings made.
To cancel this function again and to select a different module
type, you will need to disable this function in the following menu
path:
"Project" > "Properties" > "Default Initialization values"
Note
Additional settings
You make further interface settings in the "Interfaces" tab of the module properties. For
information on this, refer to section:
• Configuring interfaces (Page 96)
See also
Parameters in the content area (Page 94)
Range of values for IP address, subnet mask and address of the gateway (Page 287)
MAC address (Page 288)
For the CPs, the following addresses from STEP 7 are displayed:
If the IP address has been configured in STEP 7 so that it is assigned dynamically, this is
shown in SCT as follows depending on the settings:
Security mod- Interface MAC address of Port of Port type MAC address of the port*
ule the interface* the inter-
face
SCALANCE External MAC address (see P1 Built-in RJ-45 jack MAC address + 2
S602 / S612 / labeling) (copper)
S613 Internal MAC address + 1 P2 Built-in RJ-45 jack MAC address + 3
(copper)
SCALANCE External MAC address (see P1 Built-in RJ-45 jack MAC address + 3
S623 labeling) (copper)
Internal MAC address + 1 P2 Built-in RJ-45 jack MAC address + 4
(copper)
DMZ MAC address + 2 P3 Built-in RJ-45 jack MAC address + 5
(copper)
SCALANCE External MAC address (see P1 Built-in RJ-45 jack MAC address + 3
S627-2M labeling) (copper)
P4 Media module port MAC address + 4
(copper/FOC)
P5 Media module port MAC address + 5
(copper/FOC)
Internal MAC address + 1 P2 Built-in RJ-45 jack MAC address + 6
(copper)
P6 Media module port MAC address + 7
(copper/FOC)
P7 Media module port MAC address + 8
(copper/FOC)
DMZ MAC address + 2 P3 Built-in RJ-45 jack MAC address + 9
(copper)
* When operating in bridge mode, the printed MAC address is valid both on the external and
on the internal interface.
The MAC addresses of the interfaces are used for all services except LLDP.
The MAC addresses of the ports are used for topology discovery with LLDP (only for
modules in routing mode).
Note
The Ethernet interfaces must not be confused when connecting to the communications
network:
• X1 interface - external
Red marking = unprotected network area;
• Interface X2 - internal
Green marking = network protected by SCALANCE S;
• Interface X3 - DMZ (universal network interface)
Yellow marking = unprotected network area or network area protected by SCALANCE S.
If the interfaces are swapped over, the device loses its protective function.
Static IP address x x x
WAN access with DSL - x x
router
WAN access with DSL - x x
modem (PPPoE, dy- (when not on yellow (when not on red inter-
namic IP address from interface) face)
ISP)
Bridge mode x -
Routing mode x x x
Ghost mode - x -
DHCP server x - x
Endpoint of a VPN - x x
tunnel connection (with
DSL modem and DSL
router)
MRP/HRP client (in x x -
routing mode, ring ports
on the media modules)
x is supported
- is not supported
Duplex mode
One of the following two duplex modes can be selected for a port:
● Half duplex: At any one time, the security module can either receive or send data.
● Full duplex: At any one time, the security module can receive or send data at the same
time.
Note
Duplex method and transmission speed with optical ports
For ports with the port type "optical", the port mode is fixed by the media module used or by
the SFP transceiver used and cannot be adapted.
3.2.2 Interfaces
Bridge mode For operation in flat networks. External and internal interface are
in the same IP subnet.
For S623 / S627-2M: External and internal interface are in the
same IP subnet, the DMZ interface is in a different IP subnet or
is deactivated.
Routing mode All interfaces are in different IP subnets.
Note
If you have enabled the routing mode for the SCALANCE S
module, no MAC firewall rules can be defined.
Note
External interface and DMZ interface (only SCALANCE S623/S627-2M) as Internet access
The simultaneous operation of PPPoE on the external interface and on the DMZ interface
(dual ISP) is not possible.
Note
A configured standard router is not taken into account when using PPPoE. This is assigned
dynamically to the module by the ISP.
Note
No network components between SCALANCE S and DSL modem
If the interface of a SCALANCE S module is operated using PPPoE, there must be no other
network components between this interface and the connected DSL modem otherwise the
dial-in data of the Internet Service Provider may be transferred unencrypted over this link.
When using the "CHAP" authentication protocol, the data is transferred encrypted.
Port settings
Column Meaning
Port ID Automatically assigned ID for the port of the interface.
Port type Physical characteristic of the port (copper/fiber)
Port mode Autonegotiation The transmission speed and the duplex method are negoti-
ated automatically between IEEE 802.3-compliant ports.
Note
A transmission speed of 1000 Mbps and the autocrossing
function are supported only if autonegotiation is selected.
10 Mbps, half and full duplex Transmission speed of 10 Mbps
100 Mbps, half and full duplex Transmission speed of 100 Mbps
Long Distance Signaling (LDS) The transmission speed and the duplex method are negoti-
ated automatically between BroadR-Reach-compliant ports.
Off (only external port or DMZ port with The port is disabled.
SCALANCE S623 and SCALANCE S627-
2M)
Note
Ports of media modules using fiber-optic cables as the transmission medium always use full duplex and
operate at the maximum transmission speed. This means that the port mode of the ports of optical me-
dia modules cannot be configured.
RxTx LLDP frames can be sent For more detailed infor-
and received. mation on LLDP, refer to the
LLDP mode (in Off Receive LLDP frames following section:
routing mode) LLDP (Page 107)
Display indicating whether the media module ports of the interface are connected to an MRP ring. If this
is the case, the character strings "RingportOne" and "RingportTwo" are displayed in the table rows of
MRP port (in the media module ports. For the ports with the port ID "X1 P1" and "X2 P1", the character string "None"
routing mode for is displayed as default since these cannot be involved in an MRP ring.
the media mod- You will find general information on media redundancy with MRP in the following section:
ule ports of the Media redundancy with MRP or HRP (Page 107)
external and You will find information on configuring MRP for the security module in the following section:
internal inter- Configuring MRP/HRP for the security module (Page 108)
face)
Display indicating whether the media module ports of the interface are connected to an HRP ring. If this
is the case, the character strings "RingportOne" and "RingportTwo" are displayed in the table rows of
HRP port (in the media module ports. For the ports with the port ID "X1 P1" and "X2 P1", the character string "None"
routing mode for is displayed as default since these cannot be involved in an HRP ring.
the media mod- You will find general information on media redundancy with HRP in the following section:
ule ports of the Media redundancy with MRP or HRP (Page 107)
external and You will find information on configuring HRP for the security module in the following section:
internal inter- Configuring MRP/HRP for the security module (Page 108)
face)
Comment Freely selectable comment
See also
Special features of the ghost mode (Page 110)
Overview of the connector options (Page 96)
Configuration data for SCALANCE M modules (Page 235)
Meaning
In this tab, you make settings related to the Internet Service Provider (ISP) if a connection
using PPPoE is set for one of the interfaces of the security module.
Function Description
User name Enter the name for logging on with the ISP account.
Password Enter the password for logging on with the ISP account.
Repeat password Enter the password for logging on with the ISP account again.
Authentication Select none or one of the following authentication protocols:
• PAP (Password Authentication Protocol)
• CHAP (Challenge Handshake Authentication Protocol)
Note
Both communications partners have to use the same authentica-
tion method otherwise no connection can be established.
Permitted characters The following characters from the ANSI X 3.4-1986 character set
are permitted:
0123456789
A...Z a...z
!#$%&()"*'+`,-./:;<=>?@ [\]_{|}~^
Length of the user name 1 to 255 characters
Length of the password 1 to 31 characters
Function Description
Permanent connection Permanent Internet connection. After the connection has been
terminated by the provider, the connection is automatically re-
stored even if there are currently no packets to be sent.
On-demand connection The Internet connection is established automatically if packets
need to be sent to the Internet.
In this setting, delays in the sending of packets are possible.
Forced disconnection (only with The provider terminates the Internet connection automatically
the "Permanent connection" set- after a certain period. If you enter a time of day in the "Forced
ting) disconnection" box, the security module terminates the Internet
connection itself at this time. This allows disconnection of the
Internet connection by the provider to be delayed under certain
circumstances. A self-initiated forced disconnection is only pos-
sible with an existing permanent connection. Permitted entries:
00:00 ... 23:59
Maximum idle time (only with the If no packets are sent during a certain time, the Internet connec-
setting "on-demand connection") tion is automatically terminated. In the "Maximum idle time" box,
enter the time in seconds after which the connection will be ter-
minated. Permitted values: 10 ... 3600.
Meaning
With dynamic DNS, you can access a constantly changing IP address with a permanently
defined name (FQDN). This is necessary, for example, if you want to access a server that
can be reached via a public, IP address that changes.
How it works
The security module signals the current WAN IP address via which the security module can
be reached to a provider for dynamic DNS (for example DynDNS.org, no-ip.com). The
provider makes sure that DNS queries sent to the FQDN of the security module are replied
to with the current WAN IP address of the security module.
Dynamic DNS is permitted at the following interfaces:
● External interface
● DMZ interface
Option Meaning
Obtain DNS server address automatically The address of the DNS server can be obtained
automatically using PPPoE if the security mod-
ule is connected to the Internet via a DSL mo-
dem. Can only be set for the external interface
and the DMZ interface.
Use the following DNS server address: Enter the address of the preferred and of the
alternative DNS server manually.
3. Activate the "Activate service" check box in the "Primary dynamic DNS service" area and
make the following settings:
Setting Meaning
Provider Choose the provider with which you have set up
an account for dynamic DNS.
User account with the provider Enter the user name that you specified when
you created the account.
Password with the provider Enter the password that you specified when you
created the account.
FQDN Enter the host name (e.g. mysecuritydevice)
and the domain name (e.g. dyndns.org) that is
registered with the provider separated by a
period. If an FQDN is also entered in the "VPN"
tab, both must match.
Monitor IP address change on DSL router If the security module is connected to the Inter-
net via a DSL router, enabling this function
activates the function of the check IP service.
The security module periodically sends queries
to determine the current IP address of the DSL
router and to detect an IP address change on
the DSL router. The IP address specified in this
way is sent to the provider with each change ID.
Period Specify the interval at which the Check IP ser-
vice is called. Permitted values: 10 … 1440
minutes
4. In case the primary provider fails, create a second provider in the "Secondary dynamic
DNS service" tab (optional setting).
Setting Meaning
Provider update URL Enter the URL you received from your provider. The placeholder
texts <FQDN> and <CurrentWanIP> need to be placed at the
correct positions in the URL.
Check IP service URL Enter the URL you received from your provider.
Ignore errors when checking the To ensure that the authentication data is protected, the certifi-
server certificate cate of the update server is normally checked. If the certificate
check fails, the HTTP connection is terminated and the account
data is not transferred. If you select the check box, the function
is disabled, for example if the server certificate of the dynamic
DNS service is invalid (for example expired). It is advisable not
to ignore the check and not to select the check box.
3.2.5 LLDP
Meaning
LLDP (Link Layer Discovery Protocol) is a protocol used to discover network topologies. A
device capable of LLDP can send information about itself to neighboring devices at regular
intervals and at the same time receive information from neighboring devices. The received
information is stored on every device with LLDP capability in an LLDP MIB file. Network
management systems can access these LLDP MIB files using SNMP and therefore recreate
the existing network topology.
Configurable parameters
The degree of activity of the security module in terms of LLDP can be configured in the
"Interfaces" tab of the module properties as follows:
● Send and receive LLDP frames (default setting "RxTx")
● Receive LLDP frames ("Off")
Meaning
The term "media redundancy" groups together various methods for increasing availability in
Industrial Ethernet networks in which devices can be reached over different paths. This
might be achieved by meshing networks, arranging parallel transmission paths or by closing
a linear bus topology to form a ring.
manager due to an interruption, the redundancy manager switches through its two ring ports
and informs the redundancy clients of the change immediately.
The two media redundancy methods MRP and HRP operate according to the same
functional principle. They differ in the time the SCALANCE X switches need to switch
through their ring ports as redundancy manager.
● MRP: 200 ms
● HRP: 300 ms
* The simultaneous connection of the security module to an internal and an external ring is
possible only if at least one of the interfaces is connected as an MRP client.
With two lower-layer rings per SCALANCE S module, layer 3 communication is possible
between the rings.
Requirements
● The security module is in routing mode.
● Media modules are configured for the interfaces to be connected to rings.
Configurable parameters
Result
You have connected the security module to the MRP/HRP ring via the selected interface.
The media module ports of which interface(s) are connected to the MRP/HRP ring is also
shown in the "Interfaces" tab of the module properties.
See also
Consistency checks (Page 66)
Meaning
In ghost mode, the security module has no IP address of its own, neither on the internal nor
on the external interface. Instead, the security module obtains the IP address for its external
interface during runtime from a node connected to the internal interface of the security
module whose IP address parameters can be unknown at the time of configuration. It is
possible to change an IP address of the internal node and a corresponding IP address at the
external interface. Since the internal node is identified based on its MAC address, IP address
changes are made only for the learnt MAC address. No IP address is configured or obtained
on the internal interface of the security module.
As regards the MAC addresses, the security module replaces the MAC address of the
internal node with the MAC address of the security module in all outgoing packets on the
external interface (responses from the internal node).
Since no DNS servers can be configured in ghost mode, no FQDN resolution is possible.
Table 3- 6 Port assignments for incoming connections (from external to security module)
Table 3- 7 Port assignments for outgoing connections (from security module to external)
Configuration limits
A maximum of one internal node is recognized by the security module. If several internal
nodes exist, the security module reacts as follows:
● The first device the security module recognizes in the internal network obtains access to
the external network segment if the firewall is suitably configured.
● The data traffic of any additional nodes in the internal network is blocked in the outgoing
direction at level 2 (MAC layer) based on the sender address.
Meaning
The firewall functionality of the security modules is intended to protect networks and stations
from third-party influence and interference. This means that only certain, previously specified
communications relations are permitted. Disallowed frames are discarded by the firewall
without a reply being sent.
To filter the data traffic, IP addresses, IP subnets, port numbers or MAC addresses can be
used.
The firewall functionality can be configured for the following protocol levels:
● IP firewall with stateful packet inspection (layer 3 and 4)
● Firewall also for Ethernet "non-IP" frames according to IEEE 802.3 (layer 2)
The firewall can be used for encrypted (IPsec tunnel) and unencrypted data traffic.
Firewall rules
Firewall rules describe which packets in which direction are permitted or forbidden. IP rules
affect all IP packets of layer 3 or higher. MAC rules only affect frames lower than layer 3.
With connections configured in STEP 7, firewall rules are automatically created in SCT that
enable the communications partner. The connection establishment directions are taken into
account.
The rules are only visible in advanced mode and can only be modified there.
Project engineering
A distinction must be made between the two operating views:
● In standard mode, simple, predefined rules are used. You can only enable service-
specific rules. The enabled services are permitted for all nodes and full access is allowed
in the specified direction.
● In advanced mode, you can make detailed firewall settings. You can allow individual
services for a single node or all services for the node for access to the station or network.
The following firewall rules or rule sets must be distinguished in advanced mode:
– Local firewall rules are assigned to one security module. They are configured in the
properties dialog of the security modules.
– Global firewall rule sets can be assigned to individual or several security modules at
the same time. They are displayed in the navigation panel in advanced mode of the
Security Configuration Tool and configured globally.
– User-specific IP rule sets can be assigned to individual or several security modules at
the same time. They are displayed in the navigation panel in advanced mode of the
Security Configuration Tool and configured globally.
SCALANCE S V4 (RADIUS): User-specific IP rule sets can be assigned individual or
multiple users as well as individual or multiple roles.
With the aid of service definitions, you can also define firewall rules clearly in a compact
form. Service definitions can be used in all the rule types listed above.
Note
Firewall of SCALANCE S627-2M
The media module ports of the SCALANCE S627-2M are connected to the built-in port of the
particular interface via a switch chip. For this reason, there is no firewall functionality (layer 2
/ layer 3) between the ports of the external interface themselves nor between the ports of the
internal interface themselves.
Note
No return to standard mode possible
If you switch to the advanced mode for the current project, you cannot switch back.
Figure 4-1 Default setting for the IP packet filter CP x43-1 Adv.
Figure 4-2 Default setting for the MAC packet filter CP x43-1 Adv.
Note
No communication bypasses the VPN tunnel
Communication between the VPN endpoints is also prevented from bypassing the tunnel for
all VPN partners known in the project. The behavior cannot be modified by creating suitable
firewall rules in advanced mode.
Note
Data traffic via configured connections is not logged.
Note
Modified behavior following migration
• Following migration, the access protection is effective only on the external interface. To
make the access protection effective on the internal interface as well, configure suitable
firewall rules in the advanced mode of SCT.
• The security module also responds to ARP queries from IP addresses that have not been
enabled (layer 2).
• If you migrate an IP access control list without entries, the firewall is enabled and there is
no longer any access to the CP from external. To make the CP available, configure
suitable firewall rules in SCT.
STEP 7 menu command: "IP access protection" > "Start of firewall configuration", "Run…"
button.
Table 4- 3 Information
Parameter Meaning
IP address Permitted IP address or IP address range.
Rights Depending on the assignment made. Rights that are enabled for the IP
address.
Comment Entry of additional comments.
Logging If you select the check box, the rules are logged in the packet filter log.
Enable advanced mode If you select the check box, the entries in the following firewall rules are
converted.
Table 4- 4 Buttons
Box Description
IP address (or start of the IP range) Enter the IP address or the start value of an IP address
range.
End of the IP range (optional) Enter the end value of an IP address range.
Box Description
Comment Entry of an additional comment, for example to de-
scribe the communication partner or the address
range.
This IP address is authorized for the follow- Access to station (A = access): Communications part-
ing accesses. ners with addresses in the specified range have ac-
cess to the station (CP / CPU) assigned to the CP.
This access permission is set implicitly for IP address-
es you have specified in the connection configuration
(does not apply to specified connections).
IP routing to another subnet (R = routing): Communica-
tions partners with addresses in the specified range
have access to other subnets connected to CP. This
access permission is not set automatically for IP ad-
dresses you have specified in the connection configu-
ration. Where necessary, this access permission must
be set here explicitly.
● There is a check to determine whether individual addresses are included more than once;
here, the following is detected: Multiple single entries; overlapping ranges.
● IP addresses specified individually can also occur within a range; the access permissions
assigned in total to an IP address then apply.
● The system does not check whether invalid addresses are included in a range (for
example, subnet broadcast addresses could be specified here although they cannot
occur as the IP address of a sender).
4.1.2 CP 1628
① All frames from the NDIS and IE (Industrial Ethernet) interface to external are allowed.
② All frames from external are blocked.
③ All frames of the following type from external to the security module and vice versa are
allowed:
• ESP protocol (encryption)
• IKE (protocol for establishing the IPsec tunnel)
• NAT Traversal (protocol for establishing the IPsec tunnel)
④ IP communication over an IPsec tunnel is allowed.
⑤ Frames of the type Syslog in the direction of external are allowed by the security module.
Figure 4-4 Default setting for the MAC packet filter CP 1628
Note
No communication bypasses the VPN tunnel
Communication between the VPN endpoints is also prevented from bypassing the tunnel for
all VPN partners known in the project. The behavior cannot be modified by creating suitable
firewall rules in advanced mode.
Note
Data traffic via configured connections is not logged.
Figure 4-5 Default setting for the IP packet filter SCALANCE S602/S612
Figure 4-6 Default setting for the MAC packet filter SCALANCE S602/612
① All frame types from internal to external are blocked except for the following frame types.
• ARP frames
② All frames from internal to the security module are allowed.
③ All frames from external to internal are blocked except for the following frame types.
• ARP frames with bandwidth limitation
④ Frames of the following type from external to the security module are allowed:
• ARP with bandwidth limitation
• PROFINET DCP with bandwidth limitation
• In routing mode: LLDP frames (Ethertype 0x88CC)
⑤ In bridge mode: MAC protocols sent through an IPsec tunnel are permitted.
⑥ Frames of the following type from the security module to external are allowed:
• PROFINET
• In routing mode: LLDP frames (Ethertype 0x88CC)
⑦ Multicast and broadcast frames of the following type from external to the security module
are allowed:
• PROFINET with bandwidth limitation
Note
Automatic enabling of Ethertypes
If PPPoE is active, the Ethertypes 0x8863 and 0x8864 are automatically allowed (PPPoE
Discovery and Session Stage).
Figure 4-7 Default setting for IP packet filter SCALANCE S623/S627-2M (traffic between DMZ network and internal
network or DMZ network and security module)
Figure 4-8 Default setting for IP packet filter SCALANCE S623/S627-2M (traffic between DMZ network and external
network)
Note
Automatic enabling of Ethertypes
If PPPoE is active, the Ethertypes 0x8863 and 0x8864 are automatically allowed (PPPoE
Discovery and Session Stage).
Service Internal ⇒ External internal => DMZ => From From Enabled ports Meaning
External ⇒ Inter- DMZ Inter- internal external
nal
nal
Allow IP x x x x - - - IP communica-
communica- tion for the se-
tion lected
communication
directions is al-
lowed.
Allow S7 x x x x - - TCP port 102 Communication
protocol of the nodes
using the S7
protocol is al-
lowed.
Allow x x x x - - TCP port 20 For file manage-
FTP/FTPS TCP port 21 ment and file
(explicit access between
mode) server and client.
Allow HTTP x x x x - - TCP port 80 For communica-
tion with a Web
server.
Allow x x x x - - TCP port 443 For secure com-
HTTPS munication with a
Web server, for
example, for Web
diagnostics.
Allow DNS x x x x - - TCP port 53 Communications
UDP port 53 connection to a
DNS server is
allowed.
Allow x x x x - - TCP port For monitoring
SNMP 161/162 nodes capable of
UDP port SNMP.
161/162
Allow SMTP x x x x - - TCP port 25 For the exchange
of e-mails be-
tween authenti-
cated users via
an SMTP server.
Allow NTP x x x x - - UDP port 123 For synchroniza-
tion of the time of
day.
Allow DHCP x x x x - - UDP Port 67 Communication
UDP Port 68 with a DHCP
server is allowed.
Service Internal ⇒ External internal => DMZ => From From Enabled ports Meaning
External ⇒ Inter- DMZ Inter- internal external
nal
nal
Note
No return to standard mode possible
If you switch to the advanced mode and change the configuration for the current project, you
can no longer switch back.
Remedy SCT standalone: Close the project without saving and open it again.
Meaning
In contrast to the configuration of fixed packet filter rules in standard mode, you can
configure individual packet filter rules in the Security Configuration Tool in advanced mode.
You can set the packet filter rules in selectable tabs for the following protocols:
● Layer 3, 4: IP protocol, IP services
● Layer 2: MAC protocol, MAC services
Note
No MAC rules if routing mode is enabled
If you have enabled the routing mode for the security module, MAC rules are irrelevant
(dialogs are disabled).
If you do not enter any rules in the dialogs described below, the default settings of the
firewall apply. For more detailed information, refer to the following section:
● Default settings for CP x43-1 Adv.: Default firewall setting (Page 117)
● Default settings for CP 1628: Default firewall setting (Page 123)
● Default settings for SCALANCE S: Default firewall setting (Page 128)
Application
Global firewall rule sets are configured depending on the module at project level and are
visible in the navigation panel of the Security Configuration Tool. A global firewall rule set
consists of one or more firewall rules and is assigned to the several security modules.
In the global firewall rule sets, a distinction is made between the following:
● IP rule sets
● MAC rule sets
The following schematic illustrates the relationship between globally defined rule sets and
locally used rule sets.
Note
Only assign firewall rule sets that are supported by the security module
A bad assignment of firewall rule sets can lead to undesirable results. You should therefore
always check the module-specific local firewall rules in the result. A bad rule assignment is
not detected in the automatic consistency check. Only rules that are actually supported by
the security module are adopted.
See also
User-specific IP rule sets (Page 149)
5. Enter the firewall rules one by one in the list. Note the parameter description in the
sections below:
For IP rule sets: IP packet filter rules (Page 155).
For MAC rule sets: MAC packet filter rules (Page 164).
6. Assign the global firewall rule set to the security modules in which you want it to be used.
To do this, select the global firewall rule set in the navigation panel and drag this to the
security modules in the navigation panel (drag and drop). As an alternative, you can
make the assignment in the local rule list of a security module using the "Add rule sets..."
button.
Result
The global firewall rule set is used by the security modules as a local rule set and
automatically appears in the module-specific lists of firewall rules.
See also
Global firewall rule sets - conventions (Page 139)
Note
Restrictions when importing firewall rule sets from STEP 7 Professional into the Security
Configuration Tool
In SCT IPv6 firewall rules and ICMPv6 services are not supported. During import firewall
rules identified as IPv6 firewall rules and ICMPv6 services are ignored.
As the bandwidth limit a maximum of 100 Mbps are permitted in SCT. During import firewall
rules with more than 100 Mbps are ignored.
Note
Released configuration limits
The export and import has been released for a maximum of 1000 firewall rule sets each with
a maximum 1000 firewall rules.
Action From To IPv6* Source Destina- Service Band- Logging Stateful Com-
IP ad- tion IP width ment
dress Address
• Allow External • Internal False [free text [free text [free text [Possible • True • True [free text
with max. with max. with max. values: with max.
• Drop • DMZ • False • Fals
255 255 128 0.001…1 255
• Tunnel charac- charac- charac- 00] e charac-
• Any ters] ters] ters] ters]
• Station
Internal • External
• Internal
• DMZ
• Tunnel
• Any
• Station
DMZ • External
• Internal
• Tunnel
• Any
Tunnel • External
• Internal
• DMZ
• Tunnel
• Any
• Station
Any • External
• Internal
• DMZ
Station • External
• Internal
• Tunnel
* This column is optional. If the column does not exist when importing into SCT, the value “False” is used in SCT.
* This column is optional. If the column does not exist when importing into SCT, the value “False” is used in SCT.
Table 4- 12 Permitted parameter values for table sheet “IP Service Groups“
If a service group is imported with an undefined service, the corresponding firewall rule set is
discarded.
You will find rules for permitted parameter values in the section defining MAC services
(Page 168).
Table 4- 15 Permitted parameter values for table sheet “MAC Service Groups“
Meaning
Initially, individual or multiple users are assigned to user-specific IP rule sets. The user-
specific IP rule sets are then assigned to individual or multiple security modules. This makes
it possible, to allow user-specific access. If, for example all access to the networks
downstream from a security module is blocked, certain nodes can be allowed temporarily for
a user based on their IP addresses. This means that access is allowed for this user but
access remains blocked for other users. The responses to user-specific access are always
automatically allowed. This means that only IP rules for the initiative direction need to be
configured.
6. Assign one or more users and/or one or more roles to the user-specific IP rule set. The
assignment of roles to user-specific IP rule sets is possible only for SCALANCE S V4
modules.
Note
Assignment of user-specific IP rule sets
• A security module can only be assigned one user-specific rule set per user.
• Due to the assignment, the right "User/role may log in to module" is activated implicitly
for all users or roles assigned to the IP rule set.
7. Assign the user-specific IP rule set to the security modules in which you want it to be
used. To do this, select the user-specific IP rule set in the navigation panel and drag this
to the security modules in the navigation panel (drag and drop). As an alternative, you
can make the assignment in the local rule list of a security module using the "Add rule
sets..." button.
Result
● The user-specific rule set is used by the assigned security modules as a local rule set and
automatically appears in the module-specific list of firewall rules.
● The user can log on to the security module. Authentication of the user is performed
depending on the selected authentication method either by the security module or a
RADIUS server.
You will find more information creating users in the following section:
Managing users (Page 70)
Note
Releasing UDP multicast connections manually
No automatic firewall rules are created for UDP multicast connections. To enable the
connections, add the relevant firewall rules manually in advanced mode.
Depending on how the connection establishment is configured in STEP 7, the following level
3 firewall rules are created in SCT. If the security module is in a VPN group, the direction
"External" changes to "Tunnel".
The IP address of the connection partner is entered in the "Source IP address" or
"Destination IP address" column of these firewall rules.
For level 2 connections, "Allow" rules are created for both directions. If the security module is
in a VPN group, the direction "External" changes to "Tunnel".
The MAC address of the connection partner is entered in the "Source MAC address" or
"Destination MAC address" column of these firewall rules.
Note
If you want to ensure that only communication through the tunnel is possible, you will
need to create suitable firewall rules in advanced firewall mode, for example, for internal
nodes or NDIS addresses.
To allow only tunneled communication for a CP, add a rule with the following settings:
• "Action": "Drop"
• "From": "Any"
• "To": "External"
For the CP 1628, add a rule with the following settings:
• "Action": "Drop"
• "From": "Station"
• "To": "External"
In addition to this, you need to remove existing firewall rules that allow untunneled
communication.
Parameter
The configuration of an IP rule includes the following parameters:
Example
① All frame types from internal to external are blocked as default, except for those explicitly allowed.
② All frame types from external to internal are blocked as default, except for those explicitly allowed.
③ IP packet filter rule 1 allows packets with the service definition "Service X1" from internal to external.
④ IP packet filter rule 2 allows frames from external to internal when the following conditions are met:
• IP address of the sender: 196.65.254.2
• IP address of the recipient: 197.54.199.4
• Service definition: "Service X2"
⑤ IP packet filter rule 3 blocks frames with the service definition "Service X1" sent from the VPN tunnel to the internal
network.
⑥ IPsec tunnel communication is allowed as default except for the explicitly blocked frame types.
See also
MAC packet filter rules (Page 164)
Range of values for IP address, subnet mask and address of the gateway (Page 287)
● Multiple IP addresses
The rule applies to the specified addresses.
The addresses are specified separated by a semicolon.
● Address range
The rule applies to all the IP addresses covered by the address range.
An address range is defined by specifying the number of valid bit places in the IP address
in the format: [IP address]/[number of bits to be included]
– [IP address]/24 therefore means that only the most significant 24 bits of the IP address
are included in the filter rule: These are the first three octets of the IP address.
– [IP address ]/25 means that only the first three octets and the highest bit of the fourth
octet of the IP address are included in the filter rule.
● Address area
For the source IP address, an address range can be specified separated by a hyphen:
[Start IP address]-[End IP address]
For more detailed information, refer to the following section:
● Range of values for IP address, subnet mask and address of the gateway (Page 287)
Meaning
Using the IP service definitions, you can define succinct and clear firewall rules for specific
services. You select a name and assign the service parameters to it.
These services defined in this way can also be grouped together under a group name.
When you configure the global or local packet filter rules, you use this name.
Note
No MAC rules if routing mode is enabled
If you have enabled the routing mode for the SCALANCE S module, MAC rules are
irrelevant.
Dialog / tab
Select the security module to be edited.
Select the "Edit" > "Properties..." menu command, "Firewall" > "MAC rules" tab.
Permitted directions
The following directions can be set:
Note
IP rules apply to IP packets, MAC rules apply to layer 2 packets
For the firewall, you can define both IP rules and MAC rules. Rules for editing in the
firewall are based on the Ethertype.
IP packets are forwarded or blocked depending on the IP rules and layer 2 packets are
forwarded or blocked depending on the MAC rules.
It is not possible to filter an IP packet using a MAC firewall rule, for example based on a
MAC address.
Examples
You can apply the example of an IP packet filter in Section 5.4.3 (Page 155) analogously to
the MAC packet filter rules.
Meaning
Using the MAC service definitions, you can define firewall rules for specific services. You
select a name and assign the service parameters to it. These services defined in this way
can be grouped together under a group name. When you configure the global or local packet
filter rules, you use this name.
Note
Processing for S7-CPs
Only settings for ISO frames with DSAP=SSAP=FE (hex) are processed. Other frame types
are not relevant for S7 CPs and are therefore discarded even before processing by the
firewall.
Dialogs / tabs
You open the dialog with the following menu command:
"Options" > "IP services..." or "MAC services...", "Service groups" tab. For MAC service
groups the name "ARP" is not permitted.
ICMP incoming - x - x
ICMP pathfinder outgoing - x - -
SNMP incoming x x x x
Syslog outgoing x x x x
NTP outgoing x x x x
DNS outgoing x x x x
HTTP outgoing x - x -
VPN (IKE) x - x -
VPN (NAT Traversal) x - x -
BootP Server incoming - x x -
BootP Client outgoing - x x -
RADIUS outgoing x x x x
CARP outgoing x* x* - -
Pfsync outgoing - - x* -
x enabled as default
- disabled as default
* cannot be adapted
x enabled as default
- disabled as default
* cannot be adapted
The two services "BootP Server" and "BootP Client" are both active together either on the
external interface or on the internal interface. Accordingly, either both firewall rules are active
on the external interface or they are both active on the internal interface.
5.1.1 Overview
Meaning
By using the security module as router, the networks become separate subnets on the
internal, external and DMZ interface (SCALANCE S623/S627-2M only, see section below).
You have the following options:
● Routing - can be set in both standard and advanced mode
● NAT/NAPT routing - can be set in advanced mode
All network queries that do not belong to a subnet are forwarded by a router to a different
subnet, see following section:
● Specifying a standard router and routes (Page 174)
If you have enabled routing mode or the DMZ interface, frames intended for an existing IP
address in the subnet (internal, external, DMZ) are forwarded. The firewall rules configured
for the direction of transmission also apply.
For this mode, you need to configure an IP address and a subnet mask for addressing the
router on the internal subnet and/or on the DMZ subnet for the internal interface and/or for
the DMZ interface. All network queries that do not belong to a subnet are forwarded by the
standard router to a different subnet.
Note
In contrast to the bridge mode of the security module, VLAN tags are lost in routing mode.
Requirement
● The project is in advanced mode.
● The security module is in routing mode or the DMZ interface is activated (SCALANCE
S623 / S627-2M only).
● The external IP address of the security module or the IP address of the DMZ interface
may only be used in the NAT table for the action "Source NAT".
● Checking for duplicates in the NAT table
An external IP address or an IP address in the DMZ network used in the direction
"Destination NAT" or "Source NAT +Destination NAT" may only occur once in the NAT
table for each specified direction.
● Checking for duplicates in the NAPT table
– The port numbers or port ranges of the "Source port" column must not overlap for an
interface.
● Internal NAPT ports can be in the range > 0 and ≤ 65535.
Once you have completed your entries, run a consistency check.
Select the "Options" > "Consistency checks" menu command.
Enabling NAT
The input boxes for NAT are enabled. NAT address translations only take effect with the
entries in the address translation list described below. After creating NAT rules, the
corresponding firewall rules are generated and displayed in advanced mode, see section:
Relationship between NAT/NAPT router and firewall (Page 186)
If PPPoE is activated for the external interface or the DMZ interface, the action "Destination
NAT" cannot be configured. When configuring the action "Source NAT", the IP address
cannot be entered in the "Source translation" input box because this is obtained dynamically
during runtime.
If the SCALANCE S module is in a VPN group (not for SCALANCE S602), the action
"Destination NAT" can also be performed in the following directions:
● Tunnel to internal
● Tunnel to external
● Tunnel to DMZ (only if the DMZ interface is activated)
The following applies, for example for the direction "external to internal": The destination IP
address of a frame coming from the external network is checked to see whether it matches
the IP address specified in the "Destination IP address" input box. If it matches, the frame is
forwarded into the internal network by replacing the destination IP address of the frame with
the IP address specified in the "Destination translation" input box. Access from external to
internal using the external address is possible.
The following table shows the input required for the action "Destination NAT".
If the SCALANCE S module is in a VPN group (not for SCALANCE S602), the action
"Source NAT" can also be performed in the following directions:
● Internal to tunnel
● Tunnel to internal
● External to tunnel
● DMZ to tunnel (only if the DMZ interface is activated)
The following applies, for example for the direction "internal to external": The source IP
address of a frame coming from the internal network is checked to see whether it matches
the IP address specified in the "Source IP address" input box. If it matches, the frame with
the external IP address specified in the "Source translation" input box is forwarded to the
external network as a new source IP address. In the external network, the external IP
address is effective.
The following table shows the input required for the action "Source NAT".
Note
You can configure an address translation to the module IP address in the destination
network for all frames going from a source network to a destination network. The security
module also assigns a port number for each frame. This is an n:1 NAT address translation in
which multiple IP addresses of the source network are translated to one IP address of the
destination network.
Enter, for example, the following parameters for the direction "internal to external":
• Action: "Source NAT"
• From: "Internal"
• To "External"
• Source IP address: "*"
• Source translation: External IP address of the security module
Enabling NAPT
The input boxes for NAPT are enabled. NAPT translations only take effect with the entries in
the list described below. After creating NAPT rules, the corresponding firewall rules are
generated and displayed in advanced mode, see section:
Relationship between NAT/NAPT router and firewall (Page 186)
The IP address translation with NAPT can be performed in the following direction:
● External to internal
If the DMZ interface of the security module (SCALANCE S623/S627-2M only) is activated,
the IP address translation with NAPT can also be performed in the following directions.
● External to DMZ
● DMZ to internal
● DMZ to external
If the SCALANCE S module is in a VPN group (not for SCALANCE S602), IP address
translation with NAPT can also be performed in the following directions:
● External to tunnel
● Tunnel to internal
● Tunnel to external
● DMZ to tunnel (only if the DMZ interface is activated)
● Tunnel to DMZ (only if the DMZ interface is activated)
The following applies, for example for the direction "external to internal": Frames intended for
the external IP address of the security module and for the port entered in the "Source port"
column are forwarded to the specified destination IP address in the internal network and to
the specified destination port.
The following table shows the input required for address translation with NAPT.
See also
IP packet filter rules (Page 155)
Meaning
Address translations with NAT/NAPT can also be performed for communications relations
established via a VPN tunnel.
Requirements
The following requirements apply generally to a SCALANCE S module that will perform an
address translation with NAT/NAPT in a VPN tunnel:
● The SCALANCE S module is in a VPN group.
● The SCALANCE S module is in routing mode and/or the DMZ interface of the
SCALANCE S module is activated.
● The tunnel interface is enabled.
Note:
Once you have configured a NAT address translation to or from the direction of the tunnel,
only the IP addresses involved in the NAT address translation rules can be reached via the
VPN tunnel.
Meaning
After creating NAT/NAPT rules, SCT automatically generates firewall rules that enable
communication in the configured address translation direction. To clarify the relationship
between the NAT/NAPT rules and the corresponding firewall rules, the rules are identified by
corresponding, consecutive numbers in the "NAT/NAPT" and "Firewall" tabs. The generated
firewall rules can, if necessary, be expanded (additional IP addresses / IP address range / IP
address band, services, bandwidth) and as default have the highest priority because SCT
inserts them above existing firewall rules.
If firewall rules already exist that were generated by SCT for NAT/NAPT rules, firewall rules
for further NAT/NAPT rules will be inserted by SCT below these firewall rules.
If firewall rules already exist that reference NAT/NAPT that were placed manually below
firewall rules without NAT/NAPT reference, firewall rules for further NAT/NAPT rules will be
placed by SCT above the firewall rules without NAT/NAPT reference.
After creating NAT/NAPT rules check the position of the firewall rules generated by SCT for
their priority. Firewall rules without NAT/NAPT reference that have higher priority than
firewall rules with NAT/NAPT reference, can prevent the execution of NAT/NAPT.
Firewall parameters generated by SCT cannot be adapted. After deactivating NAT/NAPT,
the firewall rules generated by SCT are removed.
The following table shows the system behind the firewall rules generated for NAT rules for
SCALANCE S modules.
Table 5- 1 NAT address translation and corresponding firewall rules for SCALANCE S modules
The following table shows the system behind the firewall rules generated for NAT rules for
CP x43-1 Adv.
Table 5- 2 NAT address translation and corresponding firewall rules for CP x43-1 Adv.
The following table shows the system behind the firewall rules generated for NAT rules for
SCALANCE S modules.
Table 5- 3 NAPT translation and firewall rules created for SCALANCE S modules
The following table shows the system behind the firewall rules generated for NAPT rules for
CP x43-1 Adv.
Table 5- 4 NAPT translations and created firewall rules for CP x43-1 Adv.
Meaning
After creating NAT/NAPT rules, SCT automatically generates a user-specific IP rule set in
the user-specific firewall that enables communication in the configured address translation
direction. You can then assign this user-specific IP rule set to individual or multiple users
and/or individual or multiple roles (only for SCALANCE S modules as of V4).
The generated firewall rules can, if necessary, be moved and expanded (additional IP
address, services, bandwidth). Firewall parameters generated by SCT cannot be adapted. If
the user-specific IP rule set is dragged ith the mouse to a security module with NAT/NAPT
deactivated, the NAT/NAPT rules from the user-specific firewall are also applied to this
security module.
Note
The address translation action "Double NAT" is not supported in conjunction with the user-
specific firewall.
Supported address translation directions for the action "Source NAT + Destination NAT"
The action "Source NAT + Destination NAT" can be performed in the following directions:
● External to DMZ
● DMZ to external
No IP address can be entered in the "Source IP address" box. This is entered automatically
when the node logs on to the security module.
5.2.1 Overview
Overview
You can operate the security module in the internal network and in the DMZ network as a
DHCP server (DHCP = Dynamic Host Configuration Protocol). This allows IP addresses to
be assigned automatically to the connected devices. To be able to do this the connected
devices must be configured to obtain IP addresses from a DHCP server.
Simultaneous DHCP server operation on both interfaces is possible.
The IP addresses are either distributed dynamically from an address band you have
specified or you can select a specific IP address and assign it to a particular device. If
devices on the internal interface or on the DMZ interface should always be assigned the
same IP address for firewall configuration, the address assignment must only be static based
on the MAC address or based on the client ID.
See also
Consistency checks (Page 66)
Requirement
The "DHCP server" tab is only displayed if the project is in advanced mode.
Note
No return to standard mode possible
If you switch to the advanced mode and change the configuration for the current project, you
can no longer switch back.
Remedy SCT standalone: You close the project without saving and open it again.
5. Make the address assignment. You have the following configuration options:
– Static address assignments
Devices with a specific MAC address or client ID are assigned the specified IP
addresses. You specify these addresses by entering the devices in the address list in
the "Static address assignments" group box. This option makes sense with respect to
firewall rules with explicit specification of source or destination IP address.
– Dynamic address assignments
Devices whose MAC address or whose client ID was not specified specifically, are
assigned a random IP address from the specified address range. You set this address
range in the "Dynamic address assignments" group box.
Note
Dynamic address assignment - reaction after interrupting the power supply
Please note that dynamically assigned IP addresses are not saved if the power supply
is interrupted. On return of the power, you must therefore make sure that the nodes
request an IP address again.
You should therefore only use dynamic address assignment for the following nodes:
• Nodes that are used temporarily in the subnet (such as service devices);
• Nodes that have been assigned an IP address and send this as the "preferred
address" the next time they request an address from the DHCP server (for
example PC stations).
For nodes in permanent operation, use of a static address assignment by specifying a
client ID should be preferred (recommended for S7 CPs because it is simpler to
replace modules) or the MAC address.
6. In the DHCP options, select which additional parameters should be transferred to the
connected nodes.
● The client ID is a string with a maximum of 63 characters. Only the following characters
may be used: a-z, A-Z, 0-9 and - (dash).
Note
In SIMATIC S7, a client ID can be assigned to the devices on the Ethernet interface to
allow them to obtain an IP address using DHCP.
With PCs, the procedure depends on the operating system being used; it is advisable to
use the MAC address here for the assignment.
● For the statically assigned IP addresses, you must specify the IP address.
● The following IP addresses must not be located in the range of the dynamic address
assignments:
– All router IP addresses in the "Routing" tab
– Syslog server
– Standard router
– Address(es) of the security module
● DHCP is supported by the security module on the interface to the internal subnet and on
the interface to the DMZ network. The following additional requirements for IP addresses
in the range of the dynamic address assignments result from this operational behavior of
the security module:
– Bridge mode
The range must be within the network subnet defined by the security module.
– Routing mode
The range must be within the internal subnet defined by the security module.
Note
The DMZ network always represents a separate subnet. When using DHCP on the
DMZ interface, make sure that the free IP address range (dynamic IP addresses) is
within the DMZ subnet.
● The free IP address range must be fully specified by entering the start address and the
end address. The end address must be higher than the start address.
● The IP addresses you enter in the address list in the "Static address assignments" input
area must be in the address range of the internal subnet or in the DMZ network of the
security module.
Note the explanations in section Consistency checks (Page 66).
5.3.1 Overview
Meaning
The date and time are kept on the security module to check the validity (time) of a certificate
and for the time stamps of log entries. With time-of-day synchronization the date and time of
the security module can be adjusted to that of other system components.
The following alternatives can be configured:
● The module time is set automatically to the PC time when a configuration is downloaded.
● Automatic setting and periodic synchronization of the time using a Network Time Protocol
server (NTP server).
Note
Before the security functions of a CP are used, this must receive a valid time-of-day
synchronization frame from the time master.
Note
NTP servers created in STEP 7 are automatically migrated to SCT with the update
interval. The update interval can only be changed in STEP 7.
2. If you have selected the synchronization mode "Time-of-day synchronization with NTP" or
"Time-of-day synchronization with NTP (secure)", with the "Add" button, you assign a
previously created NTP server of the same type as in the "Synchronization mode" box to
the security module.
If no NTP servers exist yet, create an NTP server with the "Configure server..." button.
Parameter Meaning
Key ID Numeric value between 1 and 65534.
Authentication Select the authentication algorithm.
Hex/ASCII Select the format for the NTP key.
Key Enter the NTP key with the following lengths:
Hex: 22 ... 40 characters
ASCII: 11 ... 20 characters
5.4 SNMP
5.4.1 Overview
What is SNMP?
The security module supports the transfer of management information using the Simple
Network Management Protocol (SNMP). To allow this, an SNMP agent is installed on the
security module that receives and responds to SNMP queries. The information on the
properties of SNMPcompliant devices is entered in MIB files (Management Information
Base) for which the user must have the required rights (SNMPv3).
In SNMPv1, the "community string" is also sent. The "community string" is like a password
that is sent along with the SNMP query. If the community string is correct, the security
module replies with the required information. If the string is incorrect, the security module
discards the query and does not reply.
In SNMPv3, the data can be transferred encrypted.
Requirement
HW Config: In the "SNMP" tab of the CP properties, the "Enable SNMP" check box is
selected. If it is not enabled, SNMP cannot be configured in the Security Configuration Tool.
Note
Encrypted data transfer with SNMPv3
To increase security, you should use SNMPv3 since the data is then transferred
unencrypted.
– SNMPv1
The security module uses the following default values for the community strings to
control the access rights in the SNMP agent:
For read access: public
For read and write access: private
To enable write access using SNMP, select the "Allow write access" check box.
– SNMPv3
Select either an authentication method or an authentication and encryption method.
Authentication algorithm: none, MD5, SHA-1
Encryption algorithm: none, AES-128, DES
Note
Avoiding the use of DES
DES is not a secure encryption algorithm. It should therefore only be used where
downwards compatibility is required.
Note
When using SNMPv3 no RADIUS authentication is possible.
security module with an SNMP tool using an SNMP-SET command are not overwritten
when downloading an SCT configuration again to the security module.
6. If you want to use SNMPv3, assign a user a role for which the corresponding SNMP
rights are activated so that it can reach the security module via SNMP.
For more detailed information on configuring users, rights and roles, refer to the next
section:
– Managing users (Page 70)
Overview
Proxy ARP allows routers to respond to ARP queries for hosts. The hosts are in networks
separated by routers but use the same IP address range.
If PC1 sends an ARP request to PC2, it receives an ARP response and the hardware
address of the interface (MAC address of the port of the security module) on which the query
was received from the security module located in between and not from PC2. The querying
PC1 then sends its data to the security module that then forwards it to PC2.
Requirement
The "OPC UA" tab is only available if the OPC UA server function was enabled for the CP in
STEP 7.
Meaning
Here you specify the Security profiles and access options for the UA server of the CP.
● Securityprofile
– No security profile
The CP does not use any Security profile.
– Basic128Rsa15
This corresponds to the Security profile "Basic128Rsa15" of the OPC UA
specification.
The CP uses signing and if configured 128 bit encryption.
– Basic256
This corresponds to the Security profile "Basic256" of the OPC UA specification.
The CP uses signing and if configured 256 bit encryption.
– Basic256Sha256
This corresponds to the Security profile "Basic256Sha256" of the OPC UA
specification.
The CP uses signing and if configured 256 bit encryption using the hash algorithm
SHA-256.
If you enable several options, depending on the settings on the communications partner
(client) the CP selects the profile with the highest possible security.
In the "Certificate validation" tab you set the options for checking the certificates of the
communications partner. You can set the options for the UA client and for the UA server
function of the CP separately.
If you use the client function of the CP, you should also note the following: The value of the
parameter "CheckServerCertificate" you programmed in the connection information
(UASessionConnectInfo) for the client program block "UAConnect" will be overwritten by the
settings in SCT for the certificate check. If the client is to check the certificates of the
communications partner (server), you can ignore the parameter in the UDT
"UASessionConnectInfo". For the certificate check only the settings in the SCT tab
"Certificate validation" are relevant.
● Checking the certificates
The CP always checks the certificate of the communications partner.
If the partner certificate is invalid or is not trustworthy, communication is aborted.
● No strict certificate validation
If the option is selected, the CP also allows communication in the following cases:
– The IP address of the communications partner is not identical to the IP address in its
certificate.
Note: The OPC UA server does not check the IP address of the communications
partner (client).
– The use stored in the certificate (OPC UA client/server) differs from the function (OPC
UA client/server) of the communications partner.
– The current time on the CP is outside the period of validity of the partner certificate.
Regardless of these exceptions, at least the following requirements must be met to
establish a connection:
– The application URI sent by the requesting client must match the URI of the server
application of the CP.
– If the partner certificate is not trustworthy, the CP must at least have stored a self-
signed certificate of the partner.
– If the partner certificate was issued by several CAs, all CAs must be saved in the
certificate store of the CP.
● Do not check period of validity
If the option is enabled, the CP checks the certificate of the communications partner. The
CP also allows communication in the following situation:
– The current time on the CP is outside the period of validity of the partner certificate.
If none of the three options is enabled, no certificates are checked.
5.6.3 S7 communication
In the "S7 communication" tab, you make the settings for S7 communication via the CP and
for protection of LAN access to the pages of the S7 special diagnostics on the CP.
● Disable S7 communication
If the option is enabled, S7 communication via the CP is blocked.
● Disable online diagnostics via LAN
If the option is enabled, access to the diagnostics pages of the S7 special diagnostics on
the CP via LAN is blocked.
In this section, you will learn how to connect IP subnets protected by the security or
SCALANCE M module to a VPN (Virtual Private Network).
As already described in the section on module properties, you can once again use the
default settings to ensure secure communication in your internal networks.
Further information
You will find detailed information on the dialogs and parameter settings in the online help.
You can call this with the F1 key or using the "Help" button in the relevant dialog.
See also
Online functions - diagnostics and logging (Page 273)
Note
If the name of a module is changed, all the modules of the groups to which the changed
module belongs must be reconfigured (menu command "Transfer" > "To all modules...").
If the name of a VPN group is changed, all modules of this VPN group must be reconfigured
(menu command "Transfer" > "To all modules...").
Note
Layer 2 frames are also tunneled when there is a router between two modules. To make this
possible, however, the MAC addresses of the communications partners must be configured
statically in the Security Configuration Tool and, where necessary, static ARP entries must
be entered on the communications devices.
The following applies in general: Non-IP packets are transferred through a tunnel only when
the devices that send or receive the packets were able to communicate previously; in other
words, without using the modules.
Authentication method
The authentication method is specified within a VPN group and decides the type of
authentication used.
Key-based or certificate-based authentication methods are supported:
● Pre-shared keys
Authentication is achieved using a previously agreed character string that is distributed to
all modules in the VPN group.
To do this, enter a password in the "Key" box of the "VPN group properties" dialog or
generate a password using the "New..." button.
● Certificate
Certificate-based authentication "Certificate" is the default that is also enabled in standard
mode. The procedure is as follows:
– When you create a VPN group, a CA certificate is generated automatically for the VPN
group.
– Each module in the VPN group receives a VPN group certificate signed with the key of
the certification authority of the VPN group.
All certificates are based on the ITU standard X.509v3 (ITU, International
Telecommunications Union).
The certificates are generated by a certification function in the Security Configuration
Tool.
Note
Restriction in VLAN operation
With IP packets through the VPN tunnel of the module, no VLAN tagging is transferred.
The VLAN tags included in IP packets are lost when they pass through the modules
because IPsec is used to transfer the IP packets.
As default, no IP broadcast or IP multicast frames can be transferred with IPsec through
a layer 3 VPN tunnel. Through a layer 2 VPN tunnel of the security module, IP broadcast
or IP multicast packets are "packaged" just like MAC packets including the Ethernet
header in UDP and transferred. With these packets, the VLAN tagging is therefore
retained.
Meaning
The following tables show which tunnel interfaces can establish a tunnel between them.
Here, a distinction is made depending on whether the SCALANCE S module is in routing or
in bridge mode.
Regardless of the interface via which the VPN tunnel is established, as default the nodes of
the internal subnets of the security modules can always communicate with each other. If
communication via the VPN tunnel should also extend to other subnets, these can be
enabled for tunnel communication in the "VPN" tab in the advanced module properties, see
following section:
● Configuring other nodes and subnets for the VPN tunnel (Page 243)
Table 6- 2 Tunnel communication between CPs, SCALANCE M modules, SOFTNET Security Clients and SCALANCE S
modules in routing mode
Responder interface
Initiator interface External (SCALANCE External (SCALANCE GBit, IE External DMZ (SCALANCE
M875) M-800) (CP) (SCALANCE S623 / S627-2M)
S)
PC/PG x x x x x
(SSC)
External - x x x x
(SCALANCE
M875)
Responder interface
Initiator interface External (SCALANCE External (SCALANCE GBit, IE External DMZ (SCALANCE
M875) M-800) (CP) (SCALANCE S623 / S627-2M)
S)
External - x x x x
(SCALANCE M-
800)
Gbit, IE - - x x x
(CP)
External - - x x x
(SCALANCE S)
DMZ - - x x x
(SCALANCE S623
/ S627-2M)
x is supported
- is not supported
Table 6- 3 Tunnel communication between CPs, SOFTNET Security Clients and SCALANCE S modules in bridge mode
Responder interface
Initiator interface GBit, IE (CP) External (SCALANCE S) DMZ (SCALANCE S623 /
S627-2M)
PC/PG (SSC) x x -
GBit, IE (CP) x x -
External (SCALANCE S) x x -
DMZ (SCALANCE S623 / - - -
S627-2M)
x is supported
- is not supported
Note
SCALANCE S V1/V2 modules
SCALANCE S V1/V2 modules are no longer supported as of SCT V5.0. Existing SCALANCE
S V1/V2 modules from projects of older SCT versions can therefore no longer be inserted in
VPN groups. It is also not possible to add SCALANCE S modules to a VPN group in which
there is a SCALANCE S V1/V2 module. The SCALANCE S V1/V2 must first be removed
from the VPN group or replaced by a SCALANCE S module with a higher firmware version.
Requirement
Note
Current date and current time of day on the modules
When using secure communication (for example HTTPS, VPN...), make sure that the
modules involved have the current time of day and the current date. Otherwise the
certificates used will not be evaluated as valid and the VPN communication will not work.
Configuring properties
Just as when configuring modules, the two selectable operating views in the Security
Configuration Tool have an effect on configuring VPN groups:
● Standard mode
In standard mode, you retain the defaults set by the system. Even without expert
knowledge, you can configure IPsec tunnels in this way and operate secure data
communication.
● Advanced mode
The advanced mode provides you with options for setting specific configurations for
tunnel communication.
Note
Expiry of a certificate
Communication through the VPN tunnel continues after the certificate has expired until
the tunnel is terminated or the SA lifetime expires. You will find more information on
certificates, in the following section:
• Managing certificates (Page 85)
Note
No return to standard mode possible
If you switch to the advanced mode and change the configuration for the current project, you
can no longer switch back.
Remedy SCT standalone: You close the project without saving and open it again.
Note
Knowledge of IPsec necessary
To be able to set these parameters, you require IPsec experience. If you do not make or
modify any settings, the defaults of standard mode apply.
3. Select whether a pre-shared key or certificate will be used for authentication. For more
detailed information, refer to the following section:
– Authentication method (Page 212).
Here you set the parameters for negotiating the security parameters to be used in phase 2:
Note the permitted settings for nodes with an unknown IP address, see section Including
module in configured VPN group (Page 229).
Parameter Description
IKE mode • Main mode (default setting)
• Aggressive mode
Selection of the mode IKE phase 1. In Main mode, the VPN connection
partners exchange their identities encrypted, in Aggressive mode unen-
crypted. In Aggressive mode IKE phase 1 runs faster but is less secure
than in the alternative Main mode.
Phase 1 DH group Groups selectable for the Diffie-Hellman key exchange:
• Group 1*
• Group 2*
• Group 5
• Group 14 (default setting)
• Group 15
SA lifetime type Phase 1 Security Association (SA):
• Time: Time limit in minutes
The lifetime of the current key material is limited in time. When the time
expires, the key material is renegotiated.
SA lifetime Numeric value:
Range of values for time: 1440 … 2500000 minutes (default setting: 2879)
Phase 1 encryption Encryption algorithm:
• DES*: Data Encryption Standard (56 bit key length, mode CBC)
• 3DES-168*: Triple DES (168-bit key length, mode CBC)
• AES-128, 192, 256 (default setting): Advanced Encryption Standard
(128-bit, 192-bit or 256-bit key length, mode CBC)
Phase 1 authentication Authentication algorithm:
• MD5*: Message Digest Algorithm 5
• SHA1: Secure Hash Algorithm 1 (default setting)
* The setting is classified as less secure. It is recommended that you use a more secure
setting.
Here, you set the parameters for negotiating the security parameters used for the IPsec data
exchange with ESP (Encapsulating Security Payload) and AH (Authentication Header).
Communication in phase 2 is already encrypted.
Parameter Description
SA lifetime type Phase 2 Security Association (SA):
• Time (default setting): Time limit in minutes The use of the current key
material has a time limit. When the time expires, the key material is re-
negotiated.
• Limit: Limitation of the data volume in MB
SA lifetime Numeric value:
• Range of values for time: 60 … 16666666 minutes (default setting:
2879)
• Range of values for limit: 2000 ... 500000 MB (default setting: 4000)
Phase 2 encryption Encryption algorithm:
• DES*: Data Encryption Standard (56 bit key length, mode CBC)
• 3DES-168*: Triple DES (168-bit key length, mode CBC)
• AES-128 (default setting): Advanced Encryption Standard (128-bit key
length, mode CBC)
Phase 2 authentication Authentication algorithm:
• MD5*: Message Digest Algorithm 5
• SHA1 (default setting): Secure Hash Algorithm 1
Perfect Forward Secre- If you enable this check box, new Diffie-Hellmann public key values are
cy exchanged for recalculation of the keys. If the check box is disabled, the
values already exchanged in phase 1 are used for recalculation of the keys.
* The setting is classified as less secure. It is recommended that you use a more secure
setting.
Parameter Setting
Authentication method Certificate
IKE mode Main
Parameter Setting
Phase 1 DH group Group 14
Phase 1 encryption AES-256
Phase 1 SA lifetime SA lifetime proposed by the initiator: 480 minutes
Range permitted by the responder for the SA
lifetime: 480 … 2880 minutes
Phase 1 authentication SHA1
Phase 2 SA lifetime type Time
Phase 2 encryption AES-128
Phase 2 SA lifetime SA lifetime proposed by the initiator: 240 minutes
Range permitted by the responder for the SA
lifetime: 60 … 2880 minutes
Phase 2 authentication SHA1
Perfect Forward Secrecy Disabled
Parameter Setting
Authentication method Certificate
IKE mode Main
Phase 1 DH group Group2
Phase 1 encryption AES-256
Phase 1 SA lifetime SA lifetime proposed by the initiator: 480 minutes
Range permitted by the responder for the SA
lifetime: 480 … 2880 minutes
Phase 1 authentication SHA1
Phase 2 SA lifetime type Time
Phase 2 encryption 3DES-168
Phase 2 SA lifetime SA lifetime proposed by the initiator: 2880
minutes
Range permitted by the responder for the SA
lifetime: 60 … 2880 minutes
Phase 2 authentication SHA1
Perfect Forward Secrecy Disabled
Parameter Setting
Authentication method Certificate
IKE mode Main
Phase 1 DH group Group2
Phase 1 encryption 3DES-168
Parameter Setting
Phase 1 SA lifetime SA lifetime proposed by the initiator: 480 minutes
Range permitted by the responder for the SA
lifetime: 480 … 2880 minutes
Phase 1 authentication SHA1
Phase 2 SA lifetime type Time
Phase 2 encryption 3DES-168
Phase 2 SA lifetime SA lifetime proposed by the initiator: 2880
minutes
Range permitted by the responder for the SA
lifetime: 60 … 2880 minutes
Phase 2 authentication SHA1
Perfect Forward Secrecy Disabled
Parameter Setting
Authentication method Certificate
IKE mode Main
Phase 1 DH group Group2
Phase 1 encryption DES
Phase 1 SA lifetime SA lifetime proposed by the initiator: 480 minutes
Range permitted by the responder for the SA
lifetime: 480 … 2880 minutes
Phase 1 authentication MD5
Phase 2 SA lifetime type Time
Phase 2 encryption 3DES-168
Phase 2 SA lifetime SA lifetime proposed by the initiator: 2880
minutes
Range permitted by the responder for the SA
lifetime: 60 … 2880 minutes
Phase 2 authentication SHA1
Perfect Forward Secrecy Disabled
Parameter Setting
Authentication method Pre-shared key
IKE mode Main
Phase 1 DH group Group2
Phase 1 encryption 3DES-168
Phase 1 SA lifetime SA lifetime proposed by the initiator: 480 minutes
Range permitted by the responder for the SA
lifetime: 480 … 2880 minutes
Parameter Setting
Phase 1 authentication SHA1
Phase 2 SA lifetime type Time
Phase 2 encryption 3DES-168
Phase 2 SA lifetime SA lifetime proposed by the initiator: 2880
minutes
Range permitted by the responder for the SA
lifetime: 60 … 2880 minutes
Phase 2 authentication SHA1
Perfect Forward Secrecy Disabled
Since the initiator is a Known Peer and both security modules are in "VPN Group 1", the
VPN connection can be established with the properties of this VPN group without any further
configuration.
As default, the responder allows VPN connection establishment by Unknown Peers with the
properties of the predefined VPN profile 1. To allow the VPN connection establishment with
the properties of the VPN group "VPN Group 1", this VPN group must be selected in the
module-specific properties of the responder.
Note
If you remove an active node from an existing VPN group, this can still establish a
connection to the group nodes even if you have downloaded the project to all nodes of the
VPN group again.
If you do not want the removed active node to be able to establish a connection any longer,
renew the CA certificate of the VPN group and download the project again to the nodes of
the VPN group.
The CA certificate of the VPN group can be renewed in the group properties of the VPN
group or in the certificate manager, "Certification authorities" tab.
Advantage in case a
Existing modules that have already been commissioned do not need to be reconfigured and
loaded. Active communication is not influenced or interrupted.
Meaning
You can configure the following module-specific properties for data exchange via the IPsec
tunnel in the VPN:
● Dead peer detection
● Permission to initiate connection establishment
Requirements
● You can only make settings in the "VPN" tab if the module you are configuring is in a VPN
group.
● The "VPN nodes" dialog area in the "VPN" tab is only displayed if the project is in
advanced mode.
Mode Meaning
Start connection to partner (initia- If this option is selected, the module is "active", in other
tor/responder) (default) words, it attempts to establish a connection to a partner.
The reception of requests for VPN connection establish-
ment is also possible.
This option is recommended if the module being config-
ured is assigned a dynamic IP address by the ISP.
The partner is addressed using its configured WAN IP
address, its configured external module IP address or the
configured DNS name.
Wait for partner (responder) If this option is selected, the module is "passive", in other
words, it waits for the partner to initiate the connection.
This option is recommended if the module being config-
ured is assigned a static IP address by the ISP.
Note
Make sure that you do not set all the modules in a VPN group to "Wait for partner" otherwise
no connection is established.
WAN IP address / FQDN - addresses of the modules and gateways in a VPN over Internet
When operating a VPN with IPsec tunnel over the Internet, additional IP addresses are
generally required for the Internet gateways such as DSL routers. The individual security or
SCALANCE M modules must know the public IP addresses of the partner modules in the
VPN that need to be reached via the Internet.
Note
If you use a DSL router as Internet gateway, the following ports (at least) must be opened on
it as described in the relevant documentation and the data packets forwarded to the module:
• Port 500 (ISAKMP)
• Port 4500 (NAT-T)
security module at the same time, this FQDN must match the FQDN entered in the "DNS"
tab that is registered with a provider for dynamic DNS.
Whether the external IP address, the IP address of the DMZ interface (only SCALANCE
S623 / S627-2M) or the WAN IP address / the FQDN will be used can be specified in the
VPN properties for specific connections. For more detailed information on VPN properties for
specific connections, refer to the following section:
Configuring VPN properties for specific connections (Page 234)
If you do not enter an access point here, the external IP address or the IP address of the
DMZ interface (SCALANCE S623/S627-2M only) will be used as the VPN endpoint. For
SCALANCE M-800 modules configured as responders, an access point must be specified.
For VPN connections from SOFTNET Security Client / SCALANCE M-800 modules to
SCALANCE S / CPs the selected VPN profile with the highest priority is always used and
read out. The authentication method of the selected VPN profile must match the
authentication method of the corresponding VPN group. The priority of the VPN profile is as
follows:
1 Selected VPN group profile
2. VPN profile 1
3. VPN profile 2
4. VPN profile 3
5. VPN profile 4
6. VPN profile 5
For VPN connections from SCALANCE M875 modules to SCALANCE S / CPs, VPN profile
3 must be selected if the authentication method of the corresponding VPN group is
"Certificate". If the authentication method of the corresponding VPN group is "Preshared
key", VPN profile 5 must be selected.
See also
Including module in configured VPN group (Page 229)
Meaning
While module-specific VPN properties are configured for a specific module, connection-
specific VPN properties relate to the VPN connections of a module. If a module establishes
several tunnel connections to other modules, with connection-specific VPN properties, it is
possible, for example, to configure which connections the module initiates and which it does
not.
Requirements
● The module is a member of a VPN group.
Parameter
Parameter Meaning
Initiator/Responder Specifies the permission to initiate connection establishment
Partner module Display of the module name of the partner module.
Type of transferred packets Display of the layer on which the packets are transferred.
Local interface Specifies the interface that will be used as the VPN endpoint
on the selected partner module. If a WAN access point (IP
address / FQDN) is configured for the module, this can also
be selected here.
Partner interface Specifies the interface that will be used as the VPN endpoint
on the partner module. If a WAN access point (IP address /
FQDN) is configured for the VPN partner, this can also be
selected here.
Meaning
You can generate your VPN information for the assignment of parameters to SCALANCE M
modules using the Security Configuration Tool. With the generated files, you can then
configure the SCALANCE M modules.
The following file types are generated:
● Export file with the configuration data
– File type: *.txt file in ASCII format
– Contains the exported configuration information for the SCALANCE M including
information on the additionally generated certificates.
– Export file for SCALANCE M875 modules:
Note
Configuration files are not transferred to the module. An ASCII file is generated with which
you can configure the VPN-relevant properties of the SCALANCE M. Fur this to be possible,
the module must be in at least one VPN group with a security module or a SOFTNET
Security Client as of V3.0.
Note
Protecting exported configuration files from unauthorized access
Configuration files for SCALANCE M exported from the Security Configuration Tool can
contain security related information. You should therefore make sure that these files are
protected from unauthorized access. This is particularly important when passing on the files.
Note
You will find further information on configuration in the operating instructions for the relevant
SCALANCE M modules.
Meaning
You can generate your VPN information for the assignment of parameters to a VPN device
using the Security Configuration Tool. With the generated files, you can then configure the
VPN device.
To do this, select the VPN device you want to edit and then select the menu command "Edit"
> "Properties...".
● VPN group certificates of the VPN device
– *.crt file: Base64-coded certificate
– *.crt file: DER coded certificate
– *.pem file: Base64-coded certificate
– *.cer file: CER coded certificate
– *.der file: DER coded certificate
● VPN group certificates of partner modules:
– *.crt file: Base64-coded certificate
– *.crt file: DER coded certificate
– *.pem file: Base64-coded certificate
– *.cer file: CER coded certificate
– *.der file: DER coded certificate
● Private keys:
– *.p12 file: Password-protected PKCS12 archive with private key
– *.key: Unprotected Base64-coded private key
● Certification authorities of the VPN groups:
– *.crt file: Base64-coded certificate
– *.crt file: DER coded certificate
– *.pem file: Base64-coded certificate
– *.cer file: CER coded certificate
– *.der file: DER coded certificate
Note
Configuration files are not transferred to the VPN device. An ASCII file is generated with
which you can configure the VPN device. For this to be possible, the VPN device must be in
at least one VPN group with a security module or a SOFTNET Security Client as of V3.0.
3. In the save dialog that then opens, enter the path and file name of the configuration file
and click the "Save" button.
4. In the dialog that follows, choose whether you want to create your own password for the
two created certificate files.
If you select "No", the project name is assigned as the password (for
example VPN_project_02), not the project password.
If you select "Yes" (recommended), you enter a password in the next dialog.
Result: The files (and certificates) are stored in the folder you specify.
Meaning
You can generate the VPN information for the assignment of parameters to an NCP VPN
client (Android) using the Security Configuration Tool. With the generated files, you can then
configure the NCP VPN client software.
Note
Configuration files are not transferred to the NCP VPN client (Android). An ASCII file is
generated with which you can configure the NCP VPN client (Android). To allow this, the
NCP VPN client (Android) must be located in at least one VPN group with a security module.
SCALANCE S
Apart from the static configuration of the network nodes, a SCALANCE S module also
provides the option of learning these automatically.
How to configure the network nodes is described in the following section:
Configuring other nodes and subnets for the VPN tunnel (Page 243)
For more information on automatic learning of internal network nodes, refer to the following
section:
How the learning mode works (Page 244)
6.9.1 Configuring other nodes and subnets for the VPN tunnel
Meaning
By adding a security module to a VPN group, the local, internal network nodes/subnets of
the security module are automatically enabled for VPN tunnel communication. To allow
communication via the VPN tunnel with other subnets or nodes of another subnet, these
subnets or nodes need to be enabled for VPN tunnel communication in the configuration.
A subnet that needs to be enabled in the configuration may be as follows:
● A subnet that is reachable via the local network on the internal interface if a VPN tunnel
terminates on the external interface or on the DMZ interface.
● A subnet that can be reached via the DMZ interface if a VPN tunnel terminates at the
external interface.
● A subnet that can be reached via the external interface if a VPN tunnel terminates at the
DMZ interface.
Requirement
Before the nodes or subnets can be enabled for tunnel communication, the following
requirements must be met:
● The security module is in a VPN group.
● The "VPN nodes" dialog area in the "VPN" tab is only displayed if the project is in
advanced mode.
Note
No return to standard mode possible
If you switch to the advanced mode and change the configuration for the current project,
you can no longer switch back.
Remedy SCT standalone: You close the project without saving and open it again.
Finding nodes for tunnel communication automatically (SCALANCE S in bridge mode only)
One great advantage of configuration and operation of tunnel communication is that
SCALANCE S modules can find nodes in the internal network automatically. This means that
you do not need to configure the internal network nodes involved in tunnel communication
manually.
New nodes are detected by the SCALANCE S module during operation. The detected nodes
are signaled to the SCALANCE S module belonging to the same group. This allows data
exchange within the tunnels of a VPN group in both directions at any time.
Requirements
The following nodes are detected:
● Network nodes with IP capability
Network nodes with IP capability are found when an ICMP response to the ICMP subnet
broadcast is sent.
IP nodes downstream from routers can be found if the routers pass on ICMP broadcasts.
● ISO network nodes
Network nodes without IP capability but that can be addressed over ISO protocols can
also be learnt.
This is only possible if they reply to XID or TEST packets. TEST and XID (Exchange
Identification) are auxiliary protocols for exchanging information on layer 2. By sending
these packets with a broadcast address, these network nodes can be located.
● PROFINET nodes
Using DCP (Discovery and basic Configuration Protocol), it is possible to find PROFINET
nodes.
Network nodes that do not meet these conditions must be configured statically.
Note
No learning mode for VPN tunnel on DMZ interface
The learning of internal nodes is supported only on interfaces that are connected in bridge
mode. The DMZ interface is always connected in routing mode.
Note: In learning mode, all network nodes in the internal network are detected. The
information relating to VPN configuration limits relates only to network nodes that
communicate over VPN in the internal network.
Note
If more than 128 internal nodes are being operated, the permitted configuration limits are
exceeded and an illegal operating status results. Due to the dynamics in the network traffic,
this causes internal nodes that have already been learned to be replaced by new previously
unknown internal nodes.
Note
No return to standard mode possible
If you switch to advanced mode and change the configuration for the current project, you can
no longer switch back.
Remedy SCT standalone: You close the project without saving and open it again.
Meaning
Failures of the security modules SCALANCE S623 as of V4 and SCALANCE S627-2M as of
V4 can be automatically compensated by routers and firewall redundancy during operation.
To do this, group two security modules of the type SCALANCE S623 or SCALANCE S627-
2M in a redundancy relationship and then decide which will be the active security module of
the redundancy relationship during normal operation. If the active security module fails, the
passive security module automatically takes over its function as firewall and (NAT/NAPT)
router. To ensure the identical configuration of both security modules, these are connected
together via their DMZ interfaces and their configurations are synchronized during operation.
In this case, the DMZ interfaces of the security modules involved cannot be used for other
purposes.
Address redundancy
In addition to their module IP addresses, the two security modules share a common IP
address on the external and on the internal interface so that if one of the security modules
fails, the IP addresses do not need to be changed. To do this, you need to configure an IP
address for the external and for the internal interface of the redundancy relationship.
● Log settings
● SNMP
● MRP/HRP
● RADIUS
Note
Loading a configuration on security modules of a redundancy relationship (only SCALANCE
S623/S627-2M as of V4)
The configured properties of a redundancy relationship must be loaded on both security
modules. To load the configuration, the physical IP address via which your engineering
station can reach the security module must be used. The virtual IP addresses of the
redundancy relationship cannot be used for loading.
Note
Configuring routing when using router and firewall redundancy
In a redundancy relationship only routing information is synchronized between the security
modules that was configured statically in the properties of the redundancy relationship in the
“Routing” tab. Routing entries resulting dynamically due to using standard routers are not
synchronized. When using routers and firewall redundancy it is therefore recommended that
you configure all known routers statically.
Requirements
Security modules can only be assigned to a redundancy relationship if they meet the
following requirements:
● Security module is of the type "S623 V4" or "S627-2M V4"
● The security module is in routing mode.
● All interfaces of the security module are active
● IP assignment method "static address" is configured for all interfaces
● The security module is not a member of a VPN group.
● The security module is not assigned to any other redundancy relationship
Procedure
1. Select the "Redundancy relationships" object in the navigation panel.
2. Select the menu command "Insert redundancy relationship..." in the shortcut menu (right
mouse key) of the object.
Result: The created redundancy relationship is shown in the navigation panel.
3. Assign the security modules to the redundancy relationship by selecting them in the
content area and dragging them to the created redundancy relationship in the navigation
panel.
4. in the "Configuration of the redundancy relationship" dialog, you have the following
options for configuring the redundancy relationship:
– Adoption of the configuration from the "Firewall", "Routing" and "NAT/NAPT" tabs of a
security module for the redundancy relationship. From the drop-down list, you can
select the security module whose configuration you want to use for the redundancy
relationship. This overwrites an existing configuration of the redundancy relationship.
– Creation of the assigned security module within the redundancy relationship. This is
possible only when only one security module is assigned to a created redundancy
relationship.
As an alternative, you can configure the redundancy relationship later using the
properties of the redundancy relationship, see section:
Configuring redundancy relationships (Page 251)
Result: You have created a redundancy relationship and assigned the required security
modules to it.
For general information on configuring network parameters, refer to the following section:
Creating modules and setting network parameters (Page 91)
Configuring routing
The configuration of routes for the redundancy relationship is basically the same as when
configuring routes for individual security modules.
For general information on configuring routing, refer to the following section:
Specifying a standard router and routes (Page 174)
See also
MAC packet filter rules (Page 164)
Further information
You will also find detailed information on the dialogs and parameter settings in the online
help of the SOFTNET Security Client.
You can call this with the F1 key or using the "Help" button in the relevant dialog.
Note
Via the IPsec tunnel, IP-based communication is possible only between SOFTNET Security
Client and the security modules as well the internal nodes downstream from the security
modules. Layer 2 communication is not possible with the SOFTNET Security Client.
Response to problems
If problems occur on your PG/PC, SOFTNET Security Client reacts as follows:
● Established security policies are retained when you turn your PG/PC off and on again;
● Messages are displayed if a configuration is not found.
Core statement
You install the SOFTNET Security Client PC software from the product DVD.
1. First read the information in the README file of your SCALANCE S DVD and follow any
additional installation instructions it contains.
2. Run the Setup program;
The simplest way is to open the overview of the contents of your SCALANCE S DVD →
this is started automatically when you insert the DVD or can be opened from the start.exe
file. You can then select the entry "Installation SOFTNET Security Client" directly
NOTICE
Incompatibility with other VPN client software
If other VPN client software is installed on your PC in addition to the SOFTNET Security
Client, it may no longer be possible to establish VPN tunnels using the SOFTNET Security
Client. You should therefore uninstall this VPN client software before using the SOFTNET
Security Client.
Startup behavior
Downloading the security rules can take some time. The CPU of the PG/PC is utilized up to
100% during this time.
Assign the created SOFTNET Security Client to the VPN group or groups in which an IPsec
tunnel is to be set up to the PG/PC. The group properties you configured for these VPN
groups are adopted.
Note
Refer to the information on parameters in the following section:
• Including module in configured VPN group (Page 229)
Note
If you create several SOFTNET Security Clients within a group, no tunnels are set up
between these clients but only from the relevant client to the security modules.
Procedure
To generate the configuration files, perform the following steps in SCT:
1. Create a module of the type SOFTNET Security Client in SCT.
2. Assign the SSC module to the VPN groups in which the PG/PC will communicate over
IPsec tunnels.
Configurable properties
You can use the following individual services:
● Setting up secure IPsec tunnel communication (VPN) between the PC/PG and all security
modules of a project or individual security modules. The PC/PG can access the security
modules and the internal nodes via this IPsec tunnel.
● Enabling and disabling existing secure connections.
● Only possible when the learning mode is enabled: Setting up connections after adding
end devices later.
● Checking a configuration; in other words, which connections are set up or possible.
The following options are available in the “VPN control" if the SOFTNET Security client was
started by a user with administrative rights.
Option Meaning
Load Configuration With this button you open a file dialog for selecting the configuration file created
with the Security Configuration Tool.
Disable / Enable Disable / enable all secure tunnels.
Tunnel Overview Dialog for setting up and diagnostics of the tunnel.
In this dialog, you will find a list of the secure tunnels that can be set up.
If the SOFTNET Security client was started by a user without administrative rights only the
button “Tunnel Overview" is available in the “VPN Diagnostics” dialog area.
NOTICE
Incompatibility with other VPN client software
If other VPN client software is installed on your PC in addition to the SOFTNET Security
Client, it may no longer be possible to establish a VPN tunnel using the SOFTNET Security
Client. You should therefore uninstall this VPN client software before using the SOFTNET
Security Client.
Requirement
You have started the SOFTNET Security Client with administrative rights.
5. If you have selected Certificate as the authentication method in the Security Configuration
Tool, you will now be prompted to enter your password.
6. If you have configured a SCALANCE M875 module, SCALANCE M-800 module or an S7
CP with DHCP activated on the Gbit interface in the Security Configuration Tool, the
"DNS/IP settings" dialog opens. Follow the steps below depending on the configured
module type:
– For SCALANCE M875 modules and SCALANCE M-800 modules: Decide whether or
not the tunnel to the module will be established using the IP address obtained from the
ISP at runtime or alternatively using a DNS name.
– For S7 CPUs with DHCP activated on the Gbit interface: Enter the IP address
assigned using DHCP.
Note
Setting the firewall under Windows 7
If you are asked for the networks in which you want to allow communication of the
SOFTNET Security Client in Windows 7, you will need to allow communication of the
SOFTNET Security Client in public networks otherwise the SOFTNET Security Client
does not display learned nodes in the tunnel overview.
7. Now open the "Tunnel Overview" dialog with the "Tunnel Overview" button.
In the table, you can see the security modules and nodes with status information about
the tunnel connections.
See also
Setting a managed configuration - "Manage users and groups" dialog (Page 265)
Meaning
In the table that opens, you will see the modules and nodes with status information on the
tunnel connections.
"Delete" button
With this, you delete all the IP security policies set up by the SOFTNET Security Client
completely.
Note
Extension of the security policy when activating internal nodes
Please note that the security policy in the system is extended each time the internal nodes
are activated. Deactivation of the overall system (via the shortcut menu of the higher-level
SCALANCE S) does not result in the adjustment of the security policy but only to
deactivation of the policy. This means that the deactivated overall security policy plus the
additional internal node are activated when an internal node is activated. If you want to make
sure that the established security policy completely refers to the nodes you activated, close
the SOFTNET Security Client and reopen it.
Note
Statically configured nodes and subnets
If you configure nodes or subnets statically at a later point in time, you will also need to
download the configuration for a SOFTNET Security Client used in the VPN again.
Parameter
Symbol Meaning
There is no connection to the module or node.
There are further nodes that are not displayed. Double-click on the symbol to display fur-
ther nodes.
Tunnel to node is disabled. There is no IP security policy set up in the system. You com-
municate with this node without encryption.
Tunnel to node is enabled. There is an IP security policy set up in the system. You com-
municate with encryption and therefore securely with this node.
Tunnel to SCALANCE S module is disabled. There is no IP security policy set up in the
system. You communicate with this module without encryption.
Tunnel to SCALANCE S module is enabled. There is an IP security policy set up in the
system. You communicate with encryption and therefore securely with this module.
Tunnel to SCALANCE S M875/M-800 module is disabled. There is no IP security policy
set up in the system. You communicate with this module without encryption.
Tunnel to SCALANCE S M875/M-800 module is enabled. There is an IP security policy set
up in the system. You communicate with encryption and therefore securely with this mod-
ule.
Tunnel to CP343-1 Advanced is disabled. There is no IP security policy set up in the sys-
tem. You communicate with this CP without encryption.
Tunnel to CP 343-1 Advanced is enabled. There is an IP security policy set up in the sys-
tem. You communicate with encryption and therefore securely with this CP.
Tunnel to CP 443-1 Advanced is disabled. There is no IP security policy set up in the
system. You communicate with this CP without encryption.
Tunnel to CP 443-1 Advanced is enabled. There is an IP security policy set up in the sys-
tem. You communicate with encryption and therefore securely with this CP.
Tunnel to CP 1628 / CP 1243-1 / CP 1543-1 is disabled. There is no IP security policy set
up in the system. You communicate with this CP without encryption.
Note: The creation of configuration files for the SOFTNE Security client with which VPN
tunnels can be established to the CP 1243-1 and CP 1543-1 is possible as of STEP 7 V12
SP1.
Symbol Meaning
Tunnel to CP 1628 / CP 1243-1 / CP 1543-1 is enabled. There is an IP security policy set
up in the system. You communicate with encryption and therefore securely with this CP.
The creation of configuration files for the SOFTNE Security client with which VPN tunnels
can be established to the CP 1243-1 and CP 1543-1 is possible as of STEP 7 V12 SP1.
Tunnel to internal subnet is disabled. There is no IP security policy set up in the system.
Tunnel to internal subnet is enabled. There is an IP security policy set up in the system.
Module / node cannot be reached.
Module / node can be reached, tunnel to module / node is, however, disabled. There is no
IP security policy set up in the system. You communicate with this module / node without
encryption.
Module / node can be reached, tunnel to module / node is enabled.
Reachability test disabled. No statement can be made as to whether the node can be
reached.
* In Windows 7 SP1 and higher, the table is valid if the Windows firewall is enabled.
Logging Console
In the "Settings" dialog, you can select which entries are displayed in the log console. You
can open this dialog in the main dialog with the menu command "Settings" > "SOFTNET
Security Client settings".
The following information is shown:
● Diagnostics information about connection establishment with the configured security
modules and internal nodes / subnets.
● Date and time stamp at the time of the events
● Establishment and termination of a security policy
● Negative reachability test (test ping) to the configured nodes
● Download configuration files
● Learn / unlearn internal nodes/subnets
Further notes
● Nodes that are still entered in the list, but no longer exist in the subnet, remain in the list
for approximately 10 minutes during which time, they are checked to find out whether or
not they are available again. If it can no longer be reached, the entry is removed from the
list and a corresponding entry appears in the logging console.
Privileged users
Privileged users can make all settings in SOFTNET Security Client, load VPN configuration
files and diagnose the VPN tunnel in the tunnel overview.
The "Manage users and groups" dialog provides privileged users with the option of creating
configurations for non-privileged users that automatically become active when this user logs
on in Windows. This means that non-privileged users can also use VPN tunnel connections.
Privileged users also have the option of putting users together to form groups to then be able
to create the VPN group configurations for these groups. This can reduce the configuration
effort.
Note
Changing VPN group configurations
If a user with administrative rights makes changes to a VPN group configuration, the
changes also affect all members of this group.
Note
Note the "Security instructions" and notes on firewall parameter assignment
The SOFTNET Security Client can support you only within certain limits when assigning
parameters for the Windows firewall in terms of the secure operation of plants, solutions,
machines, devices and/or networks.
Note the "Security instructions" and notes on firewall parameter assignment in the
configuration manual and in the online help of the SOFTNET Security Client.
ESP not not both IPSec User data traffic of the VPN tunnel
ap- appli- ends
plica cable
ble
UDP All 3820 Incom- SCP Automatic learning of internal nodes of the VPN
ing devices.
ICMP not not both Reachabil- ICMP packets of the SOFTNET Security Client
ap- appli- ends ity test reachability test.
plica cable
ble
Logged-on users Shows the users logged on to the Internet page for user-
specific IP rule sets.
Communications status Display of the communication status and the internal net-
work nodes of security modules located in the same VPN
group as the selected security module.
Internal nodes Display of the internal network nodes of the security mod-
ule.
Dynamically updated firewall rules Display of the IP addresses enabled dynamically by HTTP
or HTTPS or downloaded later by a user. The IP addresses
in this tab can be updated by the following events:
• Expansion/modification of the IP access control list
• Updating he firewall rules
• Dynamic expansions entered by the CP during runtime,
for example PROFINET IO devices
Since this tab only shows the dynamically updated firewall
rules, to gain an overall view of the current firewall status of
the module, the firewall rules that were configured offline
must also be included.
For more detailed information on the possible settings, in the individual tabs, refer to the
online help.
Note
Requirement for online diagnostics in ghost mode
Online diagnostics is only available in ghost mode if the security module has learnt the IP
address of the internal node and has adopted this as its external interface. After this, the
security module can be reached via the IP address of the external interface.
Warning if the configuration is not up-to-date or the wrong project has been selected
When you open the online dialog, the program checks whether the current configuration on
the security module matches the configuration of the loaded project. If there are differences
between the two configurations, a warning is displayed. This signals that you have either not
yet updated the configuration or have selected the wrong project.
Overview
Events on the security module can be logged. Depending on the event type, they are stored
in volatile or non-volatile buffers. As an alternative, you can also record on a network server.
The security module recognizes the following events for both logging methods:
If necessary, you can modify these configured log settings in the online functions. This does
not change the settings in the project configuration.
Line diagnostics Line diagnostics generates a Using the severity, you weight the system
special system event. Set the events of line diagnostics relative to the se-
percentage of bad frames as of verity of the other system events.
which a system event is generat- Note
ed. Assign a facility and a severi-
Assign the system events of line diagnostics
ty to the system event.
a lower severity than the filtering of system
events. Otherwise, these events will not pass
through the filter and are not logged.
Note
Firewall - Syslog server not active in the external network
If the Syslog server is not enabled on the addressed computer, this computer generally
returns ICMP responses "port not reachable". If these reply frames are logged due to the
firewall configuration and sent to the Syslog server, the procedure can become never ending
(storm of events).
Remedies:
• Start the Syslog server;
• Change the firewall rules;
• Take the computer with the disabled Syslog server out of the network.
Note
No return to standard mode possible
If you switch to the advanced mode and change the configuration for the current project,
you can no longer switch back.
Remedy SCT standalone: You close the project without saving and open it again.
The Syslog server must be reachable from the security module using the specified IP
address, if necessary using the router configuration in the "Routing" tab. If the Syslog server
cannot be reached, the sending of Syslog information is disabled. You can recognize this
operating situation based on the system messages. To enable the sending of Syslog
information again, you may need to update the routing information and restart the security
module.
If you enable the "Use symbolic name in logging" option, the address information of the log
frames transferred to the Syslog server is replaced by symbolic names. The security module
checks whether corresponding symbolic names have been configured and enters these in
the log frames.
Note
Longer a processing time when using symbolic names
If the "Use symbolic name in logging" check box is selected, the processing time on the
security module is increased.
The module names are automatically used as symbolic names for the IP addresses of the
security modules. In routing mode, these names have a port name added to them as follows:
"Modulename-P1", "Modulename-P2" etc.
Line diagnostics Line diagnostics generates a special Using the severity, you weight the sys-
system event. Set the percentage of tem events of line diagnostics relative to
bad frames as of which a system the severity of the other system events.
event is generated. Assign a facility Note
and a severity to the system event.
Assign the system events of line diag-
nostics a lower severity than the filtering
of system events. Otherwise, these
events will not pass through the filter and
are not recorded by the Syslog server.
Note
A.2 Range of values for IP address, subnet mask and address of the
gateway
Note:
You can also enter a value between 224 and 255 for the first decimal number of the IP
address. This is, however, not advisable since this address range is reserved for other tasks
and with some configuration tools (e.g. STEP 7), there is no check of these values.
See also
Link to the documentation:
(http://www.automation.siemens.com/simatic/portal/html_00/techdoku.htm)
/1/
SIMATIC NET
S7 CPs for Industrial Ethernet
Configuring and Commissioning
Manual Part A - General Applications
Configuration Manual
Siemens AG
30374198 (http://support.automation.siemens.com/WW/view/en/30374198)
/2/
SIMATIC NET
S7CPs for Industrial Ethernet
Manual Part B
Manual
Siemens AG
(SIMATIC NET Manual Collection)
You will find the manuals for the individual CPs under the following entry IDs:
CP 343-1 Advanced (GX31): 28017299
(http://support.automation.siemens.com/WW/view/en/28017299)
CP 443-1 Advanced (GX30): 59187252
(http://support.automation.siemens.com/WW/view/en/59187252)
/3/
SIMATIC NET
NCM S7 for Industrial Ethernet
Primer
Siemens AG
(part of the online documentation in STEP 7)
/4/
SIMATIC NET
Commissioning PC Stations - instructions and getting started
Configuration manual
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under following entry ID:
13542666 (http://support.automation.siemens.com/WW/view/en/13542666)
/5/
SIMATIC
Configuring Hardware and Connections with STEP 7
Siemens AG
Part of the documentation package "STEP 7 Basic Knowledge"
(Part of the online documentation in STEP 7)
/6/
SIMATIC S7
Siemens AG
● S7-300 automation system
– CPU 31xC and 31x Installation: Operating Instructions
Link: 13008499 (http://support.automation.siemens.com/WW/view/en/13008499)
– Module Data: Reference Manual
Link: 8859629 (http://support.automation.siemens.com/WW/view/en/8859629)
● Automation system S7-400, M7-400
– Installation: Installation Manual
Link: 1117849 (http://support.automation.siemens.com/WW/view/en/1117849)
– Module Data: Reference Manual
Link: 1117740 (http://support.automation.siemens.com/WW/view/en/1117740)
/7/
SIMATIC NET
Twisted-Pair and Fiber-Optic Networks Manual
Siemens AG
(SIMATIC NET Manual Collection)
/8/
SIMATIC
Communication with SIMATIC
system manual
Siemens AG
Entry ID:
25074283 (http://support.automation.siemens.com/WW/view/en/25074283)
/9/
Documentation package "STEP 7 Basic Knowledge"
● Working with STEP 7 Getting Started (ID: 18652511
(http://support.automation.siemens.com/WW/view/en/18652511))
● Programming with STEP 7 (ID: 18652056
(http://support.automation.siemens.com/WW/view/en/18652056))
● Configuring Hardware and Connections with STEP 7 (ID: 18652631
(http://support.automation.siemens.com/WW/view/en/18652631))
● From S5 to S7, Converter Manual (ID: 1118413
(http://support.automation.siemens.com/WW/view/en/1118413))
Siemens AG
Order number 6ES7 810-4CA08-8AW0
(part of the online documentation in STEP 7)
/10/
SIMATIC NET
Industrial Ethernet Network Manual
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under the following entry ID: 27069465
(http://support.automation.siemens.com/WW/view/en/27069465)
/11/
SIMATIC NET
Commissioning PC Stations - Manual and Quick Start
Configuration Manual
Siemens AG
13542666 (http://support.automation.siemens.com/WW/view/en/13542666)
/12/
SIMATIC NET Industrial Ethernet CP 1628
Compact Operating Instructions
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under the following entry ID: 56714413
(http://support.automation.siemens.com/WW/view/en/56714413)
/13/
SIMATIC NET Industrial Ethernet Security
SCALANCE S as of V3.0
Commissioning and installation manual
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under the following entry ID: 56576669
(http://support.automation.siemens.com/WW/view/en/56576669)
/14/
SIMATIC NET Industrial Remote Communication
SCALANCE M-800
Configuration Manual
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under the following entry ID: 78389151
See also
78389151 (http://support.automation.siemens.com/WW/view/en/78389151)
/15/
SIMATIC NET
Telecontrol SCALANCE M875
Operating Instructions
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under the following entry ID: 58122394
(http://support.automation.siemens.com/WW/view/en/58122394)
* C
*.cer, 236, 257 CA certificate, 85, 89
*.dat, 257 CA group certificate, 89
*.p12, 89, 236, 257 Certificate, 86, 212
Exporting, 85
Importing, 85
3 Renewing, 88
Replace, 89
3DES, 221
Replacing, 89
Certificate manager, 86
Certification authority, 85, 86
A
CHAP, 103
Access protection, 44 Configurable properties, 259
Active nodes, 229 Configuration data
Address of the gateway, 288 Load, 260
Address parameters, 94 Configuration rights, 76
Address range, 161 Configuring time-of-day synchronization, 199
Administrator, 73 Connection rules, 152
Advanced Encryption Standard (AES), 221 Consistency check, 69, 110, 196
Advanced mode, 46 local, 67
DHCP server, 193 project-wide, 67
Firewall rules, 136 Content area, 94
Global firewall rules, 137 CP 1628
Local logging, 276, 278 Purpose, 41
Logging, 284 CP x43-1 Adv.
Network Syslog, 276 Purpose, 38
User-specific firewall rules, 149 C-PLUG, 44, 66
AES, 202, 221 Creating a route, 174
Aggressive mode, 221
Applet, 77
ARP, 211 D
ARP proxy, 203
Data Encryption Standard (DES), 222
Audit events, 277
Data espionage, 30
Authentication, 71
DCP (Primary Setup Tool), 170
Authentication method, 212, 219
Dead peer detection (DPD), 230
Autocrossover, 102
Default firewall setting
Automatic firewall rules, 152
CP 1628, 123
Autonegotiation, 102
CP x43 Adv., 117
Default initialization values, 66
Dependencies of rights, 78
B
DES, 202, 222
Bandwidth, 156, 166 Detect members, 262
Bridge mode, 99 Device rights, 76
Broadcast, 176
Buffer, 277
DHCP Glossary, 9
Server configuration, 193 Group assignments, 62
Symbolic names, 68 Group name, 162, 168
DHCP server, 194
Diagnostics, 273
Diagnostics user, 73 H
Diffie-Hellman key agreement, 221
Half duplex, 99
DNS conformity, 287
I
E
ICMP, 154
Enabling the firewall
ICMP services, 163
CP 1628, 117
IEEE 802.3, 31, 115
CP x43-1 Adv., 117
IKE, 118, 124
SCALANCE S V3, 133
IKE settings, 219
Enabling tunneled communication
Installation
CP x43-1 Adv., 117
SCALANCE S, 47
SCALANCE S V3, 133
Interface routing, 92, 99
Encryption, 47, 66
Interfaces, 173
ESP protocol, 118, 124, 222
Internal network nodes
Ethernet non IP frames, 115
Configuring, 242
Exporting an NTP server, 201
CP x43-1 Adv., 40
External network nodes
SCALANCE 602, 29
CP x43-1 Adv., 40
SCALANCE S612 / S623 / S627-2M, 32
SCALANCE 602, 29
Internet Key Exchange (IKE), 221
SCALANCE S612 / S623 / S627-2M, 32
IP access control list, 77
IP access protection, 59
IP address, 160, 287
F
IP blacklist, 275
Facility, 282 IP packet filter
Firewall, 31 local, 154
Advanced mode, 136 IP packet filter rules, 155
Firewall rules, 115 CP 1628, 157
Symbolic names, 68 CP x43-1 Adv., 157
Firewall rule sets SCALANCE S, 157
Global, 62 IP protocol, 136
User-defined, 149 IP rule sets, 137
Firmware version, 3 User-specific, 149
Flat network, 99 IP services, 162
FTP, 77 IPsec settings, 219
FTP/FTPS, 59 IPsec tunnel, 209
FTPS certificates, 85 ISAKMP, 231
Full duplex, 99 ISO protocol, 245
ISP account, 103
G
L
Ghost mode, 100
Global firewall rule sets, 164 Layer 2, 115, 136, 211
Global firewall rules, 137 Layer 3, 115, 136
Assigning, 139 Layer 4, 115
Global packet filter rules, 139 Learning mode, 244
V
VLAN operation, 212
VLAN tagging, 212
VPN, 26, 209
Module-specific properties, 230
SOFTNET Security Client, 253
VPN device, 92
Module certificate, 239
VPN group, 216
W
WAN IP address
Specifying, 231