-
Notifications
You must be signed in to change notification settings - Fork 0
Command Guides
Colby Farley edited this page Apr 11, 2026
·
3 revisions
These pages turn HarrierOps Kube command intent into operator-facing guidance.
They are written to answer four practical questions quickly:
- what the command is for
- when to run it
- what to look for in the output
- what to do next if the command finds something important
images
Start with:
Then pivot based on what you learn:
- use chains when the next useful answer depends on a bounded joined path instead of one command at a time
- use exposure when outside-facing paths are already visible
- use workloads when the important question is which running thing changes the story first
- use service-accounts when workload-linked identity paths look more important than raw grants
- use rbac when you need the exact assignment evidence behind a capability or identity story
- use permissions when the real question is what the current session can do now
- use secrets when trust material or dependency paths matter more than general workload posture
- use privesc when you need the shortest honest answer to which path could broaden power next
For a fast first pass:
harrierops-kube whoami --output table
harrierops-kube inventory --output table
harrierops-kube exposure --output table
harrierops-kube workloads --output tableFor an identity and access follow-up:
harrierops-kube service-accounts --output table
harrierops-kube rbac --output table
harrierops-kube permissions --output table
harrierops-kube privesc --output table
harrierops-kube chains workload-identity-pivot --output tableFor a secret-path follow-up:
harrierops-kube secrets --output tableCore
Identity
Orchestration
Workload
Exposure
Secrets
Investigations
Reference
Later Depth
-
images(later depth surface, not yet a full guide page)