Security Hub findings become Linear tickets.
The resolution goes back.
The record stays.
AWS ships ticketing for Jira Cloud and ServiceNow only. Linear teams have no supported path. The record starts before Security Hub's 90-day deletion.
Security Hub findings sit in a queue nobody owns
AWS Security Hub sees everything. Linear is where your engineers work. Nothing connects them, so findings age, teams miss SLAs, and auditors ask where the evidence is.
Findings age unacknowledged
High-severity findings sit in Security Hub for weeks. Nobody is on call for the queue. SLA clocks tick silently.
No record of what was done
A ticket is closed in Linear. The finding stays open in Security Hub. There is no paper trail connecting the two at audit time.
The record expires before the audit does
Security Hub deletes a finding 90 days after its last update. The ticket is closed, the finding is gone, and an auditor asking about anything older finds nothing.
Five steps. No agent.
LoopProof is a serverless pipeline in your AWS account. The connector is a Terraform module.
Install the connector
One module block in Terraform. It creates an EventBridge rule that forwards Security Hub "Findings Imported V2" events (High, Critical and Fatal) to LoopProof's bus across accounts. No IAM user, no access key, no agent process.
Connect Linear
Authorize LoopProof's OAuth app in your Linear workspace. Findings will be filed as the LoopProof app, not as a person.
Self-check
LoopProof assumes the connector role, confirms the account identity with STS, and provisions an isolated schema. If the connector role does not work, the check says why before anything is filed.
Import and preview
LoopProof imports your open findings and shows what would become tickets: team, severity label, one ticket per remediation. Nothing is filed until you confirm.
Go live
Enable ticketing. From this point, new findings from GuardDuty and Inspector become Linear tickets automatically. The resolution goes back when the ticket is closed.
For the engineer who owns AWS security at a Linear shop
If your team runs on AWS, files tickets in Linear, and needs to show an auditor that a finding was handled, LoopProof is for you.
Your security team gets coverage
Every High, Critical and Fatal finding from GuardDuty and Inspector lands in Linear. The finding is resolved in Security Hub when the ticket is closed. Nothing is missed and nothing is manual.
Your compliance team gets evidence
Every finding, every ticket, every resolution is in the audit log with a timestamp and an operator identity. The raw Security Hub event is in S3, independent of Security Hub's 90-day deletion window. Hand the auditor a log stream, not a spreadsheet.
Your engineering team is not interrupted
Tickets appear in the right Linear team, labelled by severity. Engineers close them the way they close any ticket. There is no Security Hub console to learn and no approval queue to gate on.
Every accept has a reason on record
When a finding is suppressed, the reason is in the audit log. The raw event is in S3. An auditor asking about anything LoopProof touched finds the full chain, not a gap.
Transparent roadmap
Findings in, tickets out, resolution written back, the record and the web app are live. More finding sources, the evidence export, Jira and notifications are on the 2027 roadmap.
Working today
Findings in
GuardDuty and Inspector findings at High and above, from every account and Region you connect.
Tickets out
One Linear ticket per remediation, not per finding, routed to the owning team, filed as the app.
Resolution written back
LoopProof updates the finding in Security Hub as the work moves, so the two do not drift apart.
The record
Every finding, ticket, resolution and accepted risk, with the raw event in S3, past the 90 days.
The web app
Onboarding, people, settings, the audit trail and reports, in the browser.
Coming next
More finding sources
Security Hub CSPM and Exposure findings alongside GuardDuty and Inspector.
The evidence export
The record packaged for an auditor to read, rather than read in the app.
More trackers
Jira alongside Linear, if design partners need it.
Notifications
A daily digest and hold alerts in Slack.
Shape LoopProof before it ships
We're working with a small group of AWS and Linear teams to validate the product before general availability. Design partners get direct access to the founding team and early access to features.