> ## Documentation Index
> Fetch the complete documentation index at: https://synthetiq.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Security

> How the Console scans every app and service for known vulnerabilities, and how fixes ship

**Security** checks every app and service for known vulnerabilities. The scan runs every night at 03:00 UTC, and you can start one any time with **Scan now**.

![Security page with the Packages tab open, listing findings by severity, fix, app or service, where it runs and when it was first found](https://mintcdn.com/synthetiq/hhugnC-v5exvzXyJ/images/platform-docs/console/security-packages.png?fit=max\&auto=format\&n=hhugnC-v5exvzXyJ\&q=85\&s=3c36941caf211e8d9012ee1b9e04f172)

Security › Packages: open findings by severity, fix and where they run.

## What the scan checks

A scan covers every app version deployed to any environment, every service version those apps bundle, and the active and latest version of each app and service. Each gets three checks:

| Tab | Checks |
| - | - |
| **Packages** | Every npm package in the lockfile, including those Synthetiq's libraries bring in, against the [OSV](https://osv.dev) database. |
| **Framework** | The app's release of Synthetiq's app libraries, against the latest stable (beta releases never count). |
| **Node runtime** | Each deployed app's Node version, web and worker, against the newest patch of its major version. |

Published versions never change, so the scan reads each lockfile once and rechecks it against OSV every run. A scan that makes no progress for six hours counts as failed.

### Where the scan runs

The scan runs inside the Console on Synthetiq, from the lockfile stored with each version. Nothing runs in your AWS account, and package findings cover a version whether it runs in Synthetiq's AWS account or yours. The exception is Node runtime: the Console can only read Node versions in Synthetiq's AWS account, so apps in yours show **Not visible**.

## Findings

A finding is one package advisory in one app or service. Each one shows:

* **Severity**, from the advisory. A malicious package is always critical, and an unrated one counts as medium.
* **Fix**: the fixed version, if there is one.
* **Where it runs**: the most exposed affected version (**In production**, **Preview** or **Not deployed**), linked to each environment.
* **Who brings it in**: the app's own dependencies, Synthetiq's libraries or the app's starting template. Build-only packages are listed last as **Build tools only**.
* When it was first found and last scanned. Service findings also list the apps that bundle the service.

The summary line counts open, critical, in-production, fixable and build-only findings, and each count is a filter. You can also filter by app or service, severity, where it runs and fix, or search. Select a finding for its details and fix steps.

![Finding drawer for a critical jsforce vulnerability, showing what it is, two fix steps, and details including package, fixed-in version and the apps it is built into](https://mintcdn.com/synthetiq/hhugnC-v5exvzXyJ/images/platform-docs/console/security-finding.png?fit=max\&auto=format\&n=hhugnC-v5exvzXyJ\&q=85\&s=1edd024e68b035299ba2af3e848ac68b)

A finding opened: what it is, how to fix it, and which apps it's built into.

### Framework and Node runtime

**Framework** shows each app's release, how far behind it is and since when, and vulnerabilities only Synthetiq's libraries bring in. **By advisory** lists each advisory with the first release that doesn't have it.

![Framework tab listing three apps with their framework version, how many releases behind, and their framework vulnerabilities](https://mintcdn.com/synthetiq/hhugnC-v5exvzXyJ/images/platform-docs/console/security-framework.png?fit=max\&auto=format\&n=hhugnC-v5exvzXyJ\&q=85\&s=d562c88fc68464b35bbff91515647206)

Security › Framework: each app's release against the latest stable one.

**Node runtime** shows each deployed app's Node version. Your infrastructure sets the major version and a redeploy picks up the newest patch, so the fix is **Redeploy**.

![Node runtime tab with three apps: one behind with a Redeploy link, one up to date, and one not visible](https://mintcdn.com/synthetiq/hhugnC-v5exvzXyJ/images/platform-docs/console/security-node-runtime.png?fit=max\&auto=format\&n=hhugnC-v5exvzXyJ\&q=85\&s=e98ae513b0f3c13a72c3874b482eef95)

Security › Node runtime: one app needs a redeploy; one runs outside Synthetiq's AWS account, so its version isn't visible.

## How fixes ship

The Console doesn't change code. It gives the app's owners fix steps: upgrade the package and publish a new version; for an older release, update Synthetiq's libraries, refresh dependencies and publish; for an old Node runtime, redeploy. New versions go through [review](https://synthetiq.com/docs/platform-docs/console/reviews.md) like any change before you [deploy](https://synthetiq.com/docs/platform-docs/console/deployments.md#deploy-a-version) them. When a service publishes a fix, apps that bundle it get it when they update to that service version.

## Dismiss a finding

Open the finding, select **Dismiss** and pick a reason:

| Reason | Use it when |
| - | - |
| **Accepted risk** | It's real and you're living with it. Pick a review date: 30 days, 90 days or 6 months. |
| **False positive** | The scan got it wrong. |
| **Not used** | The affected code never runs. |

A note is required and shown to anyone who opens the finding later, along with who dismissed it and when. You can dismiss the same package and advisory across every app in the organization at once.

A dismissed finding leaves the open list and counts until its severity rises above what it was, or an accepted risk hits its review date. **Dismissed** lists them, and **Reopen** brings one back.

![Dismissed findings list showing one low-severity finding dismissed as accepted risk, with the note, who dismissed it and its reopen date](https://mintcdn.com/synthetiq/hhugnC-v5exvzXyJ/images/platform-docs/console/security-dismissed.png?fit=max\&auto=format\&n=hhugnC-v5exvzXyJ\&q=85\&s=e973a1f09d6b1bd75b097c5ad1e24821)

Security › Dismissed: an accepted risk with its reason, who accepted it and when it reopens.

## Who can do what

Everyone sees findings for the apps and services they contribute to or their teams own. People with the organization-wide view (`audit:read`) can switch to **Everything**, run **Scan now**, and dismiss or reopen findings.

## What the scan doesn't cover

The scan checks packages, the release of Synthetiq's libraries and the Node runtime. It doesn't scan your app's own code, package licenses, container images, secrets or infrastructure templates, and it doesn't test running apps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.