Exposed admin endpoint after a load balancer change
The weekly external run found an admin endpoint exposed after a load balancer change two days earlier. Nectar reproduced unauthenticated access to its health and config pages.
An annual pentest shows one week of your environment. Hayrok tests every week and after every relevant change, inside rules your team approves. Each attack step is checked against your own SIEM, EDR, WAF and cloud telemetry, so you also see whether your defenses responded. Every fix is retested automatically, and a finding closes only when the replay fails.
The test was thorough. Then the team shipped, the cloud changed, and a WAF rule was edited. None of that is in the report.
Deploys, cloud changes and new APIs land between engagements, untested.
Retests are scheduled, billed and delayed, so findings stay "pending verification" for months.
Few pentest reports show whether your SOC, EDR or WAF responded to each step.
You approve the plan. Nectar does the testing on a schedule and when things change. Your team reviews what matters.
Assets, environments, exclusions, test windows and approvers, set once and reviewed each quarter.
A weekly baseline plus runs triggered by deploys, cloud changes and new exposures.
Each step is matched to your SIEM, EDR, WAF and cloud telemetry.
When a fix ships, the same test runs again. The finding closes only when it fails.
Each surface has its own cadence and change triggers. Every step is also read against your telemetry, so each run doubles as a control and detection check.
| SURFACE | CADENCE | ALSO RUNS WHEN | LAST RUN | OPEN FINDINGS |
|---|---|---|---|---|
| External perimeterInternet-facing hosts, services and admin panels | Weekly | DNS or load balancer changes, new certificates | 3 days ago | 1 High |
| Web applications and APIsAuthenticated behavior, business logic, tenant isolation | Weekly | Deploys to tenant-scoped services | 1 day ago | 2 High3 Medium |
| CloudIAM, metadata, storage and cross-account trust | Weekly | Terraform applies, new accounts | 2 days ago | 1 Critical |
| IdentityAccounts, roles, tokens and permissions | Weekly | Role and policy changes | 2 days ago | 1 High |
| Internal networkLateral movement, credentials and segmentation | Monthly | Firewall and segmentation changes | 9 days ago | 2 Medium |
| AI featuresPrompt injection, tool access and retrieval | Per release | Model, prompt or tool changes | 4 days ago | None open |
No retest tickets, no waiting for next year's engagement. Select a stage to follow one finding from discovery to closure.
Each model has a place. Many teams keep a human-led engagement for depth and add continuous testing for everything in between.
| Annual pentest | Pentest as a service | Hayrok continuous | |
|---|---|---|---|
| How often | Once a year, sometimes twice | Scheduled engagements, often quarterly | Weekly, plus every relevant change |
| Who tests | A human team | Human testers on a platform | Nectar under your rules, with human review |
| Depth on novel chains | High | High | Broad and repeatable; pair with human engagements for novel work |
| Retesting fixes | Next engagement or extra cost | On request | Automatic on every fix |
| Controls and detections | Rarely reported | Sometimes reported | Read from your telemetry on every step |
| Evidence | A PDF report | Portal findings | Replayable records with approvals and history |
| Change triggers | None | None | Deploys, cloud and config changes |
The weekly baseline catches drift. Change triggers catch the rest within hours. Select a trigger type to see this week's runs.
Generate a pentest summary for a customer, an attestation letter for a deal, or a full export for an auditor, from the same live results. Select an output.
Many teams keep a human-led engagement for depth, compliance and novel attack chains, and use continuous testing for everything in between. Hayrok results can scope that engagement and retest its findings.
We will walk through scoping and approval, the weekly and change-triggered runs, how your telemetry is read on each step, and how fixes are retested automatically.