The CrowdStrike Incident: A much needed Wake-Up Call for the Business... and its IT posture.
Angelique Dawnbringer
Digital Trust | Information & Cybersecurity Advisor
Internal Audit would have caught it they say... I read multiple people overselling internal audits capability. I say; Hell no! I strongly disagree with the notion that internal audit would have caught this issue before it happened. In reality, auditors may not always possess (e.g., almost never) the specific knowledge and expertise to identify complex security vulnerabilities. It has very little to do with cybersecurity but rather the IT posture of companies...
This incident highlights the importance of first-line solution architecture design and domain architecture considerations from both the software supplier's and consumer's perspectives. Software can indeed fail, just like any other system, and it's essential to build resilient and fast systems capable of recovery, including adequate staffing and training based on continuity planning.
The truth is that IT issues are often perceived as solely technical problems, but they have significant business implications. The CrowdStrike incident serves as a prime example - an IT-related issue with substantial business consequences. It's crucial to recognize that IT issues require a strategic response, rather than just treating them as separate entities.
When we view IT as a distinct function, we neglect the broader picture. We focus on patching holes and addressing symptoms, rather than tackling the underlying causes of these issues. However, I firmly believe that IT is actually a business problem, not an IT problem in itself. The CrowdStrike incident shows us that IT issues have far-reaching consequences for businesses, making it essential to adopt a more holistic approach to risk management.
In this context, let's consider the role of Internal Audit or Assurance as part of our Third Line of Defense. While internal audit plays a critical role in assessing the effectiveness of controls implemented by operational teams (First Line of Defense), I question whether their expertise and resources are sufficient to cover the complex landscape of cyber threats. In reality, auditors may not always possess the specific knowledge and expertise to identify complex security vulnerabilities.
According to the three lines of defense model:
领英推荐
While internal audit is essential for ensuring that controls are in place and functioning as intended, I believe it's a stretch to assume that their primary role is to catch complex security vulnerabilities. In fact, this responsibility falls more squarely on the shoulders of operational teams (First Line of Defense) and risk management functions (Second Line of Defense).
To achieve a higher level of maturity, organizations should invest in people capacity - having sufficient personnel with the necessary expertise to handle various scenarios, from routine maintenance to complex crisis situations. This includes not only technical skills but also essential soft skills like communication, teamwork, and problem-solving.
Organizations should commit to developing their people capacity through training, upskilling, and reskilling opportunities for their IT staff and risk management functions. By doing so, we can transform IT into an asset that drives business growth and innovation, rather than a liability.
And as for governance? Well there is COBIT; ITIL, ISO bla bla bla bla bla....
Knowit Maker of Digital Trust
3 个月Angelique Dawnbringer thank you. What internal audit would identify a "read-out-of-bounds memory safety error in the CrowdStrike developed CSagent.sys driver"? Has anything like that ever happened?
CISO | Speaker | Technology Enthusiast | Father | Husband | Occasionally Gamer
4 个月"Internal Audit would have caught it" - what is the "it" we refer to here? If "it" refers to "3rd party dependencies", then yes sure, who doesn't have in their risk registry something related to 3rd parties or supply chain attacks? I do, and i choose to accept the risk. Besides that, i am not sure what IA would have contributed here. CS can go kaboom (it did), MS Updates can go kaboom (they have done so), and so on. What would be the recommendation here? Build everything yourself?
Interim CISO, CEO & Owner Akysec AB, CISM, CCSK(CSA), ISO 27005 Lead Risk Manager, ISO 27001 LI
4 个月If companies just started working with governance and assurance then I think most of these incidents would be avoided. Internal audit is a one off task and is not enough.
People & Product Leader | cloudcloud.dev
4 个月Hear hear! What was missing in the #crowdstrike incident wasn’t internal audit, but rather lack of focus on and sustained commitment to engineering excellence.
Architect - Analytics (ML/AI, BI), Data Management, Contractor
4 个月Love the article! Paperwork don’t solve/mitigate problems. Skillful and people with knowledge mitigate and forecast possible flaws. IMO