Articles

Anti-Patterns in Incident Response That You Should Unlearn

,

It is important to invest time and effort in understanding why a system performs the way it does and how we can improve it. Companies continue with practices that yield successful results but ignoring anti-patterns can be far worse than choosing rigid processes. In this article, we will explore anti-patterns in incident response and why you should unlearn those.

Common Anti-Patterns in Incident Response 

Just Get Everyone on the Call 

Alerting everyone each time an incident is detected is not the best of practices. Sometimes notifying everyone is easier or adds value. For example:

Source de l’article sur DZONE

/par

5 On-Call Practices To Help You Sleep Through the Night

,

On-call: you may see it as a necessary evil. When fast incident response can make or break your reputation, designating people across the team to be ready to react at all hours of the day is a necessity.  But, this often creates immense stress while eating into personal lives. It isn’t a surprise that many engineers have horror stories about the difficulty of carrying a pager.

But does on-call have to be so dreadful? No way. Here are five best practices to help your team respond quicker and build more resilient systems.

Source de l’article sur DZONE

/par

How to Provide Remote Incident Response During the Coronavirus Times

, , ,

While the Coronavirus pandemic continues to strike chaos across the global economies, threat actors keep on launching cyberattacks on organizations from all sizes and verticals. IR providers face a unique challenge when approached by these organizations since, due to the Coronavirus mass quarantine, conducting incident response engagements by arriving physically to the customers’ offices is
Source de l’article sur The Hacker News

/0 Commentaires/par

Maximizing Your IT Team’s Incident Response Speed

,

The reality of IT support is that engineers cannot avoid downtime. No matter how responsible managers are in ensuring regular maintenance and repair, incidents will happen. Sites will fill. Servers will fill up. APIs will fail. When these incidents do occur, it is important that IT teams are well trained and have the necessary equipment to ensure a rapid incident response.

However, incident response is not as easy as simply creating a check list for teams to follow. When incidents occur, there are often conflicting priorities between restoring availability and investigating the causes of the incident. For example, Security incident response teams and infrastructure teams operate with different sets of assumptions and priorities when resolving issues. If these separate priorities are not effectively managed before-hand, there can lead to the duplication of work, delays in handoffs, and faulty results.

Source de l’article sur DZone

/0 Commentaires/par