Security perimeter

As explained in Azure Security

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

A security perimeter separates resources and users treated as inside a security domain from those treated as outside. Traditional defenses protected this boundary with network walls, trusting what was inside and distrusting what was outside. section 1.6

Cloud services and diverse devices weaken that model: applications may sit outside the corporate network, while users connect from phones, tablets, laptops, or other locations. Access control therefore moves away from one fixed perimeter toward continuous verification. section 1.6

Apply the perimeter concept across the resources and access paths that require protection:

• Treat identity as the primary security perimeter because identities access cloud services and perform actions on resources. section 1.8
• Secure identities, data, applications, infrastructure, and networking resources rather than relying on a single network boundary. section 1.8
• Use a perimeter-less, zero trust approach that does not implicitly trust resources merely because they occupy a familiar location. section 1.6

Cloud access beyond the corporate walls

A user may reach Microsoft 365 or Salesforce CRM from a mobile phone, tablet, or personal laptop. Because these applications do not reside behind the corporate network, their location cannot establish trust; access must be verified instead. section 1.6

Figure 1.4 Azure environments usually include different resource types.

Use the resource categories to map perimeter controls across identities, data, applications, infrastructure, and networking resources. section 1.8

How Azure Security covers it

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 it assumes

Builds from the familiar distinction between trusted internal resources and untrusted external resources before challenging that assumption.

What you can do after

Evaluate access models by identifying where location-based trust fails and where identities require continuous verification.

How it connects

Connects security perimeter with zero trust, identity security, defense in depth, cloud services, and kill chain analysis.

liveBookmanning.com

Read Azure Security on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Authorization in ActionPerimeter security is an approach that controls access primarily through network boundaries and location-based restrictions.

Compare how 2 books explain security perimeter →

Related concepts

• policy-based access controlcontrasts with · Policy-based access control is an authorization model that determines access by evaluating defined policies against identities, resources, actions, attributes, and context.
• zero-trust networkingcontrasts with · Zero-trust networking is a security architecture that grants no implicit trust based on network location or prior access and verifies and authorizes access requests explicitly.
• physical access controlused by · Physical access control comprises mechanisms and procedures that restrict physical entry to facilities, equipment, or other protected assets based on authorization.
• authorizationconfigures · Authorization is the determination and enforcement of rules governing which subjects may access resources or perform operations.

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.