4 ms·
A company I worked for started a devops team. 3 years later and there's still not a single ops person on it. There were so many security holes in their group we
by CaptSpify 9y ago
A company I worked for started a devops team. 3 years later and there's still not a single ops person on it. There were so many security holes in their group we had to ban them from releasing to our servers, so now they have their own cloud setup that is bleeding money.
The frustrating thing is: I'd have loved to work closer with them. But every time we tried, the response was "You have no place here, your slowing the process down". We just wanted to automate the security testing, they decided that throwing the security tests out altogether was a better idea. I do admit that it was indeed faster....
- lowbloodsugar 9y agoJust because someone has an Ops title doesn't mean they know anything about security. I've worked places where the Ops team caused every security incident. Its a business leadership issue. When teams accept requests from the business and prioritize those requests over security then we have problems. Ops teams can be just as guilty of this as any other team.