Security

Defensive access path with segmentation

Follow an explicitly authorized user through identity checks, a policy enforcement point and an isolated application segment.

Restricted service segmentmanaged-user ↔ identityRequestRequestNarrowly allowedNarrowly allowedDecision logDecision logManaged user device192.0.2.15Managed user device — 192.0.2.15Identity providerIdentity providerPolicy enforcementPolicy enforcementMonitoringMonitoringIsolated application203.0.113.40Isolated application — 203.0.113.40
Legend

Current step

Verify identity and device state

The request is associated with an authenticated identity and a managed device before access is considered.

Review the boundary

Which component should enforce the service-specific decision, and what should be recorded?

Reveal diagnosis

The policy enforcement point grants only the approved application request; monitoring records identity, resource and outcome.

Trust is evaluated for the requested resource, not granted to an entire network because a device is inside it. Monitoring records the decision for later review.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Tags

  • zero trust
  • segmentation
  • identity
  • least privilege
  • defense

Lessons using this diagram