Providers

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 typeEvidenceWhat it contains
Scan resultSnyk Vulnerability ScanningHow 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 resultSnyk Open Issue BacklogEach 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 resultSnyk Code Analysis (SAST)Which organizations have Snyk Code on, the code projects it analyzes, and open, ignored and resolved code issues by severity.
Scan resultSnyk Open Source Dependency ScanningThe projects whose dependencies are scanned, by package manager, and open, ignored, resolved and fixable dependency vulnerabilities.
Scan resultSnyk Container ScanningThe images and Dockerfiles Snyk scans, and their open, ignored and resolved vulnerabilities.
Scan resultSnyk Infrastructure as Code ScanningThe infrastructure-as-code projects Snyk checks, by type, and open, ignored and resolved misconfigurations.
Scan resultSnyk Secrets ScanningWhich organizations have secrets scanning on, and open, ignored and resolved leaked secrets.
Scan resultSnyk License ComplianceOpen, ignored and resolved open-source license issues.
Scan resultSnyk Ignored IssuesHow 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.
InventorySnyk Projects & TargetsEach 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.
InventorySnyk SBOM CoverageWhich 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.
IAMSnyk Members & RolesEach person who can sign in: name, email, the roles they hold and in how many organizations, and whether a role is an administrator role.
IAMSnyk Service AccountsEach service account: name, organization, authentication type and level.
ConfigurationSnyk Connected IntegrationsThe kinds of source control, registry and CI integrations each organization has connected.
Audit logSnyk Audit Log ActivityHow many audit events Snyk recorded in the last 7 days, by event name, and when the latest one was.
ConfigurationSnyk Single Sign-OnThe single sign-on connections configured for your Snyk group.

Beyond evidence, Noru also creates:

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.

EvidenceControlAs evidence ofConditionFramework references
Vulnerability ScanningVulnerability Scans (VM-01)Scanning evidenceA project is monitoredISO 27001 A.8.8, SOC 2 CC3.2, CC7.1
Vulnerability ScanningVulnerability Scanning (VM-34)Vulnerability assessmentsA project is retested daily or weeklyNIS2
Vulnerability ScanningVulnerability Scans: Trend Analysis (VM-04)Sample vulnerability remediationAn issue was resolved in the last 90 days
Vulnerability ScanningSystem Security Monitoring (SM-25)Sample of alerts generatedSnyk raised an issueISO 27001 A.8.16, SOC 2 CC6.8, CC7.2, CC7.3
Open Issue BacklogBacklog Prioritization (VM-23)Sample identified bugsOpen issue groups
Code Analysis (SAST)Cybersecurity & Data Privacy Testing Throughout Development (SLC-27)Application security testingA code project is analyzedNIS2
Code Analysis (SAST)Code Security Check (VM-13)Latest vulnerability assessment reportA code project is analyzedISO 27001 A.5.8, A.8.25, A.8.29
Open Source Dependency ScanningThird-Party Library Check (VM-15)Latest vulnerability assessment reportA project's dependencies are scanned
Secrets ScanningEmbedded Authenticators (VM-17)Latest vulnerability assessment reportSecrets scanning is on for an organization
Infrastructure as Code ScanningConfiguration Checks (CFM-07)Configuration deviation samplesAn infrastructure-as-code project or issue existsISO 27001 A.8.18, SOC 2 CC6.8, CC7.1
Projects & TargetsInventory Management: Applications (AM-02)Asset inventoryRepositories or imagesSOC 2 CC6.1
Projects & TargetsAsset Inventories (AM-17)Software asset inventoryRepositories or imagesNIS2 Article 21(2)(i)
License ComplianceSoftware Usage Restrictions (SG-17)Software monitoring compliance reportA project's dependencies are scanned
SBOM CoverageSoftware Bill of Material (AM-13)Software bill of materialsAn SBOM was sampled and hashed this sync
Members & RolesUser & Service Account Inventories (IAM-42)User and service inventoryMembersNIS2
Members & RolesPrivileged Account Management (IAM-61)Privileged user inventoryA member with an administrator roleNIS2
Members & RolesPrivileged Session Management (IAM-23)List of privileged usersA member with an administrator roleISO 27001 A.8.2
Members & RolesLeast Privilege (IAM-29), Role-Based Access Control (IAM-51)Defined roles and authorizationsA member holds a role
Service AccountsService Account Restrictions (IAM-27)Service accounts listingService 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.io or app.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

Open Data Sources, click Connect data source, and pick Snyk. The Connect Snyk dialog opens.
Enter a Data source name and pick the Region.
Paste the API token.
Click Connect Snyk. Noru checks that the token can read at least one organization before it saves the connection, then shows "Snyk connected".

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

RoleWhy Noru needs itWhat it could technically allow
Org Viewer or Group ViewerRead projects, targets, issues, ignores, members, service account names, settings, audit events and SBOMsRead 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.io is 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