Quick start
Use this guide to complete the user journey in TRON.ASOC and perform the following actions:
- log in to the system;
- create your first project;
- configure a security check;
- start a scan;
- view scan results.
This guide is intended for users who already have an account in TRON.ASOC. If you haven't installed the system yet, start with the Installation and first login section.
Before you start
Make sure you meet the following requirements:
- you have the system login link, Username, and Password for your account (request them from your system administrator);
- your role has permission to create projects and security checks;
- your administrator has configured an integration with at least one scan source (for example, a repository) and security tool in the Integrations section. For more information about configuring integrations, see the Integrations section.
Step 1. Log in
To log in, follow these steps:
- Go to the authorization page using the link you received from your administrator.
- Enter your account Username and Password.
- Select Login.
When you log in for the first time, the system prompts you to change your password. Your new password must meet the password requirements set by your administrator.
After you log in, the Dashboard home page opens with general project statistics.
Step 2. Create a project
A project is a top-level entity that brings together layers, security checks, and scan results for a single product or service.
To create a project, follow these steps:
- Go to the Projects section.
- Select Add project.
- Enter the project code, name, Description, and Tags.
- Select Create.
For more information, see Create a project.
Step 3. Add a project layer
A project layer (pipeline) is an entity that groups security checks, for example, by environment, service, or container.
To add a project layer, follow these steps:
- Open the project overview page and go to the Project layer tab.
- Select Add layer.
- Select From scratch or From template if you've already configured a template.
- Enter the name, Description, Layer type, and, if necessary, associate a quality gate.
- Select Create.
If you've already configured a layer template for similar projects, creating a layer from the template will save time—most parameters will be filled in automatically.
For more information, see Create a layer from scratch and Create a layer from a template.
Step 4. Add a security check
A security check combines a scanning tool (for example, a SAST or SCA tool) with a scan source (for example, a repository). It starts the scan and returns the results.
To add a security check, follow these steps:
- In the project layer, select Add security check.
- Select a scan source and security tool from the integrations configured earlier.
- Complete the remaining form fields—the fields depend on the selected source and tool.
- Test the connection to the tool by selecting Check connection.
- Select Create.
You must select the scan source and tool from the integrations configured by the administrator. If you need to add new integrations with sources or tools, contact your TRON.ASOC administrator.
For more information, see Create a security check.
Step 5. Start a scan
You can start one security check or all checks in a layer:
- To start all security checks in a layer, select Start new scan on the project layer page. To start only one check, select the additional actions button in its row and select Start new scan.
- Wait for the check status to change from Scanning to Ready.
For more information, see Start a security check.
Step 6. View scan results
After the scan finishes, you can view the results in several sections:
- Dashboard—summary statistics and widgets for all projects. For more information, see the Dashboard section.
- Project report—a summary or detailed report for a specific project. For more information, see the Project report section.
- Security issues—a list of detected vulnerabilities with filters for severity, status, tool, and other parameters. For more information, see the Security issues section.
You can process detected issues by changing their status, assigning an owner, leaving a comment, or marking them as false positives. For more information, see the Process security issues section.
What's next?
- Configure Quality Gates to automatically block releases with critical vulnerabilities.
- Configure the security check integration with a CI/CD pipeline to start scans automatically with every build.
- Read the Work with security issues section to configure deduplication and vulnerability processing rules.
- If you plan to work through the API, create an API token and read the API documentation.