Security assessment (penetration testing)
for applications and IT infrastructure
Practical penetration testing, adversary simulation, and assessment of real business resilience against attacks. We validate exploitability, demonstrate compromise paths, and help eliminate root causes.
Why run a security assessment
The goal is to obtain a practical risk assessment for scenarios that may compromise systems, steal data, enable fraud, disrupt business processes, or allow attackers to persist in the infrastructure.
Protecting business processes, customers, and data
We identify attack scenarios that may lead to unacceptable business impact and help address those risks before attackers exploit them.
Assessing IT and security process effectiveness
Hands-on assessment of processes such as account and access management, patch management, network segmentation, and monitoring and response.
Assessing software development processes and AI integration
In white-box testing, we identify both specific vulnerabilities and systemic issues in architecture, development processes, integrations with external services, and third-party component integration.
What the assessment covers
The scope is tailored to the assessment target and threat model. Below are the main areas a project may include.
Application systems
Web applications and APIs, mobile applications, applications using AI/ML and agentic systems, blockchain solutions, and smart contracts.
External perimeter
External perimeter of owned infrastructure, deployments in data centers and hosting environments, and cloud deployments.
Internal infrastructure
Active Directory, corporate network, wireless networks, development and CI/CD segments, and business process automation systems.
Isolated critical infrastructure
Critical information infrastructure (CII), special segments (treasury, Bank of Russia Customer Automated Workstation [ARM KBR], ATM management), OT networks and industrial control systems (ICS), and IT and security management segments.
Application delivery environments
Microservice architectures across all layers, container orchestration systems such as Kubernetes and Docker, and the effectiveness of overlay security controls such as WAF, CAPTCHA, and bot protection.
Physical perimeter, processes, and people
Access control systems, biometric control systems, employee resilience to social engineering, and effectiveness of security processes and monitoring tools.
Project formats
Testing can be performed with different levels of depth and transparency. We choose the format based on your goals, timeline, available input data, and acceptable impact on production.
Classic security assessment
Testing applications and infrastructure under an agreed threat model: from an external attacker profile to assessments with access to source code, architecture, and test environments.
- Finding and validating exploitable vulnerabilities
- Business logic and non-standard attack vector analysis
- Pinpointing vulnerabilities when source code is available
- Remediation and security hardening recommendations
External Attack Surface Checkup
A quick security assessment of the external perimeter for limited timelines and budgets, focused on the most critical risks.
- Critical vulnerability discovery and remediation prioritization
- Forgotten or unknown asset discovery
- Concise report: vulnerabilities and remediation recommendations
- Identifying assets that require deeper assessment
Real-world attack simulation
Testing the organization’s ability to detect, contain, and investigate adversary actions under realistic conditions.
- Critical asset compromise scenarios
- Assessing security operations center (SOC) actions
- Social engineering
- Testing whether an attack can progress inside the infrastructure
SOC collaboration
Assessment of coordination with the incident response team: the SOC is aware of the project, tracks the attacking team’s activities, and actively practices detection and response scenarios.
- Agreed attack scenarios and communication rules
- Assessment of SOC detection, actions, and response
- Review of strengths and weaknesses in the security approach
- Recommendations for improving monitoring and response
How the project works
The process is transparent to your team: regular status updates, approval of potentially dangerous checks, and immediate notification of critical risks as soon as they are found.
Define the scope and threat model
We agree on the scope, assessment target, permitted testing activities, and coordination procedures.
Study the target and attack surface
We adapt our methodology to the specifics of the application, infrastructure, or other assessment target.
Perform active testing
We use manual analysis, proprietary techniques, and both Russian and international methodologies.
Validate exploitability and risk
We validate exploitability, assess the severity of impact, and demonstrate business risk.
Deliver the report and support remediation
We deliver recommendations, answer questions, and perform retesting if needed.
What you get
The final report helps you not only fix individual vulnerabilities but also improve the maturity of your security, IT, and development processes.
Executive summary
A concise assessment of security posture, key risks, possible business impact, and priorities for decision-making.
Technical report
A complete list of validated findings, reproduction steps, proof of concept (PoC), and CVSS severity ratings.
Remediation recommendations
Practical remediation guidance, prioritized by risk reduction.
Why SolidLab
Our offensive security team combines project experience, security research, participation in CTF competitions and bug bounty programs, and proprietary methodologies for application and infrastructure assessment.
30+ experts
Practicing experts in application security assessment, modeling the actions of potential adversaries, and researching vulnerabilities in application systems and IT infrastructure.
700+ projects
Project experience across the finance, telecom, manufacturing, retail, IT, healthcare, transportation, and government sectors.
30+ CVEs
Vulnerabilities found in Google Chrome, Apple, Microsoft Exchange, VMware, Jenkins, TrueConf, cPanel, and others.
100+ bug bounty reports
Accepted reports in HackerOne, Standoff, Google, and other bug bounty programs, plus acknowledgments from major companies.
Team certifications
OSCP, OSWE, OSEP, CRTE, CRTP, CEH, BSCP, WAPT, CPTS, RTO, and other professional certifications.
Proprietary methods and R&D
Our methodologies are based on FSTEC, OWASP, PTES, and MITRE ATT&CK and are continuously updated to reflect current attack techniques and changes in the threat landscape.
Examples of publicly disclosed vulnerabilities
Google Chrome
CVE-2024-10229, CVE-2025-4664: vulnerabilities in browser security mechanisms.
TrueConf
CVE-2022-46763, CVE-2022-46764: critical vulnerabilities, including unauthenticated SQL command execution.
VMware vCenter
A series of vulnerabilities, including CVE-2021-22005, documented in VMware security bulletin VMSA-2021-0020.
Jenkins
CVE-2019-1003029: sandbox bypass enabling arbitrary code execution on the Jenkins controller.
Microsoft Exchange
CVE-2024-49040: sender spoofing in Microsoft Exchange.
cPanel
CVE-2025-66429: privilege escalation to root.
Questions and answers
How is security assessment different from automated scanning?
Scanners help identify some common issues, but they cannot assess business logic, combine findings into attack chains, systematically analyze ways to bypass security controls, or evaluate potential impact on business processes. We use tools as part of the process, but the key value lies in manual analysis, exploit validation, and in-depth analytical work: developing assessment methodologies, evaluating the severity of identified weaknesses, and formulating recommendations to reduce the identified risks.
Can testing be performed in production?
Yes, provided we jointly develop and agree on a testing plan. We discuss the testing conditions: the types and timing of testing activities, an emergency communication plan with the operations team, and procedures for approving specific tests. Keep in mind that real attackers will target production environments however they choose.
When should source code access be provided?
White-box assessment has several advantages. First, it provides more comprehensive coverage: source code access makes it possible to find vulnerabilities that cannot be discovered through black-box testing. Second, for large applications, white-box assessment is more efficient in terms of effort and cost than black-box assessment. Third, remediation recommendations based on code analysis are more specific and account for the codebase’s characteristics: they can even address architectural and coding-style issues, unlike the more general recommendations produced by black-box assessment.
How fast are critical vulnerabilities reported?
Information about critical weaknesses is communicated as soon as they are discovered and their severity is confirmed. This lets your team promptly remediate the weaknesses or reduce the risk in another way, for example by configuring the WAF.
What happens after the report?
We answer the technical team’s questions, help interpret recommendations, and can perform retesting after fixes.
Test real-world attack scenarios before attackers do
Tell us which systems you need to assess. We will propose the right assessment format, scope, and testing plan.
Discuss a project