Over the past two weeks, one of our consultants from the BiH office, Azure DevOps engineer Ahmed Babić, led an engaging on-site training program on Azure Pipelines, guiding participants from “zero to hero” level. It was a great opportunity and something we continuously strive for, to share knowledge among the teams, boosting our competency and the delivery of our projects. The training program included more than 20 participants, who attended all four organized sessions. The number of attendees ensured the training program remained engaging, sparking many discussions and prompting numerous questions.

Everyone in software development is under stress to make sure to not introduce any vulnerabilities to the application/code. If you do not have that mindset, then probably your security department will chase you after some scanning is being performed. They might run occasionally or on a scheduled basis some scans that might find vulnerabilities in your application. But, how do we minimize that possibility? It's not rocket science that you should first have a security-oriented mindset in your team, but also include some SCA (Source Composition Analysis), SAST (Static Application Security Testing), and DAST (Dynamic Application Security Testing) in your CI CD setup. 

Leveraging Bicep modules empowers teams to encapsulate and reuse resource configurations effectively, promoting consistency, modularity, and collaboration. As organizations strive to adhere to best practices for security and compliance, the use of private container registries for managing and distributing container images has gained significant traction. This introduces a layer of complexity to the deployment pipeline, as the integration of Bicep modules with private registries demands careful orchestration and configuration.

Have you ever heard of YAML- a weird name for some scripting language?

Well, if you are working within the software development industry and did not hear about it until now, you should probably keep reading this blog.