Securing historian servers in OT environments
Audit and harden OSIsoft PI / Honeywell PHD / GE Proficy historians — IEC 62443, Purdue model, DMZ replication
- What
- Audit and harden OSIsoft PI / Honeywell PHD / GE Proficy historians — IEC 62443, Purdue model, DMZ replication
- Cost
- Free
- Needs
- access to an OT/ICS environment with historian servers (OSIsoft PI, Honeywell PHD, GE Proficy, AVEVA Historian); OT change-control discipline for any configuration change
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a skill for auditing and hardening process historian servers (OSIsoft PI, Honeywell PHD, GE Proficy, AVEVA Historian) in OT environments: Purdue-model network placement, interface access control, secure DMZ replication via data diodes or PI-to-PI connectors, SQL injection prevention, and process data integrity. By @mukul975, listed here with credit to its creator. Honest caveats: industrial niche — you need an actual OT/ICS environment with historian servers to apply this; changes in OT must follow change-control discipline, a misapplied hardening step can interrupt process data flows; OT expertise assumed, not taught from zero. Not verified. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Securing historian servers is a free Muse skill for auditing and hardening OSIsoft PI, Honeywell PHD and GE Proficy historians in OT environments. It applies IEC 62443, the Purdue model and DMZ replication. That matters because historians bridge operational systems and business networks, making them high-value targets for attackers.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 54a7988Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: access to an OT/ICS environment with historian servers (OSIsoft PI, Honeywell PHD, GE Proficy, AVEVA Historian); OT change-control discipline for any configuration change Install "Securing historian servers in OT environments" for me. Give my agent the skill for auditing and hardening historian servers in OT — Purdue placement, access control, DMZ replication, SQL injection prevention, data integrity Repository: https://raw.githubusercontent.com/mukul975/anthropic-cybersecurity-skills/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/securing-historian-server-in-ot-environment/SKILL.md Pinned version: install the code at commit 54a798831d2266a3ca61ce68a7acb80b81160d57 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the mukul975-anthropic-cybersecurity-skills-securing-historian-server-in-ot-environment skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mukul975-anthropic-cybersecurity-skills-securing-historian-server-in-ot-environment". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. identify the historian servers to audit, confirm change-control approval). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 54a7988 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.