Ops Authorization Methodology
Scope Gate
Confirm scope.md before any task start
scope.md must exist under the current project root
auth.status must be granted
network_profile.mode must be set to one of:
offline — no external network, only local files / VMs
lab_only — only lab/CTF network segments
authorized_target_only — only in-scope assets listed in in_scope.assets
unrestricted_lab — only with written authorization for an isolated experiment network
If scope.md is missing or auth.status != granted, STOP and report scope deficiency. Do not proceed with any analysis or tool invocation.
In-Scope and Out-of-Scope Assets
in_scope.assets
List every host, domain, APK path, binary, URL, or service that is authorized for analysis.
- If
in_scope.assets is empty and no offline sample path is set, STOP and report asset deficiency.
- Review
in_scope.assets before any recon, reverse, or exploit activity.
out_of_scope.assets
List activities and assets explicitly NOT authorized.
- Do not act on any asset not in
in_scope.assets or out_of_scope.assets.
- If an activity would cross into
out_of_scope, halt and re-evaluate scope.
Network Profile
network_profile.mode
Select the appropriate mode before any network-dependent step:
| Mode |
Allowed |
Prohibited |
offline |
Static analysis, local files, simulation |
Any external network connection, public RPC |
lab_only |
Lab/CTF roach machine network segment |
Production or unassigned IP addresses |
authorized_target_only |
Only assets listed in in_scope.assets |
Any asset outside the in-scope list |
unrestricted_lab |
Isolated experiment network (written authorization only) |
Production or any unisolated network |
MUST NOT use unrestricted_lab against production or any network without written authorization documentation.
Deliverables
The following deliverables are expected for every completed task:
report — a formal technical document in the user project directory (see docs-generator for templates)
field_journal — a succinct journal entry recording 3 key Evidence IDs + commands, 1 core Finding, and 1 reusable Path pattern
diagrams — any architecture or attack-path diagrams generated during the task
timeline — optional timeline summary, linkable to timeline.md
If any required deliverable is missing, pause and note the gap before proceeding to the next deliverable.
Constraints
timebox
- If a timebox is set in
scope.md, do not exceed it without explicit user consent.
- Report progress at the timebox boundary.
stealth
stealth level (low | medium | high) must match the authorized operation type.
- Higher stealth does not override authorization; it only changes observability.
data_handling
data_handling must be anonymize or no_user_pii.
- Do not store, log, or transmit real user PII, tokens, or passwords in any artifact, report, or journal entry.
Signoff and Ready-for-Act
ready_for_act
ready_for_act must be true before any analysis step, tool invocation, or target engagement.
- If
ready_for_act is false, STOP and either:
- Complete the missing scope/auth fields in
scope.md, or
- Obtain explicit user consent to proceed despite gaps.
checklist
Before setting ready_for_act = true, confirm every item:
If any checklist item is no, update scope.md before setting ready_for_act = true.
Minimal Viable Setup Command (read-only)
# Ensure scope.md exists and is valid
# If offline, confirm offline sample path is configured
# If lab, confirm lab network segment is set
# If authorized_target_only, confirm in_scope.assets lists only authorized targets
# If unrestricted_lab, confirm written authorization is on file
# Then set ready_for_act = true in scope.md
Version History
- 1.0: Initial release. Extracted from reverse-skill: ops/scope-contract.md, ops/role-map.md, ops/IDENTITY.md. No scripts, no toolchain coupling. Designed as a clean methodology-only skill for VS Code Copilot.
1---2name: ops-authorization-methodology3description: 'Authorization and scope methodology for security/penetration/red-team tasks. Read-only checklist: confirm scope.md, network_profile mode, in-scope/out-of-scope assets, deliverables, and stop/replan conditions. No scripts, no toolchain coupling.'4license: MIT5metadata:6 version: "1.0"7 source: https://skillmd.com/skills/jzkk720/ops-authorization-methodology8 upstream: reverse-skill (methodology extraction, no upstream toolchain coupling)9 port: >-10 Clean methodology-only port. No GPL/AGPL, no offensive toolchain, no client-specific11 script dependencies. Extracted from reverse-skill: ops/scope-contract.md, ops/role-map.md,12 ops/IDENTITY.md.13---1415# Ops Authorization Methodology1617## Scope Gate1819### Confirm scope.md before any task start2021- `scope.md` must exist under the current project root22- `auth.status` must be `granted`23- `network_profile.mode` must be set to one of:24 - `offline` — no external network, only local files / VMs25 - `lab_only` — only lab/CTF network segments26 - `authorized_target_only` — only in-scope assets listed in `in_scope.assets`27 - `unrestricted_lab` — only with written authorization for an isolated experiment network2829If `scope.md` is missing or `auth.status != granted`, **STOP** and report scope deficiency. Do not proceed with any analysis or tool invocation.3031## In-Scope and Out-of-Scope Assets3233### in_scope.assets3435List every host, domain, APK path, binary, URL, or service that is authorized for analysis.3637- If `in_scope.assets` is empty **and** no offline sample path is set, **STOP** and report asset deficiency.38- Review `in_scope.assets` before any recon, reverse, or exploit activity.3940### out_of_scope.assets4142List activities and assets explicitly NOT authorized.4344- Do not act on any asset not in `in_scope.assets` or `out_of_scope.assets`.45- If an activity would cross into `out_of_scope`, halt and re-evaluate scope.4647## Network Profile4849### network_profile.mode5051Select the appropriate mode before any network-dependent step:5253| Mode | Allowed | Prohibited |54|------|---------|------------|55| `offline` | Static analysis, local files, simulation | Any external network connection, public RPC |56| `lab_only` | Lab/CTF roach machine network segment | Production or unassigned IP addresses |57| `authorized_target_only` | Only assets listed in `in_scope.assets` | Any asset outside the in-scope list |58| `unrestricted_lab` | Isolated experiment network (written authorization only) | Production or any unisolated network |5960**MUST NOT** use `unrestricted_lab` against production or any network without written authorization documentation.6162## Deliverables6364The following deliverables are expected for every completed task:6566- `report` — a formal technical document in the user project directory (see docs-generator for templates)67- `field_journal` — a succinct journal entry recording 3 key Evidence IDs + commands, 1 core Finding, and 1 reusable Path pattern68- `diagrams` — any architecture or attack-path diagrams generated during the task69- `timeline` — optional timeline summary, linkable to `timeline.md`7071If any required deliverable is missing, **pause** and note the gap before proceeding to the next deliverable.7273## Constraints7475### timebox7677- If a timebox is set in `scope.md`, do not exceed it without explicit user consent.78- Report progress at the timebox boundary.7980### stealth8182- `stealth` level (`low` | `medium` | `high`) must match the authorized operation type.83- Higher stealth does not override authorization; it only changes observability.8485### data_handling8687- `data_handling` must be `anonymize` or `no_user_pii`.88- Do not store, log, or transmit real user PII, tokens, or passwords in any artifact, report, or journal entry.8990## Signoff and Ready-for-Act9192### ready_for_act9394- `ready_for_act` must be `true` before any analysis step, tool invocation, or target engagement.95- If `ready_for_act` is `false`, **STOP** and either:96 - Complete the missing scope/auth fields in `scope.md`, or97 - Obtain explicit user consent to proceed despite gaps.9899### checklist100101Before setting `ready_for_act = true`, confirm every item:102103- [ ] `auth.status = granted` in `scope.md`104- [ ] `in_scope.assets` non-empty OR offline sample path set105- [ ] `network_profile.mode` chosen and consistent with authorized scope106- [ ] `out_of_scope.assets` reviewed (no activity crosses into out-of-scope)107- [ ] `stealth` level appropriate for the operation type108- [ ] `data_handling = anonymize` or `no_user_pii`109- [ ] All required deliverables identified (report, field_journal, diagrams, timeline)110111If any checklist item is `no`, update `scope.md` before setting `ready_for_act = true`.112113## Minimal Viable Setup Command (read-only)114115```bash116# Ensure scope.md exists and is valid117# If offline, confirm offline sample path is configured118# If lab, confirm lab network segment is set119# If authorized_target_only, confirm in_scope.assets lists only authorized targets120# If unrestricted_lab, confirm written authorization is on file121122# Then set ready_for_act = true in scope.md123```124125---126## Version History127128- 1.0: Initial release. Extracted from reverse-skill: ops/scope-contract.md, ops/role-map.md, ops/IDENTITY.md. No scripts, no toolchain coupling. Designed as a clean methodology-only skill for VS Code Copilot.