The way we build, provision, maintain and secure apps continues to evolve. As agile development practices put pressure on operations, organizations move to DevOps where both functions are synchronized. This in turn puts pressure on the app security organization, and so we see more companies today adopting a DevSecOps model.
At the same time, the complexity of a typical environment has increased dramatically in recent years. Your app runs on a virtual server hosted in AWS. Your CI/CD pipeline sits in another public cloud environment. You have a managed WAF. You’re using another software as-a-service product owned by another vendor.
And then there are various internal teams that weigh in on any app or web development project—IT, app security, content, developers, project managers—plus the fact that each member of each team, both internal and external, is probably supporting multiple releases and business units.
When you’re trying to identify a problem among all of the possible permutations across all of those distributed entities, you face exponential complexity. So how do you immediately triage to resolve the problems that inevitably come up?
Sometimes called conversation-driven collaboration or conversation-driven DevOps, ChatOps is growing out of this need for a range of stakeholders to share data and keep all members of your extended, cross-functional team on the same page. It’s about anticipating that challenges will arise and building that fact into the broader development process.
ChatOps uses chat clients, chat bots and real-time communication tools to facilitate DevOps, and increasingly DevSecOps. In the ChatOps environment, the chat client serves as the primary communications channel across all stakeholders, providing visibility into the right ..
Support the originator by clicking the read the rest link below.
