What it is DevSecOps and why this its a different to DevOps ?

DevOps and DevSecOps are both development methodologies that have emerged to address the increasing complexity and speed of modern software development. Here’s a brief comparison between the two:

DevOps

DevOps is a combination of two words, “Development” and “Operations.” It’s a collaborative approach that brings together the software development (Dev) and IT operations (Ops) teams to streamline the software development process. The goal of DevOps is to shorten the system’s development lifecycle while delivering features, fixes, and updates frequently in close alignment with business objectives.

Key concepts in DevOps include:

• Continuous integration and continuous delivery (CI/CD): These practices involve regularly merging code changes into a central repository, then testing and delivering the software product from this repository.
• Infrastructure as Code (IaC): This is the management of infrastructure (networks, virtual machines, load balancers, and connection topology) in a descriptive model, using the same versioning as DevOps team uses for source code.
• Monitoring and Logging: Keeping track of application performance and user activity to identify issues and trends.

DevSecOps

DevSecOps is a philosophy that integrates security practices within the DevOps process. DevSecOps involves creating a ‘Security as Code’ culture with ongoing, flexible collaboration between release engineers and security teams. The term DevSecOps was developed due to the growing realization that security should not be at the end of the development cycle. Instead, security should be integrated into every part of the development process.

Key concepts in DevSecOps include:

• Security automation: Automated security checks are included throughout the development process, reducing the risk of security issues making it to production.
• Security as code: Just as infrastructure as code treats infrastructure as a software system, security as code means applying the same principles to security. This could include automating security checks and protocols.
• Shift left on security: This means thinking about security as early as possible in the software supply chain. Instead of thinking about security at the end of development, it’s considered from the beginning and throughout the development lifecycle.

In essence, DevSecOps is an extension or evolution of DevOps. It’s DevOps done with security as a main focus, rather than as an afterthought or a separate stage of the process. Both methodologies aim to create more efficient, effective and resilient software development processes.

for more please follow :
https://owasp.org/www-project-devsecops-guideline