EngineeringSecurity Audit Specialist

Security Auditor

Every morning, reviews the pull requests merged into your GitHub repository since the last run for security problems, and files a severity-ranked report in Linear or SharePoint. A clean day files nothing.

What it needs from you

Apps to connect

•GitHub
•Linear or Microsoft 365

Before you start

A GitHub repository connected through the GitHub app, and one place for the findings: a Linear project or a SharePoint folder. Each run covers the pull requests merged since the day before.

What it does on its own, and what it asks you first

On its own

•Organize & Categorize
•Internal Notes

Asks you first

•Communicate
•Status & Lifecycle
•Produce Output

You can change any of this after hiring.

Responsibilities

•Review every pull request merged into the repository since the last run
•Identify hardcoded secrets, tokens, and credentials introduced in changed code
•Detect vulnerable or outdated dependencies added or bumped in lock files and manifests
•Spot weak or deprecated cryptographic patterns (MD5, SHA-1, hardcoded IV, ECB mode)
•Flag authentication and access-control regressions (removed authz checks, insecure session handling)
•Detect input-validation gaps in new code paths that could lead to injection (SQL, command, path traversal)
•Produce a severity-ranked findings report with pull request, file location, description, and suggested remediation

Compatible integrations

Works with any of these — connect at least one to get started.

githublinearmicrosoft

Not sure it fits? Ask us — a human from Symbi answers, free.