Overview of capabilities
The platform provides an API to automate application security testing tasks.
Use cases
- identifying security issues in applications during development;
- embedding security checks into application development processes;
- assessing the security of information systems based on automated analysis results;
- validating discovered issues and implementing a remediation workflow.
Deployment
The platform is hosted by the service provider and runs on hardware and software built on infrastructure as a service (IaaS) from cloud providers. It is designed for SaaS and managed service delivery models.
Key features
SolidLab SDP is a set of tools, scanners, services, and automation components that can be flexibly configured to your needs and are designed to identify security issues in applications.
The platform consists of independent subsystems, which makes it possible to:
- use only the subsystems required for specific tasks;
- change the set of subsystems in production without downtime for deployed components;
- optimize allocated compute resources.
Depending on the tasks, the platform may include:
- a centralized subsystem for processing and storing discovered issues and displaying results of other subsystems;
- a subsystem for identifying issues using static code analysis methods;
- a subsystem for dynamic application security testing;
- a subsystem for detecting exposed secrets in source code;
- a subsystem that analyzes infrastructure-as-code (IaC) definitions for security misconfigurations;
- a subsystem for analyzing third-party software components for known vulnerabilities;
- a subsystem for analyzing components inside container images for known vulnerabilities.
Subsystem capabilities
- retrieving source code for analysis from repositories;
- selecting subsystems used to analyze a particular information system;
- parallel execution of multiple analysis jobs and a job queue;
- exporting discovered issues to the centralized processing and storage subsystem;
- grouping results from multiple subsystems;
- filtering findings and verifying them with severity assessment;
- tracking remediation of findings;
- granular access control to analysis results;
- statistics on findings and report generation;
- finding issues through static analysis without compiling application source code;
- static analysis for C, C++, C#, Go, Java, JavaScript, Kotlin, TypeScript, Ruby, Rust, PHP, Python, Scala, and Swift;
- detecting issues via static analysis, including injections (e.g., XSS, SQLi, SSTI), user-data deserialization, SSRF, XXE, and RCE;
- mapping the attack surface during dynamic analysis by discovering entry points with static and dynamic techniques;
- detecting issues via dynamic analysis, including reflected XSS, DOM-based XSS, SQL injection, XXE, and path traversal;
- detecting exposed secrets in source code and commit history;
- infrastructure-as-code analysis (Terraform, Kubernetes, Docker, Ansible);
- finding vulnerabilities in dependencies (npm, Maven, Gradle, pip, Composer, Go, etc.);
- analyzing components inside Docker images for known vulnerabilities.
The subsystems use:
- proprietary vulnerability databases delivered with the platform;
- public vulnerability databases.