Audit and accountability

Answer “who changed this, and when?” with a signed record instead of a guess.

Contact Sales See a sample audit record

A search for a range change on LT-204 returns one signed record. Illustration with fictional data. LT-204 write range 1 result 35 Write Range Values LT-204, North Pump Station m.chen, Engineer, 3 months ago Allow Signed

Illustrative scenario

The range change nobody remembers

A transmitter’s configuration changed last quarter. The maintenance manager searches the audit record and has the who, when, and what in seconds.

Fictional scenario, people, and devices.

What it gives you

  • Who changed what

    Every record names the person and their role, the site, gateway, and device, the session, and the HART command by number and name.

  • Command-aware evidence

    Each record shows the policy decision and what actually happened to the command, so a reviewer never has to guess whether a flagged command was carried out.

  • Signed and chained

    Each record is digitally signed and chained to the one before it, so any alteration, deletion, or reordering is detectable.

  • Export for auditors

    Administrators and auditors export the record, or the slice matching a search, as a spreadsheet-ready file. Hand an auditor an export rather than a reconstruction.

What a record looks like

Two records from one contractor session: an allowed read, and a denied write that is flagged and recorded.

Sample audit recordIllustrative record. Fictional organization, people, and devices.
  1. When
    14:32:07.418
    Who
    [email protected] (Contractor)
    In which session
    Remote support session #1182
    Where
    North Pump Station, Gateway 2
    Device
    LT-204, radar level transmitter
    What
    1 Read Primary Variable Read
    Outcome
    Carried out
    Under what authority
    Allow read commands permitted for contractors
    Can I trust it?
    ✓ Signed✓ Chained to previous record
  2. When
    14:33:52.106
    Who
    [email protected] (Contractor)
    In which session
    Remote support session #1182
    Where
    North Pump Station, Gateway 2
    Device
    LT-204, radar level transmitter
    What
    35 Write Range Values Write
    Outcome
    Recorded, not blocked
    Under what authority
    Deny write commands not permitted for contractors
    Can I trust it?
    ✓ Signed✓ Chained to previous record

Every out-of-policy command is flagged and permanently recorded.

Each record is digitally signed when it is written and carries a fingerprint of the record before it, so the records form an unbroken chain. If anyone edits, deletes, or reorders a record later, the signature or the chain no longer checks out. Integrity is mathematical, not “we promise we keep logs.”

Try to change the record

Rewrite the second record’s decision from Deny to Allow and see what a reviewer would see.

Kept for the life of your account

For as long as you’re a customer. If you leave, you get your records first; we hold them for a 180-day closing period and then delete them permanently.

Audit records are kept for the life of your account. When an account closes, field access ends and you receive your records; HartBeat then holds the data for a 180-day closing period, after which it is permanently deleted. For the life of your account Records are never deleted because of their age Account closes Field access ends; you receive your records 180-day closing period Permanently deleted

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.

Contact Sales Trial Readiness Checklist