What strategies can you use to avoid creating a single point of failure?

309 views3 Comments
Sort By:
Oldest
CISO in Finance (non-banking)7 months ago
Vendor risk management and understanding your vendor is crucial. It's also important to understand where redundancies might be and ensure they are in place if you choose to go forward. For instance, if you're heavily dependent on Microsoft and if you're in the cloud, you need to consider the risks associated with that. However, if major vendors like Microsoft or AWS were to fail, it would likely indicate larger global issues. Therefore, it's important to do a risk assessment and decide whether you're willing to take that risk or not. Disaster recovery, vendor management, and other measures can help mitigate the risk, but at the end of the day, you may have to accept it or walk away.

1 Reply
Director of Information Security in Services (non-Government)7 months ago

Planning, backup, and disaster recovery are crucial. If the vendor is cloud-based, it's important to consider whether it's one of the major players like Microsoft, AWS, or Google. If these major players go down, it could have significant impacts on your business operations. Therefore, it's important to have a backup plan in case of such eventualities. This could be especially challenging if you're relying on a single vendor for multiple services. Having dual vendors for redundancy might not be feasible for many organizations due to cost considerations. Therefore, it's a tough task to completely plan for avoiding a single point of failure.

lock icon

Please join or sign in to view more content.

By joining the Peer Community, you'll get:

  • Peer Discussions and Polls
  • One-Minute Insights
  • Connect with like-minded individuals
Director of IT in Healthcare and Biotech7 months ago
The key strategy to avoid creating a single point of failure is understanding your requirements and what's driving them. This understanding helps in identifying potential points of failure. For instance, the viability of the company itself could be a potential point of failure. Therefore, it's crucial to effectively define your requirements, evaluate against them, and measure success. If you believe that an organization's suite of tools could be a single point of failure and you don't have ways to mitigate against that, you should consider not consolidating.

Content you might like

VP of Global IT and Cybersecurity in Manufacturing6 years ago
Have clear business requirements up front, make sure the proposal includes items such as scope, timeline, cost, resources.
Read More Comments
22.1k views3 Upvotes28 Comments

Implementation complete23%

Implementation in progress54%

Planned within the next 12 months12%

Not planned7%

Not enabling O365 on mobile2%

View Results
2.4k views2 Upvotes
Director of IT in IT Services4 days ago
Implementation of Zero trust architecture, its modules across the organisation is a priority for us. So, we will be implementing zero trust strategies in IAM, inline with overall strategy.
1.4k views1 Comment

Account deletion19%

Personal data (PII) deletion from a company's own data warehouses.55%

Personal data (PII) deletion from both a company's own data warehouses and connected SaaS tools.18%

Account deletion and PII deletion from both a company's own data warehouses and connected SaaS tools.7%

View Results
1.5k views2 Upvotes