September 2021
Beginner
264 pages
7h 48m
English
Content preview from 97 Things Every Information Security Professional Should Know
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 78. DevOps for InfoSec Professionals
Sasha Rosenbaum
The term “DevOps” first appeared in 2009, at the eponymous DevOpsDays conference in Belgium.1 Since then, the term has become popular in the industry and evolved to cover a range of related concepts. In this article, we will review the two primary pillars of DevOps: culture and automation.
Culture
As computer science matured as a field, IT departments began to split vertically along the technology stack, creating separate teams for development, QA, application security, operations, and so on. In large organizations, these teams were often separated by a ticketing system, with lengthy handoffs and significant administrative overhead.
To make matters worse, it appeared that the teams had opposite incentives—developers were asked to create new features as quickly as possible, whereas operations were asked to prevent system outages. Since most outages occurred during new releases, operations were reluctant to push any changes to production. Many organizations delivered software on a two- to three-year cadence, and the process of creating a production-ready version could take months. Applications were often “down for maintenance” for entire weekends. Speed of innovation appeared to be in conflict with reliability.
As the world moved increasingly towards a software as a service (SaaS) model, organizations needed a way to ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.