Governed contractor access
Give a vendor working access without the keys to the kingdom, and keep a signed record of everything they did under their own name.
Illustrative scenario
The vendor visit that isn’t a visit
The instrument vendor’s specialist is given a contractor account. They connect remotely, work the problem, and log off. The customer’s auditor exports exactly what the vendor did, command by command.
Fictional scenario, people, and devices.
What it gives you
-
Named contractor accounts
Each vendor specialist signs in with their own account and the Contractor role. No shared logins.
-
Remote work, and nothing more
Contractors open remote work sessions with their own tools and see their own session history. Team, policy, and the record stay with your administrators and auditors.
-
Everything recorded under their name
Every HART command a contractor sends is classified, evaluated against your access policy, and recorded with the decision and the outcome. Out-of-policy commands are flagged and permanently recorded.
-
Proof after the fact
Your auditor searches the record and exports exactly what the vendor did, as a spreadsheet-ready file.
US EPA water-sector cybersecurity guidance expects accountable remote access, including for vendors (source: EPA).
Roles keep it scoped
Four roles, each with the access its job needs. Contractors do remote work, with every action recorded, and nothing more.
Set up a trial with our team.
Contact sales to set up a trial: for distributed operators, service teams, and instrumentation groups ready to evaluate governed remote HART access.