Cyber attacks frequently target personal and business data and it is critical to respond quickly to minimize the damage should a breach occur. Cyber incident response includes those plans and activities undertaken to identify, investigate, remediate, and assess damage and prevent further damage. It’s important for organizations to have a well-thought-out cyber incident response plan that includes detailed blueprints of the activities and owners for how your organization will respond to a security incident.
Imagine this scenario: It's Monday morning. As far as Mondays go, this looks to be a relatively light day. No changes were made over the weekend, so you do not anticipate any fires to put out. All you have to focus on are a couple meetings later this morning. Before those meetings begin, you check your favorite tech outlet (we recommend Cygilant Daily Security Briefing), and realize that a major vendor has announced a critical vulnerability. This vulnerability could potentially be on every node across your network. One executive finds out about this issue shortly after. He or she now needs to know where the company stands.
I spent the first few years of my career as a financial advisor and hated every day. It was boring, slow paced, and confusing to customers. Two words to describe asking grandma about her annuity over every holiday dinner: not fun. So in 2012, I joined the fast-paced, ever-changing world of cybersecurity. Over the past six years, I have held a number of sales roles, both in leadership and as an individual contributor. I have found it – thankfully – to be the exact opposite of the finance world… except when it comes to the confusion in the market.
Keeping the scale in your favor during an average production day always proves to be difficult. The list of vulnerabilities has grown unmanageable. In many cases, there are lengthy reports to review, spreadsheets to update, and worse, PDFs to comb through. Meanwhile, threat actors continue to develop zero-day vulnerabilities along with weaponizing known vulnerabilities; some of which go as far back as 2006.