The Zero Trust model relies on high-intensity identity verification and authorization for each device and individual. Whether devices and individuals are within or outside the network boundary, access or data transfer on the private network is only permitted after successful verification. This process combines analysis, screening, and logging to verify the correctness of behavior and continuously monitor for signs of intrusion. If a user or device exhibits behavior inconsistent with past patterns, it is logged and monitored as a potential threat. For example, if Marcus from Acme Co. typically logs into the intranet from Columbus, Ohio, USA, but one day attempts to access Acme's intranet from Berlin, Germany, even if Marcus's username and password are correct, the Zero Trust policy would identify the anomaly in Marcus's behavior and take measures, such as presenting additional identity verification queries to confirm his user identity. This fundamental shift in strategy effectively guards against many common security threats. Attackers can no longer exploit vulnerabilities within the perimeter and misuse your sensitive data and applications by bypassing defense layers. There is no longer a moat. Only applications and users, each application or user must mutually authenticate their identity and verify authorization before access occurs. "Mutual authentication" occurs when both parties authenticate each other, such as a user with a username and password and an application authenticated through a digital certificate. |
Key Features for Implementing Zero Trust
|
|
Read more: https://www.akamai.com/zh/glossary/what-is-zero-trust |