INTEGRATIONS

GitHub Actions integration

Secorvia connects to four cloud providers and Kubernetes, and GitHub is not one of them. Its documentation describes no GitHub Action and no GitHub app, so this page does not claim one. It covers what a pipeline on GitHub Actions can use today: the API, and the open source scanner frontdoor.

What Secorvia reads from GitHub, and what it finds

Nothing. The platform connects to AWS, Azure, Google Cloud, DigitalOcean and Kubernetes, and the connection guide lists no GitHub connection. It does not read your repositories, your workflows or your pull requests. The one place code reaches Secorvia is infrastructure as code scanning, where you supply a revision inside the product. The documentation does not describe pulling that revision from GitHub.

There is still a real connection between GitHub Actions and cloud security, and it runs through your cloud account. A workflow often deploys by exchanging a short-lived GitHub token for cloud credentials, and the role that accepts the token decides which repositories get in. That trust is where findings appear, and the tool built to find them is frontdoor.

What a pipeline can use today

frontdoor, to check the trust a workflow relies on. frontdoor is a free, read-only command line scanner under the Apache 2.0 licence. It needs no account and uses the credentials you already have. Every AWS call it makes is a List, Get or Describe, and the AWS-managed SecurityAudit policy covers everything it reads. Its rules for OIDC trust, which include GitHub Actions, look for a role with no condition on the subject claim, so that any repository on GitHub can assume it, an organization-wide subject, a role assumable from any branch, a role that accepts the pull request context, trust that rests on the repository owner alone, an audience claim that is not restricted, a condition keyed to the wrong issuer, and an OIDC provider thumbprint that is missing or stale. The frontdoor documentation explains each rule, starting with FD001.

It is built to run in CI. Adding --fail-on high makes a job fail when it finds something of that severity, and --format sarif sends findings to the GitHub Security tab. The federated trust article shows the install command and what a scan reports.

The Secorvia API, for your own scripts. Organization API keys are made for one integration each, and the guide's own example name is "CI pipeline". A key acts as a service identity, so changes and comments it makes are attributed to that identity. Scopes cover findings, inventory, cloud accounts, scans, vulnerabilities, compliance and the security graph, and read and write are granted separately. Writing scans requires an idempotency key on each request. Full API access is part of the Growth plan, and the API keys guide has the steps.

What connecting takes

There is nothing to install or authorize on the GitHub side. For frontdoor, you install the binary and run it with credentials that can read your cloud account. For the API, you create a key under API Keys, choose a service identity and grant only the scopes the job needs. Set an expiry if you want one. The secret is shown once, so copy it straight into a secret manager or an environment variable. In a GitHub Actions workflow that means the repository's encrypted secrets, never the workflow file. It must not go into source control or a browser bundle.

When it is time to replace a key, create the new one first, update the workflow, check that its requests succeed, and only then revoke the old key. Revocation is immediate and cannot be undone, so a workflow still using the old key fails on its next request.

What Secorvia does not do with GitHub Actions

Secorvia is read-only in everything it connects to. It never asks for write access to your infrastructure, and frontdoor makes only read calls. Both report problems and do not fix them, so a remediation, such as tightening a trust policy, is a change you make in your cloud account.

The documentation describes no Secorvia GitHub Action, no GitHub app, no pull request checks or comments, and no way to send findings into GitHub from the platform itself. The only route to the GitHub Security tab described here is frontdoor's SARIF output. The scopes the API keys guide lists also do not include infrastructure as code projects, so do not assume a pipeline can submit a revision through the API. That workflow lives in the product.

If a GitHub integration is what decides your purchase, read what Secorvia does first, and ask before you plan around anything this page does not describe.

Frequently asked questions

Is there a Secorvia GitHub Action?

The documentation describes no GitHub Action and no GitHub app, so this site does not claim one. The open source scanner frontdoor is built to run in a CI job, and the Secorvia API can be called from a workflow with an organization API key.

Can I fail a GitHub Actions build on findings?

With frontdoor, yes. Adding the fail-on option with a severity, such as high, makes the job fail when it finds something at that severity. The documentation does not describe the same for findings in the Secorvia platform.

Can findings appear in the GitHub Security tab?

frontdoor can write SARIF output, which is the format the GitHub Security tab reads. The documentation describes no such output from the Secorvia platform.

Does Secorvia read my GitHub repositories?

No. The platform connects to AWS, Azure, Google Cloud, DigitalOcean and Kubernetes, and the connection guide lists no GitHub connection.

How should I store a Secorvia API key in a workflow?

Keep it in the repository's encrypted secrets, not in the workflow file or source control. The key is shown once, so copy it when you create it, and grant only the scopes the job needs.

Check who can assume your roles