Secure development
This page explains how Greenlegis ensures a secure development lifecycle, continuously protecting data and maintaining high quality standards at every stage of building its applications.
Secure development lifecycle
- Rigorous application of industry best practices in coding.
- Constant monitoring and security adjustments throughout development.
- Structured process to ensure security throughout planning, coding and testing.
Anonymized data in development
- Exclusive use of anonymized and obfuscated databases, with no link to real customer or user data.
- Assurance that no real personal information is accessible or used in non-production environments.
Validation processes
- 1Code reviewDetailed review of the source code by a second developer.
- 2Automated testingUnit and integration tests.
- 3QA team validationAdditional manual testing focused on quality, performance and security.
Application security: SAST and DAST
SAST – Static Application Security Testing
Analyzes source code, bytecode or binaries without executing them, identifying vulnerabilities from the earliest stages, such as injection flaws, poor authentication handling or input validation issues. It enables earlier fixes at lower cost and impact, and supports DevSecOps.
DAST – Dynamic Application Security Testing
Evaluates the running application, simulating real attacks to detect vulnerabilities that only appear at runtime, such as authentication flaws, sensitive data exposure or configuration issues. It does not require access to the source code and is useful for web applications, APIs and published services. It complements SAST by offering a practical view of the risks in production.