Snyk
Connect Snyk: the API token to create, what Noru collects and never collects, the controls it covers, and troubleshooting.
- Authentication
- API key
- Categories
- Security
- Sync cadence
- Daily by default (hourly, weekly, or monthly on request)
Noru reads your Snyk account with a read-only API token. It collects issue counts and statuses across Snyk Open Source, Snyk Code, Snyk Container and Snyk IaC, the open issue backlog with the issues you ignored in Snyk, the repositories, images and projects Snyk monitors, who has access to Snyk, and a hash of sampled software bills of materials. It never changes anything in Snyk and never reads source code.
What Noru collects
| Evidence type | Evidence | What it contains |
|---|---|---|
| Scan result | Snyk Vulnerability Scanning | How many projects Snyk monitors, by product, origin and test frequency, and when it last tested. Issue counts: open, ignored, and resolved in the last 90 days; open issues by severity and type; open issues Snyk can fix. |
| Scan result | Snyk Open Issue Backlog | Each group of open issues that share a vulnerability or rule, highest severity first: title, type, severity, CVEs, CWEs, CVSS score, Snyk risk score, package and versions, whether a fix exists, first detection, how many places it occurs and how many of those are ignored, and the repositories or images it was found in. |
| Scan result | Snyk Code Analysis (SAST) | Which organizations have Snyk Code on, the code projects it analyzes, and open, ignored and resolved code issues by severity. |
| Scan result | Snyk Open Source Dependency Scanning | The projects whose dependencies are scanned, by package manager, and open, ignored, resolved and fixable dependency vulnerabilities. |
| Scan result | Snyk Container Scanning | The images and Dockerfiles Snyk scans, and their open, ignored and resolved vulnerabilities. |
| Scan result | Snyk Infrastructure as Code Scanning | The infrastructure-as-code projects Snyk checks, by type, and open, ignored and resolved misconfigurations. |
| Scan result | Snyk Secrets Scanning | Which organizations have secrets scanning on, and open, ignored and resolved leaked secrets. |
| Scan result | Snyk License Compliance | Open, ignored and resolved open-source license issues. |
| Scan result | Snyk Ignored Issues | How many open issues are ignored, by severity and type, and the ignore policies by kind (won't fix, temporary, not vulnerable), review state and whether they expire. |
| Inventory | Snyk Projects & Targets | Each repository or image (name, address, private or public) and each project (name, type, origin, status, test frequency, last test), with counts by business criticality, environment and lifecycle. |
| Inventory | Snyk SBOM Coverage | Which projects can produce an SBOM, and for up to three sampled projects per sync: the SHA-256 hash, CycloneDX serial number and version, component count and generation time of the SBOM. |
| IAM | Snyk Members & Roles | Each person who can sign in: name, email, the roles they hold and in how many organizations, and whether a role is an administrator role. |
| IAM | Snyk Service Accounts | Each service account: name, organization, authentication type and level. |
| Configuration | Snyk Connected Integrations | The kinds of source control, registry and CI integrations each organization has connected. |
| Audit log | Snyk Audit Log Activity | How many audit events Snyk recorded in the last 7 days, by event name, and when the latest one was. |
| Configuration | Snyk Single Sign-On | The single sign-on connections configured for your Snyk group. |
Beyond evidence, Noru also creates:
- A security finding for each issue group.
- An asset for each repository and image Snyk monitors, so a finding lands on the thing it affects.
- An account for each member in user access reviews.
What Noru does not collect
- Source code, code flows, file contents, or line-level locations.
- The SBOM documents themselves. Noru fetches a few each sync, keeps the hash and header, and discards the rest.
- The written reason on an ignore, or who ignored the issue.
- Service account keys, secrets or tokens.
- The content of audit events: only the event name and time are read.
- Snyk's reports, and Snyk Learn progress.
Controls it covers
Each evidence row is linked only to controls whose catalog already lists a matching kind of evidence, and only while the row's data shows it (the condition column). A link whose condition stops holding is removed on the next sync.
| Evidence | Control | As evidence of | Condition | Framework references |
|---|---|---|---|---|
| Vulnerability Scanning | Vulnerability Scans (VM-01) | Scanning evidence | A project is monitored | ISO 27001 A.8.8, SOC 2 CC3.2, CC7.1 |
| Vulnerability Scanning | Vulnerability Scanning (VM-34) | Vulnerability assessments | A project is retested daily or weekly | NIS2 |
| Vulnerability Scanning | Vulnerability Scans: Trend Analysis (VM-04) | Sample vulnerability remediation | An issue was resolved in the last 90 days | |
| Vulnerability Scanning | System Security Monitoring (SM-25) | Sample of alerts generated | Snyk raised an issue | ISO 27001 A.8.16, SOC 2 CC6.8, CC7.2, CC7.3 |
| Open Issue Backlog | Backlog Prioritization (VM-23) | Sample identified bugs | Open issue groups | |
| Code Analysis (SAST) | Cybersecurity & Data Privacy Testing Throughout Development (SLC-27) | Application security testing | A code project is analyzed | NIS2 |
| Code Analysis (SAST) | Code Security Check (VM-13) | Latest vulnerability assessment report | A code project is analyzed | ISO 27001 A.5.8, A.8.25, A.8.29 |
| Open Source Dependency Scanning | Third-Party Library Check (VM-15) | Latest vulnerability assessment report | A project's dependencies are scanned | |
| Secrets Scanning | Embedded Authenticators (VM-17) | Latest vulnerability assessment report | Secrets scanning is on for an organization | |
| Infrastructure as Code Scanning | Configuration Checks (CFM-07) | Configuration deviation samples | An infrastructure-as-code project or issue exists | ISO 27001 A.8.18, SOC 2 CC6.8, CC7.1 |
| Projects & Targets | Inventory Management: Applications (AM-02) | Asset inventory | Repositories or images | SOC 2 CC6.1 |
| Projects & Targets | Asset Inventories (AM-17) | Software asset inventory | Repositories or images | NIS2 Article 21(2)(i) |
| License Compliance | Software Usage Restrictions (SG-17) | Software monitoring compliance report | A project's dependencies are scanned | |
| SBOM Coverage | Software Bill of Material (AM-13) | Software bill of materials | An SBOM was sampled and hashed this sync | |
| Members & Roles | User & Service Account Inventories (IAM-42) | User and service inventory | Members | NIS2 |
| Members & Roles | Privileged Account Management (IAM-61) | Privileged user inventory | A member with an administrator role | NIS2 |
| Members & Roles | Privileged Session Management (IAM-23) | List of privileged users | A member with an administrator role | ISO 27001 A.8.2 |
| Members & Roles | Least Privilege (IAM-29), Role-Based Access Control (IAM-51) | Defined roles and authorizations | A member holds a role | |
| Service Accounts | Service Account Restrictions (IAM-27) | Service accounts listing | Service accounts exist |
Evidence supports a control; it does not prove it on its own. Some rows are collected but deliberately linked to no control, because the catalog lists no evidence they prove: ignored issues (an ignore is a decision about one finding, not a documented policy exception), audit log activity, single sign-on connections (Snyk reports that one exists, not that everyone must use it), connected integrations, and container scanning beyond the general scanning controls. Penetration testing (VM-06, VM-36), Secrets in Code (SLC-03), baseline configurations (CFM-17), patch management (VM-08, VM-31) and multi-factor authentication (IAM-14) are not claimed either.
Findings
One finding per vulnerability or rule per Snyk organization, with Snyk's severity, title, CVE and CVSS score, a link to Snyk's description of it, and the repositories or images it was found in. A vulnerable package found in forty projects is one finding with those locations, not forty. Infrastructure-as-code issues are configuration findings, license issues are compliance findings, and everything else is a vulnerability finding. Turning off vulnerability alerts on the data source stops the vulnerability findings.
Snyk's own decisions carry over:
- A finding resolves on the next sync once Snyk no longer reports it.
- When every occurrence is ignored in Snyk, the finding is Accepted, or False Positive when it was ignored as not vulnerable. The decision reason says it was ignored in Snyk.
- When the ignore is removed or expires in Snyk, the finding reopens.
- A status someone set in Noru always wins over Snyk's ignore.
Before you connect
- The region your account is in: the address you sign in at (
app.snyk.io,app.us.snyk.io,app.eu.snyk.ioorapp.au.snyk.io). A token only works in the region it was created in. - A Snyk plan with API access. Snyk's API is available on the Enterprise plan.
- A service account token. A group or organization admin creates one in Snyk under Settings → Service accounts, with the Group Viewer role (for every organization in the group) or the Org Viewer role (for one organization). Copy the token when it is shown.
- Admin or editor role in Noru.
Connect
Choose your own Data source name. See Naming and using connection dialogs for naming, scrolling, and closing behavior.
The connection syncs daily; change the frequency in the detail drawer.
After connecting
Noru reads every organization the token can see. To narrow that, open the data source, click Choose organizations next to Organizations, and tick the ones to read. Choosing none reads them all again. The change applies from the next sync.
To replace the token, open the data source and enter the new one under the API token setting. Noru checks it against Snyk before it replaces the old one.
A token without access to one kind of data still syncs the rest: the evidence that could not be read keeps its last version. Single sign-on connections and secrets scanning settings are early-access parts of Snyk's API and may be missing for your account.
The repositories Snyk monitors become their own assets. If the same repository is also connected through GitHub or GitLab, it appears once per source.
Permissions in detail
| Role | Why Noru needs it | What it could technically allow |
|---|---|---|
| Org Viewer or Group Viewer | Read projects, targets, issues, ignores, members, service account names, settings, audit events and SBOMs | Read everything a viewer sees in those organizations, including issue details Noru discards |
A viewer role cannot change a setting, ignore an issue, import a project or start a test.
Troubleshooting
- "Snyk did not accept the API token. Check that the token is still valid and
that the region matches your Snyk account, then try again." The region is
the usual cause: a token from
app.eu.snyk.iois refused everywhere else. - "The Snyk API token cannot read your organizations. Use a service account or personal token with at least the Org Viewer role, on a Snyk plan with API access, and try again."
- "The Snyk API token cannot see any organization. Give its service account or user access to at least one organization and try again."
- "None of the selected Snyk organizations can be read with this API token. Choose the organizations to sync again." The chosen organizations were removed, or the token lost access to them.
- A revoked token marks the data source Needs reauthentication. Create a new service account token and reconnect, or enter the new token on the data source.
- No SBOM coverage link: no active open-source or container project exists yet.
Last updated on
SentinelOne
Connect SentinelOne: the service user to create, what Noru collects and never collects, the controls it covers, and troubleshooting.
Supabase
Connect Supabase: read-only Management API scopes, the organization, project, auth, and edge-function data Noru collects, and the toggles that do nothing.