Secure Development Lifecycle
How does Mendix manage secure change processes in software development?
Mendix enforces a Secure Development Lifecycle (SDL) across all teams responsible for the Mendix Platform, Mendix Cloud, and supporting applications. This process ensures that security, legal, and quality considerations are embedded from planning through post-release operations.
What secure development practices are in place?
All Mendix developers undergo periodic training on secure coding to prevent common vulnerabilities and properly handle sensitive data. When legal or security-related concerns arise (e.g., data privacy or open-source licensing), R&D teams consult with Mendix’s Security or Legal departments. Outsourced development teams are held to the same standards and compliance requirements as internal teams.
How is the product portfolio managed with security in mind?
The product portfolio is reviewed and synchronized by the Chief Product Officer, Product Management Board, and relevant product managers. Security and data privacy requirements are identified and addressed during the product vision and planning stages. Internal IT-supported apps are governed separately by the IT Program Board.
How is source code securely managed and controlled?
Access to source code is restricted to only developers and engineers and is only accessible through Mendix VPN and by authenticating with SSO. Access Control to repositories is managed by development teams with the CTO as end-responsible for RnD issued access to source code and the CIO as end-responsible for IT issues access to source code
How are peer reviews and code quality ensured?
Every significant code change undergoes peer review using the 4-eyes principle or pair programming. This ensures adherence to secure coding standards and prevents unauthorized changes. Developers cannot unilaterally push updates to production, enforcing proper separation of duties.
What change management controls are enforced?
Each change requires a documented story, risk assessment, rollback plan, peer review, testing, and managerial approval. These controls are built into the development process and are reviewed quarterly by auditors. Mendix also integrates automated security checks, such as Snyk for software composition analysis and Veracode for static application security testing.
How is test data handled securely?
Mendix ensures that test environments are logically isolated and free from confidential or sensitive data. Personas simulate users during testing, and all test data is deleted prior to release. Test documentation is retained for one year to support traceability and customer service.
What procedures govern product releases?
Release preparation includes comprehensive testing, risk assessment, and documentation, including versioning and rollback strategies. All releases require formal approval from a responsible manager. Releases are blocked if approval is missing. Code review tools also verify open-source license compliance before deployment.
What is the rollback or roll-forward strategy in case of post-release issues?
Mendix prioritizes a “roll forward” approach when resolving critical post-release issues – moving ahead to a new version that incorporates a fix while preserving audit trails. If rollback is necessary, data integrity and backup plans are carefully assessed before execution.
How is security maintained post-release?
Once deployed, Mendix products are continuously tested for vulnerabilities using automated tools, external testing partners, and a public bug bounty program. This ongoing evaluation ensures a strong security posture throughout a product’s lifecycle.
What happens when a product reaches end-of-life?
When a Mendix product is phased out, data is securely deleted in compliance with relevant laws and regulations. The Information Security and Privacy departments oversee this process to ensure legal and regulatory compliance.
For more information, see Conveyor.