September - 2023ENTERPRISE SECURITY| | 9Think about it for a minute: How many security incidents have you heard about which truly affected a CSP beyond the instance of some of their customers? The answer is probably you've heard about very very very few, and rightfully so.What usually happens is that firms running their workloads in the cloud suffer cybersecurity incidents derived from attacks that rarely affect any other customer of their CSP through the same vector. These attacks normally originate from outside their perimeter rather than a security problem somewhere else at their supplier's network, and many times they leverage misconfiguration problems on the assets the customer is directly responsible for. One can't help wondering how that can be the case, especially considering that cyber security teams tend to be among the highest skilled of the IT industry, and therefore able to execute a full and comprehensive hardening of any asset. In my experience, the recipe to avoid this situation is based on two basic aspects that are easy to overlook: Assessing the need for a thorough reskilling exercise before jumping to the cloud. It's paramount to make sure that the knowledge of your security and IT teams is not only great for your traditional architecture, but also up to date when it comes to understanding the features available at the cloud service provider of your choice. Adhering to your partner indications in terms of security, and a governance model that lacks the ability to guarantee that the cyber security team is not only aware but has a say on each and every deployment in the cloud your organization decides to perform.At the end of the day, cyber attacks on a cloud-based environment are much like any other from an attacker's perspective, but can be much different from the defender position if those two elements were not carefully considered. It can be a really limiting factor to the ability of any CERT teams to react with the same speed and effectiveness they would have had had the attack happened against the systems they've always known. We should all be careful with this, design our move to the cloud by truly redefining our architecture rather than applying a lift and shift approach and make sure we leverage the plethora of advanced capabilities these new environments provide from time zero, thus sparing a good amount of sterile trial and error effort. ESIT'S PARAMOUNT TO MAKE SURE THAT THE KNOWLEDGE OF YOUR SECURITY AND IT TEAMS IS NOT ONLY GREAT FOR YOUR TRADITIONAL ARCHITECTURE, BUT ALSO UP TO DATE WHEN IT COMES TO UNDERSTANDING THE FEATURES AVAILABLE AT THE CLOUD SERVICE PROVIDER OF YOUR CHOICE
< Page 8 | Page 10 >