|
| 1 | +# SBOM monitor |
| 2 | + |
| 3 | +**Feature availability:** This feature is available to customers on Snyk Enterprise plans. |
| 4 | + |
| 5 | +## Usage |
| 6 | + |
| 7 | +`snyk monitor [<OPTIONS>]` |
| 8 | + |
| 9 | +## Description |
| 10 | + |
| 11 | +The `snyk sbom monitor` command creates a target and projects in your Snyk account to be continuously monitored for open-source vulnerabilities and license issues, sending the results to [snyk.io](https://snyk.io) |
| 12 | + |
| 13 | +Use the `sbom monitor` command to take a snapshot of dependencies detected in your SBOM to be monitored. Choose a test frequency in your Settings if you want to change the frequency from the default, which is daily. |
| 14 | + |
| 15 | +After running the `snyk sbom monitor` command, log in to the Snyk website and view your projects to see the monitor and related issues. |
| 16 | + |
| 17 | +If you make changes to your SBOM, you must run the `sbom monitor` command again.  |
| 18 | + |
| 19 | +## Exit codes |
| 20 | + |
| 21 | +Possible exit codes and their meaning: |
| 22 | + |
| 23 | +**0**: success, snapshot created\ |
| 24 | +**2**: failure, try to re-run the command. Use `-d` to output the debug logs. |
| 25 | + |
| 26 | +## Configure the Snyk CLI |
| 27 | + |
| 28 | +You can use environment variables to configure the Snyk CLI and set variables for connecting with the Snyk API. See [Configure the Snyk CLI](https://docs.snyk.io/snyk-cli/configure-the-snyk-cli) |
| 29 | + |
| 30 | +## Debug |
| 31 | + |
| 32 | +Use the `-d` option to output the debug logs. |
| 33 | + |
| 34 | +## Options |
| 35 | + |
| 36 | +### `--experimental` |
| 37 | + |
| 38 | +Required. Use experimental command features. This option is currently required as the command is in its experimental phase. |
| 39 | + |
| 40 | +### `--file=<FILE_PATH>` |
| 41 | + |
| 42 | +Required. Specify the file path of the SBOM document. |
| 43 | + |
| 44 | +The `snyk sbom monitor` command accepts the following file formats: |
| 45 | + |
| 46 | +- CycloneDX: JSON version 1.4, 1.5, and 1.6 |
| 47 | +- SPDX: JSON version 2.3 |
| 48 | + |
| 49 | +Packages and components within the provided SBOM file must be identified by a Package URL (`purl`). |
| 50 | + |
| 51 | +Supported purl types are: `apk`, `cargo`, `cocoapods`, `composer`, `deb`, `gem`, `generic`, `golang`, `hex`, `maven`, `npm`, `nuget`, `pub`, `pypi`, `rpm`, `swift` |
| 52 | + |
| 53 | +Example: `$ snyk sbom monitor --experimental --file=bom.cdx.json`  |
| 54 | + |
| 55 | +### `--remote-repo-url=<URL>` |
| 56 | + |
| 57 | +Set or override the remote URL for the repository. |
| 58 | + |
| 59 | +Example: `--remote-repo-url=https://gitlab.com/example/project` will create a target for given URL, and on the UI it would be visible as `/example/project/` . |
| 60 | + |
| 61 | +### `--target-reference=<TARGET_REFERENCE>` |
| 62 | + |
| 63 | +Specify a reference that differentiates this project, for example, a branch name or version. Projects having the same reference can be grouped based on that reference.  |
| 64 | + |
| 65 | +For more information, see [Group projects by branch or version for monitoring](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/group-projects-by-branch-or-version-for-monitoring) |
| 66 | + |
| 67 | +### `--policy-path=<PATH_TO_POLICY_FILE>` |
| 68 | + |
| 69 | +Manually pass a path to a `.snyk` policy file. |
| 70 | + |
| 71 | +### `--org=<ORG_ID>` |
| 72 | + |
| 73 | +Specify the `<ORG_ID>` to run Snyk commands tied to a specific Snyk Organization. The `<ORG_ID>` influences some features availability and private test limits. |
| 74 | + |
| 75 | +If you have multiple Organizations, you can set a default from the CLI using: |
| 76 | + |
| 77 | +`$ snyk config set org=<ORG_ID>` |
| 78 | + |
| 79 | +Set a default to ensure all newly monitored projects are created under your default Organization. If you need to override the default, use the `--org=<ORG_ID>` option. |
| 80 | + |
| 81 | +Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account) |
| 82 | + |
| 83 | +**Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API. |
| 84 | + |
| 85 | +`orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://app.snyk.io/org/[orgslugname]`. The orgname does not work. |
| 86 | + |
| 87 | +For more information, see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli) |
0 commit comments