liveBook · Manning

Security rule

A security rule is a declarative configuration that specifies conditions and the permitted or prohibited behavior for matching requests, traffic, access, or settings.

How 2 Manning books explain it

Spring in Action, Sixth Edition

A security rule is a declarative condition specifying the security requirements for requests matching particular URL paths or patterns.

How it is used
Applies authorization requirements to URL paths in Spring Security web configuration.
How deep it goes
Explains SecurityFilterChain configuration, matcher ordering, roles, standard methods, and flexible SpEL expressions.
Examples
Uses /design and /orders as protected paths and / and /** as publicly permitted paths.
What you can do after
Apply it via Spring Security to configure role-based, authenticated, public, or expression-based request access.

Read how Spring in Action, Sixth Edition explains security rule →

Microsoft Azure in Action

A security rule is an ordered network-filtering rule that specifies traffic criteria and an allow or deny action.

How it is used
Filters inbound and outbound traffic at an NSG attached to a subnet or network interface.
How deep it goes
Defines matching fields, ordered evaluation, default rules, and overlap risks without detailing packet-processing internals.
Examples
Uses default SSH and deny-all rules plus an Azure PowerShell rule allowing restricted inbound RDP.
What you can do after
Operate/configure it with Azure PowerShell by creating an NSG, attaching it to a subnet, and adding prioritized rules.

Read how Microsoft Azure in Action explains security rule →

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.