GitHub and Talon
Open a GitHub issue from any confirmed finding. Pick one repository for security work. Any finding in Talon can then become a GitHub issue with severity labels, the affected asset and the fix steps.
What you get
Included
- One click per findingA ticket button appears on each finding in Talon once GitHub is connected.
- Severity labelsIssues are labelled security, ptaas and severity:critical, severity:high and so on.
- Everything a developer needsDescription, affected asset and fix steps in Markdown.
- One target repositoryIssues go to the owner and repository you set when connecting.
Good to know
- This integration creates issues. It does not scan your code or pull requests.
- Closing the GitHub issue does not change the finding in Talon. Request a retest in Talon when the fix is live.
Set it up in a few minutes
You need a Talon workspace and permission to create a token or webhook in GitHub.
- 01
Create a token
In GitHub, create a personal access token with the repo scope for the repository you want issues in.
- 02
Open the Marketplace in Talon
Go to Workspace > Marketplace and choose Connect GitHub.
- 03
Enter your details
Add the token, the repository owner (user or organization) and the repository name.
- 04
Test and save
Use the test button to confirm the token works, then save.
- 05
Send a finding
On the Findings page, use the ticket button on any finding.
What lands in GitHub
| Field | What you get |
|---|---|
| Title | [Security] followed by the finding title |
| Body | Severity, category, status, description, affected asset and fix steps |
| Labels | security, ptaas and severity:<level> |
| Direction | One way, Talon to GitHub, when you click the button |
When the fix is live, request a retest in Talon with one click. A Lorikeet Security pentester checks it, typically within 24 to 48 hours, and Talon updates the finding.