Shift Left: Secure SDLC Explained | SecurAcademy Webinar

Поділитися
Вставка
  • Опубліковано 31 лип 2024
  • Recording of Secura's live webinar on April 2, 2020. For more information: secura.com/webinars
    Building software can be challenging. Getting your software out the door quickly, while it's usable and at the same time ensuring quality and performance, puts pressure on software development teams. The growing need for secure software products over the last years does not make this easier.
    A well-organised development process is key to keeping the software you deliver aligned to your business needs, and security needs to be part of that.
    In this webinar we will look at the benefits of 'shifting left': dealing with security earlier in the process. We will examine some of the activities you can perform and how you can organise these in your development process. We will leave you with some tips to get started.
    INTENDED AUDIENCE
    • Software Developers
    • Software Architects
    • Product Owners
    • Product Testers
    Building software is a true team effort and requires different roles. Whether you are involved in building software as a developer, architect, product owner, tester, scrum master or otherwise, we are all part of the same process.
    A secure development process therefore also involves the whole team. If you are part of a software development team, or interested in building software securely, this webinar is for you. We will not dive into application code or explain vulnerabilities here, but focus on the process and the activities of secure software development.
    AGENDA
    1. The benefits of shifting left
    2. A glimpse at SSD practices
    3. How to get started
    Curious to see what other webinars we have planned? Visit: www.secura.com/webinars
  • Наука та технологія

КОМЕНТАРІ • 2

  • @josephlesmana8832
    @josephlesmana8832 2 роки тому

    a gem!

  • @logiciananimal
    @logiciananimal 4 роки тому

    Shift left is vital, but I think one should also emphasize that the activities described have to be iterative, produce documents which are streams, not static, etc.