PROFIBUS DP, the serial fieldbus whose user organization PI (PROFIBUS & PROFINET International) was founded in 1989 and which is now formally specified as IEC 61158 Type 3, still runs an estimated 71 million devices worldwide by PI's own self-reported April 2026 count — yet its base protocol has no built-in authentication, encryption or session concept of any kind. PI's own technical documentation confirms the gap by omission: it describes the fieldbus's master/slave architecture, RS-485 wiring and data rates in detail but never mentions a credential, key or identity check. PROFIBUS predates PI's Ethernet-based successor, PROFINET, by more than a decade, and PROFINET is where PI eventually layered security extensions on — not the older PROFIBUS DP specification, which never received an equivalent retrofit, even as new PROFIBUS installations now decline in favor of PROFINET and Ethernet-APL.
Key takeaways
- PROFIBUS DP ("Decentralized Periphery") is the main variant of PROFIBUS, the serial fieldbus PI maintains alongside its Ethernet-based PROFINET.
- No. PI's technology page covers wiring, speeds and device limits but never mentions authentication, encryption, access control or a credential.
- The clearest peer-reviewed treatment is Watson, Lou and Gao's 2017 SECRYPT paper.
- The PROFIBUS protocol itself has no CVE, but PROFIBUS-connected Siemens products appear in CISA advisories, either as the affected device or as an attack path.
What is PROFIBUS DP, and what does PI's own documentation say about it?
PROFIBUS DP ("Decentralized Periphery") is the main variant of PROFIBUS, the serial fieldbus PI maintains alongside its Ethernet-based PROFINET. Per PI's technology page, PROFIBUS DP uses "the standard copper-based RS485 interface," with "an intrinsically safe version RS485-IS" for hazardous areas, supports "data rates from 9.6 KBit/s to 12 MBit/s," and connects "up to 126 I/O devices" to one cable. Cyclic exchange carries routine I/O; acyclic exchange carries diagnostics and parameterization.
The bus combines master/slave polling with token passing: a DP Master Class 1 runs cyclic I/O, an optional Class 2 master handles engineering and diagnostic access, and the masters pass a token in ascending station-address order to decide who may transmit. Slaves answer only when polled. Any station that can transmit on the shared bus can, in principle, behave as if it belongs there — the property later research flagged.
PI's specification page states that PROFIBUS "is specified in IEC 61158 Type 3 and IEC 61784," that Type 3 covers DP-V0, DP-V1 and DP-V2, and that IEC 61784 defines "Communication Profile Family CPF 3 which is PROFIBUS." The IEC texts are sold, not free: the data-link-layer part, IEC 61158-3-3:2014, lists at CHF 380 on the IEC Webstore. The architecture described here comes from PI's free summaries, not from the IEC text.
Does PROFIBUS DP have any built-in security?
No. PI's technology page covers wiring, speeds and device limits but never mentions authentication, encryption, access control or a credential. PI's security page is built around PROFINET — IEC 62443-4-2 alignment, TLS, onboarding, certificates and post-quantum preparation — and its main PROFIBUS line is: "Security does not only concern Ethernet-based systems— IO-Link and PROFIBUS must also be considered for comprehensive protection."
What PI offers for PROFIBUS today is process, not protocol. The page lists a joint working group with FieldComm Group, ODVA and the OPC Foundation on "Device / tool security for non-Ethernet-based protocols," whose stated activity is "high level threat risk assessments," and a 2022 atp magazine paper on attack scenarios for systems using HART, PROFIBUS PA and Ethernet-APL. The same four organisations released "Secure Deployment of Industrial Communication Protocols: A Risk-Based Approach" (V1.00, dated 22 April 2026 on its download page), which addresses "legacy protocols that lack built-in security mechanisms such as authentication, authorization, integrity, and confidentiality" in alignment with EN 40000-1-2. None of these defines a PROFIBUS authentication mechanism or a PROFIBUS equivalent of PROFINET's Security Classes.
What does published research say PROFIBUS's lack of security actually enables?
The clearest peer-reviewed treatment is Watson, Lou and Gao's 2017 SECRYPT paper. Its abstract states: "Similar to network protocols developed then, availability is the security objective prioritized in the PROFIBUS design." The body spells out the consequence: "Lack of authorization and authentication control suggests that a rogue device can be connected to and communicate on PROFIBUS, gaining access to the clear-text telegrams." With access to a master, an attacker can "monitor the network communication, map the network topology and spoof and/or capture, interpret and use the commands observed."
The paper cites Stuxnet as the known case: the worm "monitored the clear-text communication on a PROFIBUS DP network, waiting for specific data before executing its payload." It also explains why authentication was never retrofitted: cryptography adds processing time, and the paper puts the preferred PROFIBUS bus cycle at "less than 10ms" at field level. Its conclusion is that "a defense-in-depth approach is more feasible security solution, with strong security controls being implemented at networks interconnecting with the PROFIBUS networks."
A 2024 Politecnico di Milano thesis by Alessio Alfonsi on PROFIBUS and PROFIsafe describes "reparameterization" attacks that exploit error handling at the UART level and notes the "lack of arbitration mechanisms in RS-485." These technique names come from a single thesis and are pointers for further reading, not independently confirmed findings.
Which CISA advisories involve PROFIBUS hardware?
The PROFIBUS protocol itself has no CVE, but PROFIBUS-connected Siemens products appear in CISA advisories, either as the affected device or as an attack path. From CISA's CSAF records:
| Advisory | Product | CVE (CVSS v3) | PROFIBUS role | Fix |
|---|---|---|---|---|
| ICSA-15-335-03 (Update C) | SIMATIC CP 342-5, CP 342-5 FO, CP 443-5 Basic/Extended, SIPLUS variants | CVE-2015-8214, CWE-306 (8.8 for these CPs) | "Potential exploitation requires access to the PROFIBUS network" | None for the PROFIBUS CPs; Ethernet CPs fixed |
| ICSA-16-161-01 | S7-300 CPUs | CVE-2016-3949 (7.5) | Packets "sent to Port 102/TCP (ISO-TSAP) or via Profibus" cause defect mode | V3.2.12 for CPUs with PROFINET, V3.3.12 for CPUs without (Siemens SSA-818183) |
| ICSA-19-043-04 | S7-300 CPUs | CVE-2018-16561 (7.5) | Crafted S7 packets via "Ethernet, PROFIBUS, and Multi Point Interfaces (MPI)" | V3.X.16 |
| ICSA-18-317-02 | S7-400 CPUs | CVE-2018-16556 (7.5), CVE-2018-16557 (8.2) | Port 102/tcp via "Ethernet, PROFIBUS or Multi Point Interfaces" | Per CPU line; some lines have no fix |
ICSA-15-335-03 is the one a PROFIBUS owner should read closely. The 2021 update "added SIMATIC NET CP PROFIBUS devices," and the July 2025 update clarified that the CP 342-5 and CP 443-5 families get no fix. The weakness is missing authentication for administrative operations on the CP, and on those CPs the attacker has to be on the PROFIBUS segment. Several PROFINET DCP advisories (for example ICSA-17-129-02) state the reverse: "PROFIBUS interfaces are not affected."
How do PROFIBUS PA and PROFIsafe change the picture?
They change the physics and the safety case, not the security model. PROFIBUS PA, the process-automation variant, uses MBP (Manchester Coded Bus Powered) transmission, which per PI's technology page "provides a typical supply current of 10 - 15 mA on the bus cable" to power the field device itself, and reaches DP through a coupler or link. PI's April 2026 release counts 18 million PA devices, with 700,000 added in the last year. The current PA profile, V3.02, lets a replacement device take over "the role of the predecessor device" automatically — convenient for maintenance, and a reminder that nothing in PI's summary describes a device identity check on the PA segment.
PROFIsafe is a functional-safety layer, not a security layer. PI's PROFIsafe page describes the "black channel principle": PROFIsafe treats the transmission path below it as untrusted and detects errors end to end, for applications "up to SIL3 according to IEC 61508 / IEC 62061." That design protects against random faults; the Alfonsi thesis above is about what happens when someone deliberately manipulates that error handling. PI counts 31.5 million PROFIsafe nodes in its April 2026 release.
For a security review this means three things: count the DP/PA couplers among your bridge devices, do not cite PROFIsafe's SIL rating as evidence of protection against an attacker, and keep safety and security assessments for the same segment linked, as IEC 62443-3-2 zone risk assessments expect.
PROFIBUS DP vs. PROFINET: how does the security picture actually compare?
| PROFIBUS DP | PROFINET | |
|---|---|---|
| Standardized as | IEC 61158 Type 3 / IEC 61784 CPF 3 | IEC 61158 Type 10 / IEC 61784 CPF 3 |
| Physical layer | RS-485 serial copper (MBP for PA) | Standard Ethernet |
| Reachable from an IP network without a gateway? | No | Yes |
| Native authentication/encryption | None in the base protocol | None in base DCP; PI's Security Classes add it where both ends support them |
| CISA advisories | PROFIBUS CPs in ICSA-15-335-03; PROFIBUS as an attack path in S7-300/400 advisories | Many against PROFINET-speaking devices (ICSA-21-194-03, ICSA-19-283-02, ICSA-18-079-02 and others) |
| Installed base (PI self-reported, April 2026) | 71 million PROFIBUS devices, 18 million of them PA | See the PROFINET security guide |
Neither protocol authenticates at the base level. The difference is reach: a PROFIBUS segment is reachable only through its wiring or through a device that bridges it to Ethernet, while PROFINET is reachable wherever its VLAN extends. That makes the gateway, coupler or communication processor the realistic point of attack, and the place where a device maker's firmware practice matters most.
How do you segment a PROFIBUS network through its gateways?
Treat every device with one foot on Ethernet and one on PROFIBUS as a zone boundary, the same way the Purdue model treats a cell-area firewall:
List every bridge device: S7 CPUs with DP ports, CPs such as the CP 342-5, PROFINET-to-PROFIBUS proxies, DP/PA couplers and third-party gateway modules. Put each bridge's Ethernet side in its own zoneand allow only the engineering stations and HMIs that need it. For Siemens devices that means ISO-TSAP on 102/tcp (see the S7comm security guide). Block engineering access from the business network; use a jump host for remote programming. Keep PROFIBUS segments physically separate per cell, and lock cabinets, repeaters and terminators: on an unauthenticated bus, physical access is the access control. Patch the bridges, not the busEvery fix in the table above is a CPU or CP firmware update. Where no fix exists, as for the PROFIBUS CPs in ICSA-15-335-03, record a compensating control (zone, physical access, replacement date) in your risk register.
What does a PROFIBUS exposure review look like? (worked example)
Synthetic example, not a real plant. A water utility reviews one pumping station:
| Device (synthetic) | Link | Advisory match | Decision |
|---|---|---|---|
| S7-300 CPU, firmware 3.3.10 | Ethernet + DP | ICSA-16-161-01 (fixed in 3.3.12), ICSA-19-043-04 | Update firmware at next outage |
| CP 342-5 PROFIBUS CP | DP | ICSA-15-335-03, no fix | Restrict who reaches the CPU on 102/tcp; budget replacement |
| DP/PA coupler | DP to PA | None found | Keep in locked cabinet |
| Engineering laptop | Ethernet | Reaches CPU from office VLAN | Move behind jump host |
The PROFIBUS cable itself produced no finding; every action sits on a device that connects to Ethernet.
What should a device maker or asset owner actually check first?
Identify every PROFIBUS-to-Ethernet gateway, coupler or master module, since that is almost always the real attack surface. Treat PROFIBUS traffic as unauthenticated and readable: any station that can transmit can act as a master or disrupt the token. Restrict physical access to wiring, junction boxes and terminators For any gateway or coupler you build and ship, apply normal firmware discipline: an SBOM, scanning the gateway's software stack for known vulnerabilities, and a PSIRT process for reports — the gateway's firmware, not RS-485, is where advisories land. Plan migration deliberatelyPI reports that "the expected gradual decline in new installations is confirmed," linked to Ethernet-APL; budget replacement or gateway coexistence for an installed base that will run for years. HART brownfield sites face the same choice.
What are the common pitfalls?
- "No CVE for PROFIBUS" read as "nothing to patch." The CPUs and CPs on the bus carry the CVEs.
- Searching advisories for the word "PROFIBUS" in titles only. ICSA-15-335-03's title says "Communication Processor."
- Relying on a mirror port. RS-485 traffic never reaches an Ethernet capture.
- Assuming PROFINET security covers PROFIBUS behind a proxy. Security Classes stop at the proxy.
SoftWSP's OT Snapshot reads a mirror-port capture of the Ethernet side and lists which hosts talk to which, including S7comm sessions to CPUs and CPs and remote-access protocols crossing a boundary; it does not identify device models or see the PROFIBUS segment itself — see OT Snapshot. For a gateway or coupler maker, device firmware security reads the product's firmware SBOM and matches it against NVD, CISA KEV, FIRST EPSS and CISA's ICS advisories, with an AI-drafted, cited report an engineer reviews. For the wider architecture, see NIST SP 800-82 (NIST publication page).
This guide draws on PI's PROFIBUS technology, specification, security and download pages, PI's April 2026 press release, the Watson/Lou/Gao 2017 SECRYPT paper, a 2024 Politecnico di Milano thesis, the IEC Webstore record for IEC 61158-3-3, and CISA's CSAF and web records for the advisories listed, each read on 14 November 2026. PI's installed-base figures are self-reported. It is not a substitute for a current advisory search against your exact hardware.
Put this guide to work
Frequently asked questions
Does PROFIBUS DP have any built-in authentication or encryption?
No. PI's (PROFIBUS & PROFINET International) own technical overview of PROFIBUS, fetched directly from profibus.com, describes the protocol's master/slave communication model, its RS-485 copper physical layer with data rates "from 9.6 KBit/s to 12 MBit/s," and support for "up to 126 I/O devices" on a single PROFIBUS DP segment — but contains no mention of authentication, encryption or any credential concept anywhere in that description. PI's dedicated security page, which covers PROFINET's Security Classes in detail, names PROFIBUS in one passing sentence: "Security does not only concern Ethernet-based systems—IO-Link and PROFIBUS must also be considered for comprehensive protection." Elsewhere it lists a joint working group on security for non-Ethernet protocols, whose stated activity is high-level threat risk assessment, and a paper on attack scenarios that include PROFIBUS PA; none of these defines a PROFIBUS security mechanism. This is consistent with the protocol's history: PROFIBUS's user organization was founded in 1989, more than a decade before cybersecurity was a design consideration for industrial fieldbus protocols, and more than a decade before PI itself built PROFINET — PROFIBUS's Ethernet-based successor, released in 2003 — as a protocol PI could add security features to over time. PROFIBUS DP's base specification never received an equivalent retrofit.
Are there real CISA ICS advisories against PROFIBUS specifically?
None that this guide could find with PROFIBUS as the advisory's primary named subject. Repeated, deliberate site and vendor-specific searches of cisa.gov's ICS advisory archive turned up PROFIBUS mostly mentioned incidentally, as one of several physical interfaces (alongside Ethernet and MPI) on Siemens SIMATIC S7-300/S7-400 controllers affected by unrelated vulnerabilities — for example, advisories describing crafted packets "sent to Port 102/TCP (ISO-TSAP) or via Profibus," where PROFIBUS is named as an alternate delivery path for a flaw that actually lives in the controller's own packet handling, not in the PROFIBUS protocol itself. The exception is ICSA-15-335-03 (CVE-2015-8214, missing authentication), which since its 2021 and 2025 updates lists Siemens SIMATIC CP 342-5 and CP 443-5 PROFIBUS communication processors as affected, with no fix for them, and notes that exploitation "requires access to the PROFIBUS network." This largely negative result is itself informative and consistent with how PROFIBUS is deployed: it is a closed, serial, non-routable fieldbus with no native IP stack, so the kind of remotely-exploitable, internet-reachable vulnerability that drives most CISA ICS advisories simply has a much smaller attack surface to report on PROFIBUS segments compared to Ethernet-based protocols like PROFINET, Modbus TCP or MQTT. It does not mean PROFIBUS traffic is safe from spoofing or disruption — see the next answer — it means the usual advisory pipeline, which tracks exploitable implementation bugs in specific products, has little PROFIBUS-specific material to report because PROFIBUS was never designed to be remotely reachable in the first place.
What does published security research say about PROFIBUS DP's actual weaknesses?
The most directly relevant peer-reviewed source is Watson, Lou and Gao's "A Review of PROFIBUS Protocol Vulnerabilities – Considerations for Implementing Authentication and Authorization Controls," presented at the 14th International Joint Conference on e-Business and Telecommunications (ICETE 2017, SECRYPT track) and published by SciTePress. Its abstract states plainly that "similar to network protocols developed then, availability is the security objective prioritized in the PROFIBUS design," and the paper's conclusion recommends a defense-in-depth approach, "with strong security controls being implemented at networks interconnecting with the PROFIBUS networks," precisely because the protocol itself cannot be retrofitted with authentication. Independent technical summaries corroborating this same theme describe PROFIBUS as lacking authentication inherent to its token-passing bus-arbitration mechanism, meaning a node that is able to transmit on the bus — whether a legitimate device or one physically or electrically spliced onto the RS-485 segment — can impersonate a master and gain control over configured slaves, or capture and inject tokens to disrupt bus communication and cause denial-of-service. A 2024 Politecnico di Milano thesis by Alessio Alfonsi examining PROFIBUS and the related PROFIsafe safety layer describes further "Reparameterization Attack" techniques exploiting error-management and UART-level weaknesses, and separately notes the "lack of arbitration mechanisms in RS-485" as a contributing risk factor. These specific attack-technique names come from a single 2024 thesis and are offered as pointers to further primary reading rather than independently confirmed findings. The consistent theme across all of these sources is that PROFIBUS's vulnerability is structural — no credential concept exists to break — rather than any one implementation bug.
How widely is PROFIBUS DP still deployed today, and is that figure independently verified?
PI's own press material, the only source this guide could find for installed-base figures, reported in an April 2026 release that "1 million devices were commissioned" in the prior year, "bringing the total to 71 million," with the process-automation variant PROFIBUS PA separately reaching 18 million units after 700,000 new commissions. The same release states plainly that "the expected gradual decline in new installations is confirmed, though without any abrupt changes" and attributes that decline directly to migration: "The decline is directly linked to the technological transition to Ethernet-APL, which continues to gain momentum." PI nonetheless argues PROFIBUS "continues to play a significant role in many plants — particularly in long-running processes, expansions, and replacement projects." Every one of these figures is self-reported by PI, the vendor consortium that maintains and markets PROFIBUS, with no independent third-party audit this guide could locate. The 71-million figure is a directionally useful indicator of scale from the party with the most direct interest in it, not externally verified data. What is independently verifiable is the trend direction: PI's own numbers show new PROFIBUS commissions declining year over year as Ethernet-APL and PROFINET adoption grows, even as the installed base of already-deployed PROFIBUS devices remains very large and will stay in service for years given typical process-industry replacement cycles.
How is PROFIBUS DP different from PROFINET, and does that change the security response?
PROFIBUS DP and PROFINET are both maintained by PI, but they are different protocols on different physical layers with different security starting points. PROFIBUS DP, specified as IEC 61158 Type 3 and part of IEC 61784's Communication Profile Family 3, is a serial fieldbus running over RS-485 copper (or, in process-automation variants, Manchester-coded bus-powered wiring) with a shared, token-passing bus and no IP stack — it is not reachable from a corporate network or the internet without a protocol gateway, because it simply is not Ethernet. PROFINET, released in 2003 as PROFIBUS's Ethernet-based successor, runs standard IP networking and inherited the opposite problem: its Discovery and Configuration Protocol (DCP) has no authentication either, but because PROFINET traffic rides ordinary Ethernet, it is reachable anywhere that network segment is reachable, which is exactly why a decade of CISA advisories exists against PROFINET-speaking Siemens products (see the [PROFINET security guide](/guides/profinet-protocol-security-ot-ics/) for that record) with essentially nothing comparable for PROFIBUS. The practical consequence: PROFIBUS's serial, non-routable physical layer is itself a form of de facto segmentation that PROFINET's Ethernet physical layer does not provide, which is why the compensating controls differ — a PROFIBUS segment's real exposure is almost always at the gateway or coupler where it bridges to Ethernet, not on the RS-485 wire itself, whereas PROFINET's exposure exists anywhere its VLAN reaches.
Sources
- PI (PROFIBUS & PROFINET International): PROFIBUS technology overview — master/slave architecture, RS-485, data rates, device counts
- PI: PROFIBUS DP Standard specification download page — IEC 61158 Type 3 / IEC 61784 CPF 3 reference
- PI: PI Security page — PROFINET Security Classes, IEC 62443 alignment, single mention of PROFIBUS/IO-Link
- PI: Press release — "Strong foundation, clear direction: PI continues growth in automation" (April 2026) — 71 million installed PROFIBUS devices, decline trend
- Watson, Lou & Gao: "A Review of PROFIBUS Protocol Vulnerabilities – Considerations for Implementing Authentication and Authorization Controls," ICETE 2017 / SECRYPT, SciTePress (DOI 10.5220/0006426504440449)
- Alfonsi: "Novel attack strategies targeting PROFIbus and PROFIsafe – Exploiting Error Management Vulnerabilities," Politecnico di Milano thesis (2024)
- IEC: IEC 61158-3-3:2014, Part 3-3: Data-link layer service definition — Type 3 elements (PROFIBUS), catalogue record, Edition 2.0, TC 65/SC 65C
- NIST Special Publication 800-82 Revision 3, Guide to Operational Technology (OT) Security (September 2023)
- CISA CSAF: ICSA-15-335-03 (Update C) — Siemens SIMATIC Communication Processor, CVE-2015-8214, PROFIBUS CPs CP 342-5 / CP 443-5 with no fix
- CISA: ICS Advisory ICSA-16-161-01 — Siemens SIMATIC S7-300 denial of service via Port 102/TCP or PROFIBUS (CVE-2016-3949)
- Siemens ProductCERT SSA-818183: Denial-of-Service Vulnerability in SIMATIC S7-300 CPU Family (V1.1, 10 February 2020)
- PI, FieldComm Group, ODVA, OPC Foundation: Secure Deployment of Industrial Communication Protocols — A Risk-Based Approach, V1.00 (download page, 22 April 2026)
- PI: PROFIsafe technology page — black channel principle, SIL 3
About this guide
SoftWSP OT/ICS Desk
Covers the OT/ICS security cluster: 87 guides.

In this cluster
Questions about this page?
