AppSec platform
Checks code, libraries and secrets before release
SAST, SCA and secrets. Runs inside your perimeter, with no internet access.
Vulnerabilities · payments-apirelease 2.14
SQL injection
transfer/TransferDao.java:118
critical
log4j-core 2.14.1: update to 2.17.1
pom.xml · 3 CVE
critical
Cloud key in a .env file
config/.env:7
high
Insecure deserialization
api/ImportService.java:64
high
Checks3SAST, SCA and secrets in one platform
Languages7from Java and PL/SQL to 1C
Library ecosystems10Maven, npm, PyPI, NuGet and more
Pilot5weeks from preparation to results
01Platform
Three checks in one platform
Data path from input to vulnerability
- Full path
- through functions and files, from input to the dangerous sink
- Proven or suspicion
- findings are split: you see what is verified for certain
JavaPL/SQLC#JavaScriptTypeScriptPython1C
More about SAST uid = request.args["id"]
sql = "SELECT … WHERE id=" + uid
cursor.execute(sql)
SQL injection
One update closes several vulnerabilities
- By fix
- you see what to update and how many vulnerabilities it closes
- Vulnerability database
- inside your perimeter, matched without internet
MavennpmPyPINuGetGoComposerCargoPubSwiftCocoaPods
More about SCA CVE-2021-44228remote code execution
CVE-2021-45046code execution in certain configurations
CVE-2021-45105denial of service
One action Update log4j-core
2.14.1 → 2.17.1
closes three vulnerabilities Keys and passwords do not belong in code
- Where we look
- in code, configs, .env files and keystores
- Local specifics
- NCA RK digital signature keys, 1C exports and PL/SQL
passwordstokenscloud keysAI service keysdatabase connection stringsJWT secretskeystoresNCA RK digital signature keys
More about secrets config/.env3 secrets
-
DB_HOST=10.0.4.12 -
DB_USER=bank_app -
DB_PASSWORD=••••••••••••password -
JWT_SECRET=••••••••••••••••JWT secret -
LOG_LEVEL=info -
PAYMENT_KEY=••••••••••••payment service key
02Solutions
For your task, industry and stack
03Compliance
Clause-by-clause compliance report
For each clause you see the result and the reason in plain words.
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 | ✓ | ○ | — | ✓ | ○ | ✓ |
- ✓met
- verified by the platform itself
- ✕not met
- the reason is stated in plain words
- —no data
- the check was not run or does not apply
- ○outside the platform
- TRAIO has no remarks, the rest is confirmed by a person
Compliance report
ARDFM No. 53
3. Compliance
3met
1not met
0no data
2outside the platform
| Clause | Result | Basis |
|---|---|---|
| 148 | met | Scan No. 283: both types of analysis completed without failures |
| 149 | outside the platform | All languages of the checked version are supported: Java, TypeScript. AppSec confirms that the rules cover the seven vulnerability types |
| 150 | met | 412 components in 2 ecosystems, 412 matched against the vulnerability database, 9 vulnerabilities found |
| 151 | not met | Unresolved critical vulnerabilities: 2 (SAST 1, SCA 1, secrets 0) |
ARDFM No. 53 · payments-apipage 1 of 2
04Pilot
Pilot: five weeks
- Week 1 Pilot scope and preparation
- Week 2 Installation on your server
- Week 3 First repositories, SAST and SCA
- Week 4 Secrets and triage of findings
- Week 5 Results and next steps
05License
Annual subscription
Pricing is individual. We prepare a quote after the demo.
Request a quote- Model
- annual subscription
- Users
- unlimited
- Price
- individual
- Installation
- inside your perimeter
Demo
We will show it on your code
Leave a request: we will contact you within one business day to arrange a demo.
Request sent We will contact you within one business day.
TRAIO Insights