BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DevOps.com - ECPv5.16.4//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:DevOps.com
X-ORIGINAL-URL:https://devops.com
X-WR-CALDESC:Events for DevOps.com
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20170312T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20171105T060000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20170427T120000
DTEND;TZID=America/New_York:20170427T130000
DTSTAMP:20260904T192526
CREATED:20170606T154836Z
LAST-MODIFIED:20190907T051729Z
UID:115608-1493294400-1493298000@devops.com
SUMMARY:Security Implications for a DevOps Transformation
DESCRIPTION:If your organization is undergoing a DevOps transformation\, you’re probably thinking about where security fits in. All too often\, we tack on security testing at the end of the delivery process\, which means significant problems go undetected until development is complete. As we adopt DevOps principles and practices\, we enable a natural solution to this problem: ensure that security experts are involved throughout the delivery process. \nIn this webinar\, DevOps.com and Puppet will define a reference implementation of DevOps from the ground up\, by illustrating how the software delivery process evolves at a hypothetical startup. Once we’ve laid a technical foundation for DevOps\, we will discuss the implications for security. We will discuss: \n\nBenefits for and challenges to security during a DevOps transformation\nHow to craft a DevOps-ready security practice\nRefinements of a standard DevOps workflow to address security needs\n\nRECORDING\n \nSLIDES\n \n  \n 
URL:https://devops.com/webinars/security-implications-for-a-devops-transformation/
CATEGORIES:2017 Webinars
ATTACH;FMTTYPE=image/jpeg:https://devops.com/wp-content/uploads/2017/06/Implications.jpg
END:VEVENT
END:VCALENDAR