Zero Trust
It is a holistic approach to network security that covers every device, every process, every person
More facts about zero trust
Everything must be verified, nothing is inherently trusted. Multi-factor authentication, encryption, system permissions, additional firewalls, monitoring and analytics, etc
Planes of Operation
Split the network into functional planes. Applies to physical, virtual, and cloud components
Data plane
-Process the frames, packets, and network data
-Processing, forwarding, trunking, encrypting, NAT
Control Plane
-Manages the actions of the data plane
-Defines policies and rules
-Determines how packets should be forwarded
-Routing tables, session tables, NAT tables
Adaptive identity
-Consider the source and the requested resources
-Multiple risk indicators - relationship to the organization, physical location, type of connection, IP address, etc
-Make the authentication stronger, if needed
Threat Scope Reduction
-Decrease the number of possible entry points
Policy-Driven Access Control
-Combine the adaptive identity with a predefined set of rules
Security zones
Security is more than a one-to-one relationship. Broad categorizations provide a security-related foundation.
Where are you coming from and where are you going?
-Trusted, untrusted
-internal network, external network
-VPN 1, VPN 5, VPN 11
-Marketing, IT, Accounting, Human Resources
Zones
Using the zones may be enough by itself to deny access. For example: Untrusted to Trusted zone traffic. Some zones are implicitly trusted. For example: Trusted to Internal zone traffic
Policy Enforcement Point
You can think of it as a gatekeeper.
Subjects and Systems
-End users, applications, non-human entities
-Allow, monitor, and terminate connections can consist of multiple connections working together
PEP
Policy enforcement point
PDP
Policy Decision Point
Applying trust in planes
-Policy Decision Point
There’s a process for making an authentication decision
-Policy Engine
Evaluates each access decision based on policy and other information sources. Grant, deny, revoke
-Policy Administrator
Communicates with the policy enforcement point, generates access tokens or credentials. Tells the PEP to allow or disallow access