Platform
TRAIO platform: from code to report
Three checks, a single vulnerability list, AppSec decisions and a report for the auditor. All inside your perimeter.
Openneeds triage and confirmed
12critical
31high
57medium
4overdue
Recent scansexample
payments-apimain done
mobile-bankrelease/2.14 not everything checked done
core-ledgerPL/SQL · main running
abs-1carchive done
01How it works
One platform: from code to report
Code GitLab or an archive with code
zip, 7z, tar.gz, tar
SASTyour code
SCAlibraries
Secretskeys and passwords
Decision What to fix before release
- Update log4j-core
- Check the SQL injection
- Remove the password from code
Report For the auditor
PDF by requirement clauses
02Checks
Three checks in one platform
SASTyour code
Data path from input to vulnerability
JavaPL/SQLC#JavaScriptTypeScriptPython1C
Learn more SCAlibraries
One update closes several vulnerabilities
MavennpmPyPINuGetGoComposerCargoPubSwiftCocoaPods
Learn more Secretskeys and passwords
Keys and passwords do not belong in code
passwordstokenscloud keysAI service keysdatabase connection stringsJWT secretskeystoresNCA RK digital signature keys
Learn more 03Vulnerabilities
From list to decision in two clicks
Findings from all three checks land in one list. Click a row in the example.
Vulnerabilities · payments-api
5needs triage 0confirmed 0dismissed
Example. Pick a row and make a decision
SQL injection
transfer/TransferDao.java:118
String q = "SELECT * FROM transfers WHERE id = " + id;Statement st = conn.createStatement();ResultSet rs = st.executeQuery(q);
The id value comes from the request and goes into the SQL text without parameters.
Four statusesneeds triage, confirmed, fixed, dismissed
Dismissal reasonfalse positive, tests only, risk accepted, mitigated outside
The developer proposesto dismiss, with a reason and a comment. AppSec decides
Fix deadlinethe organization sets days by severity. Overdue items show on the home screen
04Apps
Application: code, composition and change flow
- Components
- GitLab repositories and code archives in one application
- Composition
- frameworks, packages, databases, CI and containers detected from repository files
- Flow
- the path of a change from MR to prod, and what bypassed the checks
- Owners
- the application team and those responsible for the fix
Change
MRReviewMergedReleaseTestProd
Skipped checks Transfer limitspayments-api · !412
—
New sign-in screenmobile-bank · !87
—
Reports updateabs-1c · !23
no approval
Urgent exchange-rate fixcore-ledger · push
no MRno approval
Payment gateway switchpayments-api · !405
prod not via CI
examplechanges in 30 days
05Check coverage
You see what was checked and what was not
- A mark on every file
- checked, not checked or skipped, with a reason
- Scan gaps
- languages without rules, unparsed and oversized files are named explicitly
- In the report
- unchecked languages and their share of code are stated in the basis of the clause
Code · payments-apiscan No. 214
-
src/transfer/TransferDao.javachecked -
src/api/ImportService.javachecked -
db/pkg_report.pkbchecked -
mobile/app/Login.ktSAST does not check Kotlinnot checked -
vendor/jquery/jquery.jsthird-party codeskipped -
lib/legacy-auth.jarcompiledskipped -
test/fixtures/cards.jsontest dataskipped
examplenot everything checked
06Reports
Clause-by-clause compliance report
- Regulations
- ARDFM No. 53 and Order No. 111/NK (Kazakhstan)
- Four outcomes
- met, not met, no data, outside the platform. The reason in plain words
- on compliance and on application vulnerabilities
- Export
- CSV and SARIF for the auditor and the issue tracker
ComplianceARDFM No. 53
Organization ✓met: 2✕not met: 1—no data: 1○outside the platform: 2
| Application | cl. 148 | cl. 149 | cl. 150 | cl. 151 | cl. 152 | cl. 153 |
|---|---|---|---|---|---|---|
| payments-apiPDFlast scan 16.11.2026 | ✓ | ○ | ✓ | ✕ | ○ | ✓ |
| mobile-bankPDFlast scan 15.11.2026 | ✓ | ○ | ✓ | ✓ | ○ | ✓ |
| internet-bankPDFlast scan 15.11.2026 | ✓ | ○ | ✓ | ✓ | ○ | ✓ |
| card-processingPDFlast scan 14.11.2026 | ✓ | ○ | ✓ | ✕ | ○ | ✓ |
| abs-plsqlPDFlast scan 12.11.2026 | ✓ | ○ | — | ✓ | ○ | ✓ |
07Roles
Five roles, one permissions table
| Admin | Head of security | AppSec | PO | Developer | |
|---|---|---|---|---|---|
| Users and connections | |||||
| Applications and running scans | |||||
| Decision on a vulnerability | proposes | proposes | |||
| Accept risk | all levels | all levels | up to "Planned" | "Acceptable" | |
| Reveal a secret value | |||||
| Audit log |
Organization setting. A company can allow developers to decide on a vulnerability themselves: AppSec will see the decision in the audit log. The organization also sets the levels up to which each role may accept risk.
08Perimeter
Everything runs inside your perimeter
Updates Signed archive or update channel
Your perimeter
GitLab Your repositories
read-only access
TRAIO platform Checks and decisions
SAST, SCA, secrets
Report For the auditor PDF
Internet Not required
InstallationOn your servers, with no internet access
ServerUbuntu 22.04 and 24.04, RHEL 8 and 9
DataCode never leaves your infrastructure
Interface languagesRussian, Kazakh, English