Snyk
Auditor Job Name: Snyk Python, Snyk Nodejs, Snyk Iac, Snyk Go Auditor image: registry.gitlab.com/whitespots-public/security-images/snyk-python:1.1233.0 registry.gitlab.com/whitespots-public/security-images/snyk-node:1.1233.0 registry.gitlab.com/whitespots-public/security-images/snyk-node:1.1233.0 registry.gitlab.com/whitespots-public/security-images/snyk-go:1.1233.0 AppSec Portal Importer Name: Snyk
Snyk is a multifunctional security tool designed to ensure the protection of your code from potential vulnerabilities. Here are the key features and functions:
Code Scanning: Snyk can analyze your source code, identify potential vulnerabilities, and provide detailed information about the issues found.
Dependency Analysis: The platform checks your project's dependencies, including open-source code, libraries, and frameworks, for known vulnerabilities.
Vulnerability Prioritization: Snyk assesses the severity of detected issues and provides recommendations on prioritizing their resolution.
Support for Various Programming Languages: The tool is compatible with various languages, enabling security in diverse projects.
Integration into CI/CD Pipelines: Snyk can easily integrate into your CI/CD processes, warning about issues at the early stages of development.
Container and IaC Support: Besides code and dependencies, Snyk analyzes vulnerabilities in containers and infrastructure as code configurations.
Integration with Various Development Tools: Snyk supports integration with popular development tools, facilitating seamless incorporation into your workflow.
This tool helps developers and security teams effectively manage and ensure security in various aspects of the development process.
Curl example
In this command, the following parameters are used:
-X POST: specifies the HTTP method to be used (in this case, POST)-H "Authorization: Token <authorization_token>": specifies the authorization token obtained from AppSec Portal.-H "Content-Type: multipart/form-data": specifies the content type of the request.-F "file=@<report_file_path>": specifies the path to the report file generated by the scanner.-F "product_name=<product_name>": specifies the name of the product being scanned.-F "product_type=<product_type>": specifies the type of the product being scanned.-F "scanner_name=<scanner_name>": specifies the name of the scanner used to generate the report (Snyk)-F "branch=<branch_name>": (optional) specifies the name of the branch in the source code repository (if applicable) This parameter is particularly useful when you want to associate the scan results with a specific branch in your repository. If not provided, the scan will be associated with the default branch
Asset information, if an auditor is used
-F "repository=<repository SSH URL>": If your product is code in a repository enter the address of your repository in a specific format, for example: git@gitlab.com:whitespots-public/appsec-portal.git-F "docker_image=<registry address>": If your product is image enter the address of the registry where your product is located, for example: registry.gitlab.com/whitespots-public/appsec-portal/back/auto_validator:latest-F "domain=<domain>": If your product is web enter the domain name of your product, for example: whitespots.io-F "host=<host>": If your product is web enter the IP address of your product, for example: 0.0.0.0-F "cloud_account=<Cloud Account Name>": if your product is a cloud account enter the cloud account name, for example: autotest-cloud_account
Last updated