Request a quote WhatsApp

16 September 2026 · 3 min read

Timestamps and signed log archives: what makes a record hold up?

Keeping logs is not enough; you must prove when a record was produced and that it was not altered. Timestamps, signatures, clock sync and handover reports explained.

When a business says "we keep logs", the real question is: how do you show when a record was produced and that it has not changed since? Timestamping and a signed archive answer exactly that.

A plain text file that can be edited afterwards is weak evidence. Three things make a record strong: a trusted clock, a stamp applied at creation, and an archive whose integrity can be verified.

What a timestamp actually proves

A timestamp proves a piece of data existed before a given moment. A digest of the record is taken and stamped; if a single character changes later, the digest no longer matches and the change surfaces. "Was this line added afterwards?" becomes a technically answerable question.

Why clock sync matters

A stamp is only as good as the clock behind it. In practice:

  • All network devices and the log server use the same NTP sources
  • At least two NTP sources are defined and drift is monitored
  • Time zone and daylight saving behaviour match across devices
  • Records are stored in UTC and converted for reports

Parts of a signed archive

PartPurpose
HashFingerprint of each record block
Digital signatureProof of who produced the block
TimestampProof the block existed before a moment
ChainingEach block carries the previous digest, blocking insertions
Access logWho opened the archive and when

What is stored

Session records (user, MAC, internal IP, public IP, port range, start and end), authentication records (method, result, time) and consent records. Content is not stored — details in the 5651 guide.

The report produced on request

A good report bundles four things: the queried time and address range, the matching session rows, the authentication record behind the session, and signature information proving archive integrity. The package should be machine-verifiable.

Retention and deletion

Keeping everything forever is a risk, not a safeguard. Retention must be written down, deletion must run automatically at the end of the period, and the deletion itself must be logged.

Checklist

  • Are records stamped at creation or in later batches?
  • Is NTP drift monitored?
  • Is the archive replicated to a second location?
  • How long does report generation take?
  • Is archive access granted per individual?

FAQ

Is zipping the log files enough?

No. Compression proves nothing about integrity; a file can be edited and recompressed.

Does timestamping require internet access?

If the stamping service is external, yes. When the link drops, records queue and are stamped once it returns.

Do clock drifts invalidate old records?

No, but drift must be recorded. Monitored and documented corrections preserve the value of records.

Can the archive live in the cloud?

Yes, as long as access control, redundancy and integrity verification are in place.

How does HotSpot do it?

Session and authentication records are stamped as they are produced, the archive is chained, and a signature-verified report is generated on request.

Let’s simplify your guest Wi-Fi journey

Keep your existing infrastructure and bring access, engagement and 5651 records into one panel.

Request a Free Demo

We use cookies for visit statistics. Cookie policy