Secure development practices

Introduction

NAGRAVISION integrates security as a foundational aspect of its operations, treating it as a core element of product development and service delivery. The company maintains a comprehensive Information Security Management System (ISMS), certified under ISO/IEC 27001, and extended with ISO/IEC 27017 and ISO/IEC 27018 to address cloud security and data privacy. As part of this ISMS, NAGRAVISION has defined and implemented a Secure Software Development Lifecycle (SSDLC) that governs how software is designed, developed, tested, and deployed across the organisation. The following document outlines the key components of this lifecycle, describing the practices NAGRAVISION applies to ensure the security and integrity of its software products.

Security by design

Security is integrated from the earliest stages of product development. NAGRAVISION incorporates security considerations during requirement gathering and design, documenting them as part of acceptance criteria. The process includes security reviews or threat modeling and engages security experts when needed. Secure design principles – such as least privilege, defense in depth, fail-safe defaults, and secure defaults – are consistently applied. Sensitive data, including personal information and cryptographic material, is identified and protected from the outset. Development, testing, staging, and production environments are clearly separated to prevent data leakage and unauthorised access. Data is safeguarded following internal data classification policies.

Security in implementation

During the development phase, NAGRAVISION applies secure coding practices aligned with industry recognised guidelines such as OWASP Top10. Coding guidelines are defined, regularly updated, and communicated across teams. Code is written to meet both functional and security requirements, with attention to input validation, error handling, and secure data management. Code reviews are performed with dedicated security focus on sensitive areas such as those involving authentication, authorisation, data handling, and external integrations. Hard-coded secrets are avoided, secure libraries are used, and cryptographic operations follow best practices. When generative AI tools are used, the resulting code is reviewed with the same rigor as manually-written code. Only approved tools are used, in compliance with the Kudelski Group’s Responsible AI Guideline and data classification policy.

Security in CI/CD

Automated security checks are embedded throughout the development lifecycle. NAGRAVISION integrates static and dynamic code analysis, dependency checking, and infrastructure-as-code scanning into CI/CD pipelines. Static Application Security Testing (SAST) tools are used to detect secrets, insecure patterns, and common vulnerabilities before code is merged. Dynamic Application Security Testing (DAST) complements the testing of externally exposed services and APIs. All findings are triaged and resolved in accordance with NAGRAVISION’s vulnerability management standards. Software Composition Analysis (SCA) tools are used to scan third-party libraries and dependencies for known vulnerabilities, and compliance with licensing and legal requirements is verified. Infrastructure code is scanned using tools appropriate for IaC to detect misconfigurations and risks. Security testing includes both positive and negative validation of critical areas such as authentication and input validation. Penetration tests are conducted annually, preferably by external security firms.

NAGRAVISION maintains an inventory of internet‑facing assets and runs scheduled perimeter vulnerability scans. Checks include service exposure, TLS configuration and common web/network weaknesses. Newly disclosed vulnerabilities are monitored continuously through vendor advisories, public feeds, and leveraging the services of the group Cyber Security services of Kudelski Security.
Remediation follows defined service levels based on severity, exploitability, and business context; urgent fixes are expedited.

Change management and deployment

Deployment processes include secure configuration validation and rollback mechanisms to address failures or post-release vulnerabilities. Changes to software, infrastructure-as-code, and related configurations follow a formal change management process to ensure traceability, accountability, and risk mitigation. Before going to production, new code releases undergo a formal approval process to ensure security and risk considerations are addressed.

Training and awareness

NAGRAVISION provides training and awareness programs for personnel involved in software development. Security Champions and structured initiatives, using platforms such as SecureFlag, are part of this approach. Developers, architects, product owners, and other stakeholders participate in role-specific awareness activities. These programs communicate responsibilities and address the security implications of their work, referencing standards such as OWASP.