Edmund AI Documentation
/DOCUMENTATION

Edmund secure development lifecycle (E-SDL)

Introduction

At Edmund we are committed to maintaining robust security standards throughout the entire lifecycle of software developed for our platform. To ensure security, reliability, and resilience of our products, we implement the Edmund Secure Development Lifecycle (E-SDL), integrating security best practices into each development phase.

This document outlines the mandatory security processes and standards that our development teams must follow when creating software solutions for our customers.

Development methodology

Edmund employs Agile and DevSecOps methodologies to foster iterative development, rapid deployments, and continuous security integration.

Lifecycle phases

1. Planning

  • Conduct threat modeling to identify potential security risks.

  • Perform security and privacy impact assessments.

  • Provide regular security training for development teams.

  • Clearly define security requirements and acceptance criteria.

2. Coding

  • Adhere to secure coding standards and guidelines.

  • Mandatory version control practices with commit signing for code authenticity.

  • Employ automated static application security testing (SAST).

  • Scan regularly for sensitive data and secrets using automated detection tools.

  • Conduct regular security-focused code reviews.

3. Build

  • Implement secure build practices.

  • Verify and digitally sign dependencies to ensure integrity.

  • Establish a trusted software supply chain through robust dependency management.

4. Testing

  • Execute extensive security validation and testing processes to confirm adherence to established security requirements.

  • Manage test data meticulously and securely, including robust practices around secret handling and secure data injection during the testing phases.

  • Conduct rigorous security assessments within a controlled testing environment to thoroughly validate software security posture.

5. Release

  • Conduct rigorous security assessments in quality assurance (QA) environments.

  • Provide a detailed Software Bill of Materials (SBOM).

  • Secure packaging with digital signatures and encryption.

  • Utilize secure and encrypted methods for distribution.

6. Deployment

  • Perform penetration tests prior to release.

  • Implement runtime application protection measures (WAF).

  • Execute comprehensive vulnerability scans on deployment environments.

7. Operations

  • Continuous monitoring and logging for security-related events.

  • Regular security patching and updates.

  • Use Cloud-Native Application Protection Platforms (CNAPP) for comprehensive environment protection.

  • Maintain vulnerability disclosure programs and regular security assessments.

8. Monitoring

  • Employ Security Information and Event Management (SIEM) solutions for threat analysis.

  • Conduct continuous vulnerability monitoring and reporting.

  • Integrate Extended Detection and Response (XDR) systems for complete security coverage.

Security tools and standards

Our development teams must utilize security tools and practices that meet these criteria:

  • Up-to-date tool versions actively maintained.

  • Seamless integration into CI/CD pipelines.

  • Assurance of source code privacy and integrity.

  • Regular validation and effectiveness assessments of all tools.

Compliance and audit

  • Development teams must demonstrate compliance through regular internal security audits.

  • Security incidents or vulnerabilities must be promptly addressed, documented, and communicated internally, with clear mitigation measures implemented.

Knowledge management

Development teams must maintain centralized documentation using standardized platforms (e.g., YouTrack) to enhance collaboration, consistency, and operational efficiency.

Training and awareness

Development teams are receiving ongoing security training and awareness to foster a proactive security culture.