Charterhouse Group’s Post

https://lnkd.in/dj-2erg7 I have been saying this from day 1 when enterprises and critical organization opting for cloud migration. Industry should have a proper budget to handle cloud migration. Board of Directors priorities is interested in service not security

What are the lessons CIOs are taking to heart from CrowStrike fiasco ? A wake-up call for CIOs A primary concern for CIOs is vendor lock-in. The reliance on a single cloud provider, as demonstrated by the CrowdStrike incident, creates a single point of failure. If a critical service from that provider is disrupted, it can have far-reaching implications for an organization. To mitigate this risk, CIOs are likely to explore multicloud or hybrid cloud architectures, distributing workloads across multiple platforms.

I think after this incident everyone will question complete reliance on a single cloud provider… “A primary concern for CIOs is vendor lock-in. The reliance on a single cloud provider, as demonstrated by the CrowdStrike incident, creates a single point of failure. If a critical service from that provider is disrupted, it can have far-reaching implications for an organization. To mitigate this risk, CIOs are likely to explore multicloud or hybrid cloud architectures, distributing workloads across multiple platforms.”

Following the global IT outage caused by the security vender #crowdstrike, organisations are re-evaluating their #Cloud only, #Cloudfirst strategy on the basis that having balanced workload model with a mix of cloud and hybrid may have mitigated some of the recovery issues faced post event. A interesting perspective from CIO.com on the subject with a number of CxO level comments.

Plase take a moment to read the article from Gyana Swain and CIO Online on how the recent disruption caused by a CrowdStrike incident has prompted CIOs to reassess their cloud strategies. The event highlighted the risks of relying on a single vendor for cloud services. CIOs are now considering diversification of their cloud providers to enhance resilience and reduce dependency. This shift aims to ensure business continuity and mitigate the impact of potential future incidents.

The incident with CrowdStrike is a harsh reminder that systems can go down at anytime and it’s critical to have a business continuity plan in place. Many don’t realize that TierPoint can help with your BC/DR planning, execution and testing. We are also the experts in cloud strategy, partnering with multiple cloud providers, we bring an agnostic approach to placing your workloads in the best cloud. #hybridcloud #publiccloud #privatecloud #businesscontinuity #disasterrecovery

The recent CrowdStrike incident serves as a stark reminder that systems can fail unexpectedly, emphasizing the importance of having a robust business continuity plan. While many may not be aware, TierPoint offers comprehensive support for BC/DR planning, execution, and testing. Additionally, our expertise in cloud strategy allows us to take an agnostic approach when determining the best cloud environment for your workloads. #hybridcloud #BusinessContinuity, #Privatecloud, #DisasterRecovery

From this article - "A primary concern for CIOs is vendor lock-in. ... To mitigate this risk, CIOs are likely to explore multicloud or hybrid cloud architectures, distributing workloads across multiple platforms." (And as background on Unqork: We don't run on Windows, leverage secure by default Kubernetes workloads for resilience, and aren't impacted by these types of failures) https://lnkd.in/edguDZr3

The Crowdstrike incident demonstrates a few issues for CIO’s: the risk of cloud vendor lock-in (2) failure of establishing a testing culture in favour of speed to deploy (3) not enough redundancies built in. As someone whose been recruiting in this space for the past 8 years, I’ve noticed a lot of large enterprises have built hybrid cloud environments and some have even pivoted to private clouds with data centres built on the “edge”

Question to everyone: Is rethinking your cloud strategy the best first move in reaction to the Crowdstrike outage? Perhaps a better first move is to review your testing and rollback procedures? BCP/DR? Something else?