News

Microsoft, Snyk secure open source development on Azure Cloud

0

Microsoft and Snyk have joined hands to protect and secure the development of applications and containers using open source and running on Azure Cloud.

With this alliance, Snyk announced its native integrations with Azure Cloud providing security throughout the software development life cycle (SDLC). The idea is to enable customers to secure their payloads and adopt open source and cloud more quickly and safely.

Snyk’s developer-first solution is said to offer integrated vulnerability management and remediation across the Azure Cloud SDLC – from code release to runtime. The Snyk integration enables DevSecOps, empowering developers to continue to release fast, while ensuring the security of their projects and assuring overall control and governance.

Snyk native integration with Azure Repos and Azure Pipelines will allow organisations to empower their developers to take control of security – from commit time through to CI/CD, the company said.

“As companies of all sizes continue to migrate to the cloud, with applications heavily powered by open source, Azure is providing the best environment for an easy and secure migration,” said Eduardo Laureano, Principal PM Manager at Azure Functions, Microsoft. “By partnering with Snyk to secure the software development life cycle on Azure, we’re giving customers the confidence to extend their use of open source technologies, such as Azure Functions, and accelerate their journeys towards digital transformation.”

For organizations adopting containerized applications, Snyk’s integration with Azure Container Registry scans all container images for vulnerabilities and provides actionable advice to eliminate the identified vulnerabilities.

In serverless environments, Snyk gives IT and development operations teams a detailed view of the security posture of the running applications. It enables Azure users to ensure that newly discovered vulnerabilities are acknowledged and remediated, and the team is empowered to gate the deployment to make sure no new vulnerabilities are introduced to the environment.