Design Partner Program
CONTINUOUS PENETRATION TESTING

Continuous Penetration Testing: Find It the Week It Ships, Not the Quarter After

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.

exposure_window · last 12 months6 exploitable issues introduced
TEST RUNS
CPT-0402Open S3 bucket after migration
6d to find
CPT-0407WAF rule weakened
2d to find
CPT-0411Cross-tenant export bug
4d to find
CPT-0415New API without auth
5d to find
CPT-0418Exposed admin endpoint
6d to find
CPT-0423Over-scoped CI role
6d to find
DECJANFEBMARAPRMAYJUNJULAUGSEPOCTNOV
TEST RUNS52
ISSUES FOUND IN WINDOW6 / 6
AVERAGE DAYS EXPOSED5d
TOTAL EXPOSURE DAYS29
01 · THE PROBLEM

A Pentest Report Starts Aging the Day It Lands

The test was thorough. Then the team shipped, the cloud changed, and a WAF rule was edited. None of that is in the report.

CHANGE

Your environment moves weekly

Deploys, cloud changes and new APIs land between engagements, untested.

RETESTS

Fixes wait for the next test

Retests are scheduled, billed and delayed, so findings stay "pending verification" for months.

DEFENSES

Reports say what broke, not who noticed

Few pentest reports show whether your SOC, EDR or WAF responded to each step.

02 · HOW IT WORKS

Scope Once, Test Always, Retest Every Fix

You approve the plan. Nectar does the testing on a schedule and when things change. Your team reviews what matters.

  1. 01 · SCOPEHive

    Approve scope and rules

    Assets, environments, exclusions, test windows and approvers, set once and reviewed each quarter.

  2. 02 · TESTNectar

    Run weekly and on change

    A weekly baseline plus runs triggered by deploys, cloud changes and new exposures.

  3. 03 · READHive

    Check your defenses on every step

    Each step is matched to your SIEM, EDR, WAF and cloud telemetry.

  4. 04 · RETESTNectar

    Replay every fix

    When a fix ships, the same test runs again. The finding closes only when it fails.

03 · WHAT RUNS AND WHEN

Every Surface a Pentest Covers, on a Schedule You Set

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.

SURFACECADENCEALSO RUNS WHENLAST RUNOPEN FINDINGS
External perimeterInternet-facing hosts, services and admin panelsWeeklyDNS or load balancer changes, new certificates3 days ago1 High
Web applications and APIsAuthenticated behavior, business logic, tenant isolationWeeklyDeploys to tenant-scoped services1 day ago2 High3 Medium
CloudIAM, metadata, storage and cross-account trustWeeklyTerraform applies, new accounts2 days ago1 Critical
IdentityAccounts, roles, tokens and permissionsWeeklyRole and policy changes2 days ago1 High
Internal networkLateral movement, credentials and segmentationMonthlyFirewall and segmentation changes9 days ago2 Medium
AI featuresPrompt injection, tool access and retrievalPer releaseModel, prompt or tool changes4 days agoNone open
04 · FROM FINDING TO VERIFIED FIX

A Finding Closes Only When the Replay Fails

No retest tickets, no waiting for next year's engagement. Select a stage to follow one finding from discovery to closure.

CPT-0418 · discovered HighFound

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.

TELEMETRYWAFLogged, no blockSIEMNo alertExposureInternet-wide
05 · COMPARE TESTING MODELS

Annual Pentest, Pentest as a Service, or Continuous

Each model has a place. Many teams keep a human-led engagement for depth and add continuous testing for everything in between.

Annual pentestPentest as a serviceHayrok continuous
How oftenOnce a year, sometimes twiceScheduled engagements, often quarterlyWeekly, plus every relevant change
Who testsA human teamHuman testers on a platformNectar under your rules, with human review
Depth on novel chainsHighHighBroad and repeatable; pair with human engagements for novel work
Retesting fixesNext engagement or extra costOn requestAutomatic on every fix
Controls and detectionsRarely reportedSometimes reportedRead from your telemetry on every step
EvidenceA PDF reportPortal findingsReplayable records with approvals and history
Change triggersNoneNoneDeploys, cloud and config changes
06 · WHAT TRIGGERS A RUN

Tested When It Changes, Not When It's Scheduled

The weekly baseline catches drift. Change triggers catch the rest within hours. Select a trigger type to see this week's runs.

DEPLOYS · THIS WEEKmedian 38 min from deploy
Mon 10:12 orders-api v2.14 to prod-us→ API and tenant tests · 40 steps Held
Tue 16:40 reports-svc v2.4 to prod-us→ Export isolation tests · 20 pairs Finding opened
Thu 09:30 reports-svc v2.5 to prod-us→ Replay of the export finding Fixed · replay failed
07 · REPORTS AND ATTESTATION

The Report Customers and Auditors Ask For, Always Current

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.

pentest-summary-2026-11.pdf Generated today

Penetration testing summary · November 2026

PERIODContinuous, 2026-08-01 to 2026-10-31
SCOPEExternal perimeter, web apps and APIs, cloud, identity
RUNS13 weekly baselines, 41 change-triggered runs
FINDINGS2 Critical and 7 High found, all fixed and verified by replay
OPEN2 Medium, with owners and target dates
Customer-facing wording. Finding details are summarized, not disclosed.
08 · FAQ

Continuous Pentesting FAQ

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.

Book a Demo: See Continuous Pentesting on Your Scope

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.

✓Weekly and change-triggered testing ✓Controls and detections read from your telemetry ✓Every fix retested automatically
Book a Demo