Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A historian server is the time-series database that records every process measurement with a timestamp, serving engineering analysis and reporting, and sitting on the boundary between plant and business networks.

What Is a Historian Server?
A historian is the plant’s memory. It subscribes to thousands or hundreds of thousands of process tags, records each value with a timestamp and a quality flag, compresses the stream so that decades of data fit on reasonable storage, and serves it back to anyone who needs to know what the plant was doing at 03:40 last Tuesday. The familiar platforms are the PI System from AVEVA, AVEVA Historian from the former Wonderware line, GE Proficy, Honeywell’s process data historian, and increasingly open time-series databases in newer installations.
Engineers use it for troubleshooting and performance analysis, production uses it for yield and downtime reporting, maintenance uses it for condition monitoring, energy teams use it for consumption reporting, and regulators use it, indirectly, for evidence. In pharmaceutical and food manufacturing the historian holds batch records; in energy and water it holds the data behind statutory returns; in emissions-regulated plant it holds the monitoring record. The integrity of those records is a compliance matter, not only an engineering one.
The historian is almost always the busiest legitimate crossing point between the control network and the business network. Everyone wants its data, nobody wants them on the plant network to get it, and the result is an architecture with the historian collecting inside and publishing outside. That makes it the first thing an attacker who lands in the corporate estate finds with a path toward the process, and the first thing an attacker inside the plant finds with a path outward for exfiltration.
Three specific weaknesses recur:
Vendor advisories for historian platforms appear regularly through the national industrial advisory channels, including flaws reachable without authentication, so the platform needs patching like any other server even though it lives in a network nobody wants to touch.
One practical issue deserves a mention because it caught a great many sites unprepared. Many historians collect from control systems using OPC Data Access, which is built on Microsoft DCOM. Microsoft progressively hardened DCOM authentication through updates from 2021 onwards, with enforcement becoming mandatory in March 2023, and a large number of OPC DA connections stopped working as a result. Sites that had treated the collection path as untouchable infrastructure discovered that it depended on a weak authentication mode. The episode is a good argument for migrating collection to OPC UA, which authenticates properly, works through firewalls without DCOM’s port behaviour, and does not depend on Windows domain trust across a security boundary.
At Privia Security, we review historian architectures and the plant-to-business boundary through our Infrastructure and Architecture Review Services.
The collecting instance belongs inside the control zone, close to the systems it polls, and a replica belongs in the industrial demilitarised zone for business consumers. Replication should run outward only. Placing a single historian on the business network and letting it poll controllers directly creates an inbound path from corporate IT to the process, which is the architecture most incidents rely on.
Because it legitimately talks to both sides. It holds credentials for control systems, it is trusted by business reporting tools, and it usually exposes web and database interfaces that are reachable from ordinary corporate workstations. An attacker does not need an exotic exploit if a shared service account on an interface node has write access to the control network.
Yes. Most platforms allow authorised users to backfill, edit, or delete archived values, which exists for legitimate reasons such as correcting a failed collection period. Where the data supports regulatory reporting, batch records, or emissions returns, restrict that permission to named individuals, log every such operation, and reconcile the archive against an independent copy.
Where the equipment supports it, yes. OPC DA relies on DCOM, which Microsoft has hardened to the point of breaking many legacy configurations, needs wide port ranges, and authenticates through Windows trust that should not cross a security boundary. OPC UA authenticates with certificates, encrypts traffic, and traverses a firewall on a single port.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.