When network architectures were simpler, so was protecting apps and application programming interfaces (APIs). They were predominantly on-premises, so defense-in-depth practices could be applied to enterprise networks. While far from perfect, this approach provided multilayer security defenses to protect apps and APIs.
As network architectures gradually became more complex, so did protecting apps and APIs. The on-premises enterprise environment gave way to a hybrid mix of on-premises, data center, and multiple cloud environments. These days, hybrid and multicloud environments are more the rule than they are the exception. They introduce complexity and challenges that make it significantly more difficult for organizations to apply defense-in-depth practices to protect apps and APIs.
While the idea of rebuilding the enterprise perimeter doesn’t make much sense in the current state, perhaps there is another way to bring requisite protections to apps and APIs. What if organizations could open an umbrella — a digital shield, if you will — around their hybrid and multicloud environments? This would allow them to add layers of protections that would, at least logically speaking, bring defense-in-depth practices to modern network architectures.
What are some of the essential elements and functionality of a digital shield? I’ll explain 10 of them here.
1. Standardized Communication
The first step in protecting apps and APIs is standardization across different environments. This doesn’t mean that all environments need to be homogeneous, of course. Rather, it means that all environments need a common, central management interface. There also needs to be a straightforward way to understand what environments exist, where they are, how they are connected, and what is running…
read more www.darkreading.com
Terms of use and third-party services. More here.
Soccer | NFL | NBA | Ads. Amazon
Sports Fan Rings | Sports Fan Football | Sports Fan Jerseys | Sports Fan T-Shirts | Sports Fan Shoes | Sports Fan Jewelry | Puffer Jackets |