liveBook · Manning

Security perimeter

A security perimeter is a boundary separating protected systems, resources, or users from untrusted surroundings and controlling access between them.

How 2 Manning books explain it

Authorization in Action

Perimeter security is an approach that controls access primarily through network boundaries and location-based restrictions.

How it is used
Frames network location as a traditional access-control signal and contrasts it with identity- and context-based authorization.
How deep it goes
Defines the model, explains implicit trust and lateral movement, and describes retiring VPN paths, IP allowlists, and firewall exceptions.
Examples
Uses corporate VPN access, internal reporting tools, IP allowlists, firewall exceptions, cloud services, SaaS applications, and external collaborators.
What you can do after
Evaluate access architectures by identifying where network location overrides identity, device posture, and request context.

Read how Authorization in Action explains security perimeter →

Azure Security

The boundary that separates resources and users considered inside a security domain from those considered outside it.

How it is used
Frames Azure security around replacing a fixed corporate boundary with verification across cloud resources, users, and devices.
How deep it goes
Contrasts traditional perimeter trust with zero trust but stops short of implementation procedures or specific configuration controls.
Examples
Uses Microsoft 365, Salesforce CRM, mobile phones, tablets, and personal laptops to illustrate access beyond corporate network walls.
What you can do after
Evaluate access models by identifying where location-based trust fails and where identities require continuous verification.

Read how Azure Security explains security perimeter →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.