Rootwall

Example scope classes

A scope class is the page of rules that says what a provider may do on your systems, what needs your authority, what each side reports, and what each breach costs. These are worked examples, one per scenario, so you can see the shape before you write yours.

Every example here is illustrative. None binds anybody, and no member is admitted into any of them. The real one for your systems is written with you.

The examples

  1. A provider manages your log collector over VPN. The provider connects over a VPN, then SSH, to the servers that forward your logs to your security operations platform. Configuration changes need your approved change reference. Both sides report every session and every change. 25 September 2026
  2. Read-only access to your API. A provider reads records through your API on behalf of a named person, within limits per hour and per day. Also explains what a scope class can and cannot say. 3 September 2026, revised 25 September 2026

More scenarios will be added. Each keeps its own address, so a link to one never changes.