Tamper-Evident Audit Log for Jira
Every change to every Jira ticket — signed, timestamped, and hash-chained into a tamper-evident, independently verifiable audit log.
What it does
The Tamper-Evident Audit Log for Jira captures all activity on your Jira tickets and converts each event into a cryptographically-signed, hash-chained audit entry. Every comment, status transition, field edit, attachment, link, and watcher change produces a chain entry that is:
- Cryptographically signed with ECDSA secp256k1 — the same algorithm used in Bitcoin and Ethereum key infrastructure
- RFC 3161 timestamped by an independent, accredited timestamp authority — not the Attestsys server clock
- Hash-chained to the previous entry — so any insertion, deletion, or modification of a past entry breaks the chain in a way that is mathematically detectable
- Offline-verifiable — export a self-contained bundle and verify every signature and chain link in a browser, with no internet connection and no Attestsys account required
Who it is for
| Role | What you get |
|---|---|
| Security engineers and SREs | An unforgeable record of who changed what in Jira, and when — independently verifiable without trusting Atlassian or Attestsys |
| Compliance teams (SOC 2, ISO 27001, SOX, DORA) | Tamper-evident, independently verifiable evidence bundles that reduce audit preparation effort and support authentication in audit and legal contexts |
| Engineering and DevOps leads | A signed change trail across tickets, linked to deploys and approvals — ready to attach to change-management evidence packages |
| Legal and GRC teams | Evidence designed to support authentication under eIDAS Art. 41 (qualified electronic timestamps) and Art. 35(2) (qualified electronic seals), German ZPO §371a, US FRE 902(13)(14), and UK ECA 2000 §7 |
The four-property stack
No other Atlassian Marketplace app ships all four properties together:
| Property | What it means |
|---|---|
| Per-entry cryptographic signing | Each audit entry is individually signed — not just the export |
| Hash chaining | Each entry contains the SHA-256 hash of the previous entry's signed payload, creating a chain where any past modification is detectable |
| RFC 3161 trusted timestamping | Timestamps are issued by accredited third-party timestamp authorities (TSAs), not by Attestsys. Free tier uses FreeTSA (non-qualified, clearly labelled). Paid tiers use QTSP-backed qualified timestamps from EU Trusted List providers |
| Portable offline verification | Every export bundle includes verify.html — a self-contained verifier that runs entirely in the browser with no outbound connections |
Editions
| Free | Standard | Advanced | Enterprise | |
|---|---|---|---|---|
| Hash-chain signing | ✅ | ✅ | ✅ | ✅ |
| RFC 3161 timestamping (FreeTSA, non-qualified) | ✅ | ✅ | optional | optional |
| QTSP-backed qualified timestamping | ❌ | optional upgrade | ✅ mandatory | ✅ tenant-selectable |
| Offline-verifiable export | ✅ (max 10/month) | ✅ | ✅ | ✅ |
| Retention | 30 days | 1 year | Unlimited | Custom |
| Scheduled exports | ❌ | ❌ | ✅ | ✅ |
| GRC-tool webhooks (Drata, Vanta) | ❌ | ❌ | ✅ | ✅ |
| Suspicious-tamper Slack alerts | ❌ | ✅ | ✅ | ✅ |
| Custom DPA + EU residency guarantee | ❌ | ❌ | ❌ | ✅ |
| Rovo Companion Agent | ❌ | ❌ | ✅ | ✅ |
Editions are billed per-user through the Atlassian Marketplace. Enterprise is billed directly via a flat-fee contract.
Next steps
- Feature Reference — detailed feature documentation
- Cryptographic Verification — how the signing, timestamping, and hash chain work
- Configuration — admin settings, retention policy, permission scopes
- Troubleshooting — common issues and resolutions
📸 Getting Started guide — a step-by-step install and first-run guide (with screenshots) will be published here after the Marketplace listing goes live.