EvidenceLog for Atlassian Jira Cloud
Official technical documentation for engineering squads, compliance architects, support engineers, and external auditors. Learn how EvidenceLog continuously inspects, validates, seals, and certifies software change evidence with zero external data egress.
1. Product Overview & Architecture
EvidenceLog is a cloud-native Atlassian Forge application engineered to eliminate the manual “screenshot tax” for SOC 2 Type II, ISO/IEC 27001:2022, APRA CPS 234, and DORA change management audits. Unlike traditional third-party SaaS tools that require broad read access to your Jira tickets and source code, EvidenceLog executes 100% inside your Atlassian Cloud tenant.
Operates with strict connect: false manifests. Zero tickets, code diffs, or secrets leave Atlassian's isolated microVMs.
Persists tamper-evident evidence snapshots and multi-version audit histories in Atlassian Forge Key-Value Storage (@forge/kvs).
Canonical JSON normalization generates deterministic 64-character SHA-256 fingerprints verifiable offline by external Big 4 audit teams.
2. 2-Minute Quickstart Guide
EvidenceLog requires zero server provisioning, database credentials, or external API keys. Installation takes under two minutes directly from the Atlassian Marketplace:
- 1Install from Atlassian MarketplaceNavigate to your Jira Cloud Settings → Apps → Find new apps. Search for EvidenceLog and click Get app.
- 2Automatic Issue Panel ActivationEvidenceLog automatically mounts on all Jira issue types via the
jira:issuePanelandjira:issueContextextension points. - 3(Optional) Attach the Preventive GatekeeperTo block unverified issues from reaching “Done”, open Jira Project Settings → Workflows → Edit → Select Transition → Add Validator → Choose EvidenceLog SOC 2 Gatekeeper.
3. The Five Core Compliance Pillars
EvidenceLog inspects every change request against five discrete, independent micro-controls aligned with AICPA SOC 2 Type II and ISO/IEC 27001:2022 standards:
Acceptance Criteria & Definition of Done
Evaluates Jira issue descriptions and custom fields for structured requirements. Specifically recognizes BDD Given/When/Then scenarios, Definition of Done (DoD) bullet checklists, or explicit acceptance headers.
Code Linkage & Multi-Repo VCS Traceability
Inspects Jira Development panel links, remote links, and commit associations. Automatically classifies pull requests and branch merges across GitHub (/pull/\d+), GitLab (/merge_requests/\d+), Bitbucket, and Azure DevOps.
Segregation of Duties (Author ≠ Approver)
Mathematically verifies that whoever authored or created the change did not self-approve or self-deploy it. Inspects Jira workflow changelog transitions to terminal statuses and peer review sign-offs from independent accounts.
Independent QA Sign-Off & Pre-Release Testing
Confirms testing verification before production release. Detected via QA status transitions (e.g. In QA → QA Approved), recognized testing labels (qa-verified, uat-verified), or formal sign-off comments.
Security & SAST Vulnerability Scanning
Identifies static analysis and container security traces. Automatically parses confirmation traces from Snyk, SonarQube, Trivy, Dependabot, and OWASP ZAP via issue labels, build comments, or CI bot webhooks.
4. Real-Time Issue Compliance Panel
Rendered natively in Jira Cloud issue views via Atlassian UI Kit 2 components. Provides engineers with real-time feedback without switching browser tabs:
5. 1-Click In-Situ Quick Fixes
When a change request fails one or more controls, EvidenceLog provides interactive developer buttons directly in the Jira panel to resolve missing evidence instantly without manual ticket editing:
Posts an automated BDD Acceptance Criteria and Definition of Done markdown checklist comment to the ticket.
Applies the project-configured QA verification label directly to Jira issue metadata via Jira REST API.
Generates a formal sign-off comment documenting testing environment, reviewer identity, and timestamp.
6. Preventive Workflow Gatekeeper
Configured as a native Jira Workflow Validator (jira:workflowValidator). It evaluates tickets in real time during status transitions:
If an engineer attempts to move a ticket to Done, Resolved, or Release without satisfied controls (e.g. author self-approval or missing Git PR link), the transition is blocked immediately. A clear notification displays the exact missing control so developers can fix it in seconds.
hotfix, sev1) bypass the blocker to avoid incident delays, but are automatically flagged with riskLevel = "EMERGENCY" requiring retroactive CAB review.7. Project Audit Hub & 7 KPI Scorecards
Accessible via the project left sidebar in Jira (jira:projectPage). Provides release managers, CISOs, and auditors with complete visibility across entire release batches:
8. 1-Click Batch Certification
Rather than certifying tickets individually, release managers can certify an entire sprint or release batch with a single click. The backend resolver iterates over all audit-ready issues in the release, generates cryptographic snapshots, writes them to Forge KVS, and syncs certified entity properties for instant JQL indexing.
9. Big 4 CSV & Printable PDF Certificates
EvidenceLog produces formal audit workpapers specifically formatted for Big 4 CPAs (PwC, EY, Deloitte, KPMG) and compliance platforms:
Consolidated CSV Workpaper Matrix
Downloadable CSV containing ticket key, summary, author, approver, QA signer, status, score, change risk, and SHA-256 fingerprint. Fits directly into auditor sample test workbooks.
Printable PDF Compliance Verification Certificate
Clean printable certificate with full control breakdown, regulatory references, and cryptographic seal. Can be printed directly from Jira using browser print stylesheets.
10. SHA-256 Fingerprinting & Binary Merkle Trees
To guarantee non-repudiation and prevent retroactive evidence tampering, EvidenceLog implements deterministic cryptographic tree hashing:
11. Air-Gapped Standalone Offline Verifier
External auditors do not need Jira licenses or internet connectivity to verify evidence authenticity. EvidenceLog provides a standalone, zero-dependency HTML verifier (docs/verifier.html) using the native W3C Web Cryptography API.
12. Continuous Vanta & Drata Ingestion
Automated continuous payload export matching Vanta Custom Evidence Upload specifications and Drata DCF-87, DCF-91, and DCF-104 automated tests with zero manual screenshotting.
13. Native JQL Search & Entity Properties
EvidenceLog registers a native Jira entity property (evidencelog_compliance) indexed for instant JQL search queries across Jira filters, dashboards, and agile boards:
14. Project Compliance Policy Configuration GUI
Project Administrators can customize compliance thresholds directly from the Project Audit Hub without touching backend configuration files:
15. Support & Debugging Playbook
Quick reference guide for support engineers and project admins diagnosing why a ticket or transition is flagged:
Cause: The ticket creator or assignee attempted to transition the issue to Done. Under SOC 2 CC6.8, changes require independent verification.
Resolution: An independent team member (Tech Lead, Senior Engineer) must review the PR and execute the final status transition, or post an explicit approval comment ("Peer review approved by @user").
Cause: The pull request description or branch name does not include the Jira issue key, so Jira did not associate the remote link.
Resolution: Ensure PR title or branch name contains the ticket key (e.g. feature/LANG-10-auth) or manually paste the PR URL in the Jira Development web link panel.
Resolution: Apply any recognized emergency label (hotfix, sev1, emergency). The Gatekeeper allows the release transition immediately while automatically tagging it for retroactive Change Advisory Board (CAB) review within 48 hours.