QNET PROFIBUS


Security Level

Definition

Estimated Value

Rationale

SL-C Component

Intrinsic security capability of the QNET gateway

SL2

By disabling SNMP/DCP and securing the infrared interface, the component can resist simple, intentional misuse. However, it still lacks intrinsic cryptographic features (due to CC-B) needed for full SL-C 3.

SL-T 

Target System

Security level achieved by the Zone/Conduit

SL2 / SL3

With a robust component configuration (SL-C 2) and the inclusion of network countermeasures (VPN/Firewall), the overall system can confidently achieve SL-T 2 and, with strong cryptographic implementation on the Conduit, potentially reach SL-T 3.


By deactivating weak standard services (SNMP, DCP) and protecting the integrated infrared interface, the key requirements of PROFINET security class 1 (robustness) can be met, can achieve a target security level (SL-T) of SL2 if it operates in a segregated network that uses firewalls or VPNs for public access.


Foundational

Requirement

SL-C
Component Capability

Network Measures

SL-T
Target Level Achieved

FR1 - IAC

Identification and Authentication Control 

Weak/Implicit

PROFINET only has basic device ID.

VPN/IPsec or TLS on the Conduit for strong, cryptographic authentication of connecting clients.

SL2

identification and authentication ensured by Conduit

FR2 - UC

Use Control

DCP/SNMP disabled

limiting configuration/management access via standard network services.

Deep Packet Inspection (DPI) Firewall filters PROFINET I/O data and prevent unauthorized commands from reaching the gateway's real-time functions.

SL2

DPI for I/O data provided by Conduit

FR3 - SI

System Integrity

Robust  against simple network attacks (PROFINET Netload Robustness) due to disabling SNMP/DCP.

VPN/IPsec on the Conduit to provide cryptographic integrity checks for all data transmission over the network, preventing intentional manipulation.

SL2

Integrity ensured by the transport layer


FR4 - DC

Data Confidentiality

Absent

PROFINET/TraxBus data is clear-text by default.

VPN/IPsec: Required to encrypt all traffic entering/exiting the Zone boundary.

SL2

Depends entirely on the Conduit for encryption

FR5 - RDF

Restricted Data Flow

Standard PROFINET.

Zone and Conduits Architecture: The segregation (physical/logical) and Firewall rules are the primary control for flow restriction.

SL2/SL3

Achieved by the overall network architecture (IEC 62443-3-3)

FR6 - TRE

Timely Response to Events

No SNMP/DCP means fewer network services to monitor, and robust operation is expected.

Logging and Monitoring on the Firewall/IPS to register denied access attempts and filter events related to PROFINET I/O.

SL2

Logging is done by the Conduit, but the cleaner component configuration reduces noise

FR7 - RA

Resource Availability

Disabling SNMP/DCP reduces the component's attack surface and increases robustness against simple DoS attacks.

Rate Limiting on the Firewall to block flooding of real-time or management requests aimed at overwhelming the gateway.

SL2

rate limiting required for SL2/3


The interface meets or exceeds SL2 for all analyzed Fundamental Requirements.

The security strategy is defined by the deployment environment:

  • Segregated Industrial Environment: When operating within an isolated and protected industrial network, the interface's native features are sufficient. No additional measures or external devices are required.
  • External Network Extension: If control or access is extended to external networks (IT or Cloud), a dedicated Conduit must be implemented to achieve a System Target Security Level (SL-T) of SL2 or SL3.