HarrierSecurity builds cloud and Kubernetes tooling for people who need to understand the path in front of them, not just stare at another pile of inventory.
The goal is simple: take the access you already have, pull the high-signal relationships forward, and show where identity, automation, runtime, telemetry, and routing choices can turn into real operator paths.
These tools are not trying to be exploitation frameworks. They are built for recon, validation, and proof boundaries that stay honest about what the current evidence can and cannot say.
HarrierOps Azure is an Azure reconnaissance CLI for operators who want to move past raw resource lists and see the paths that matter first. It surfaces persistence, evasion, resource hijacking, path masking, initial access, impact posture, and chained Azure movement from the identity and permissions you already hold.
Try the release container:
docker run --rm ghcr.io/harriersecurity/ho-azure:v1.2.0 helpHarrierOps Kube brings the same operator-first idea to Kubernetes. Start from a kubeconfig, pod foothold, service account, or token clue, then quickly answer what that access can reach, which workloads matter, and which service-account or RBAC paths deserve the next look.
The Azure lab gives you a disposable place to try the Azure tooling without pointing it at a production tenant or someone else's cloud. Stand up the lab, run the tool, then compare what the CLI shows against the Azure-side evidence the lab creates.
Cloud security gets noisy fast.
Most environments already have the pieces that matter: identities with too much reach, automation that can run on a schedule, apps with trusted routes, logging paths that can be made less useful, and workloads that quietly connect one control surface to another.
HarrierSecurity projects are built to make those relationships easier to see and easier to test. The tools should help an operator, defender, teammate, or curious learner answer:
- What identity am I actually using?
- What can it control right now?
- Which path matters first?
- Where does the evidence stop?
- What should I validate in a real lab before I trust the story?
If that is the kind of question you are trying to answer, start with HarrierOps Azure or HarrierOps Kube and run the first few commands. The useful parts should show up quickly.