Curated articles, resources, tips and trends from the DevOps World.
Summary: This is a summary of an article originally published by The New Stack. Read the full original article here →
Not long ago, enterprises relied on a combination of VPN and firewalls deployed within the network perimeter to secure their infrastructure and applications for providing remote access to users. Once users gained access to the network, they were implicitly trusted to access networks, servers, applications, and various endpoints.
The philosophy of implicitly trusting an entity within a network poses a huge security risk. Every asset within the enterprise — networks, subnets, servers & desktops, databases, Kubernetes clusters, internally hosted applications, and third-party applications- must be secured independently.
Instead of defining access policies per resource such as a server, Kubernetes cluster, or application, IAP centralizes the policy definitions and access control by mapping the identities registered with each resource.
Made with pure grit © 2024 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com