checkId: check.timestamp.timesync.rekor-correlation plugin: stellaops.doctor.timestamping severity: warn tags: [timestamping, timesync, rekor, correlation, transparency]

TST-Rekor Time Correlation

This Stella Ops Doctor check cross-checks the timestamp token (TST) genTime against the Rekor transparency-log integratedTime for recent attestations. It is a tamper-detection signal: an attestation whose TST is dated after its Rekor entry is a strong indicator of backdating or clock manipulation, so operators of audited release pipelines should treat any failure as a security event.

What It Checks

Verifies that TST genTime and Rekor integratedTime are properly correlated. The check:

Why It Matters

Proper time correlation between the TST and its Rekor (transparency log) entry is a key integrity signal. If a TST is dated after its Rekor entry, it may indicate clock manipulation or backdating. Excessive gaps suggest pipeline delays that could indicate operational issues.

Common Causes

How to Fix

Docker Compose

# Check system time sync
timedatectl status

# Verify pipeline timing
docker exec <platform-container> stella evidence audit --recent --show-timing

Bare Metal / systemd

# Investigate time synchronization
chronyc tracking

# Review attestation timing
stella evidence audit --recent --show-timing

Kubernetes / Helm

timestamping:
  rekorCorrelation:
    lookbackWindow: "24h"
    maximumGap: "5m"

Investigate ordering violations immediately as they may indicate tampering.

Verification

stella doctor run --check check.timestamp.timesync.rekor-correlation