Design Partner Program
OFFENSIVE SECURITY

Offensive Security: Scale Your Red Team Without Losing Control

Direct Nectar to walk attack paths under rules of engagement you set. It proposes the next move, you approve anything risky, and every hop is scored against your blue team's SIEM, EDR and WAF telemetry. Your operators spend their time on creative chains, not retests, because every finding can be replayed on demand.

ENG-27 · operator consoleobjective: reach payments-db auto-approving recommended
Internet→?→
NECTAR PROPOSES · MOVE 1 OF 3from Internet
T1190Medium★ recommendedExploit CVE-2022-22965 on checkout-apiPublic endpoint, reproduced in an earlier run.
T1110.003HighPassword spray the partner portalExcluded by ROE: account lockout risk.
T1566HighPhish a staff mailboxOut of scope for ENG-27.
BLUE TEAM TELEMETRYper hopApprove a move to see what your SIEM, EDR and WAF recorded for it.
01 · THE PROBLEM

Your Environment Changes Weekly. Your Red Team Tests Quarterly.

Skilled operators are scarce, and too much of their time goes to work that does not need them: re-running last quarter's chain, retesting fixes, and rewriting the same report.

CADENCE

Tests are point in time

An engagement shows one quarter. By the next one, half the environment has changed.

CAPACITY

Retests eat the calendar

Every fix needs a retest, and every retest pulls an operator off new work.

DEBRIEF

Blue team results are manual

Matching each hop to what the SOC saw happens in a spreadsheet, days later.

02 · OPERATORS AND NECTAR

You Direct the Engagement. Nectar Covers the Breadth.

Nectar does the repeatable work at machine pace. Operators keep the judgment: objectives, novel chains, risky approvals and the final word on every finding.

NECTAR HANDLES
◆Walks known and generated attack paths at machine pace
◆Retests every finding after a fix or change
◆Reads SIEM, EDR and WAF telemetry for every hop
◆Proposes next moves with risk, expected value and evidence
◆Writes each hop up in the shared finding format
YOUR OPERATORS HANDLE
●Set objectives and write the rules of engagement
●Approve high-risk moves and stop runs at any time
●Build novel chains and test business logic
●Decide what is a finding and how severe it is
●Brief the blue team and own the narrative
03 · RULES OF ENGAGEMENT

Rules of Engagement, Enforced on Every Move

The rules you write in a scoping call become the rules Nectar runs under. Each move is checked against scope, exclusions and the approval tier for its risk. Select a tier to see what it allows.

ROE · ENG-27 · MEDIUMApproved · a.reyes
scope:
  include: [checkout-platform/prod-us]
  exclude: [real customer accounts, payroll-*]
tier: medium
  allow: within scope
  window: Tue–Thu 02:00–06:00 UTC
  rate_limit: 5 req/s per host
  approval: plan-level (a.reyes)
kill_switch: any operator, any time
Medium moves in ENG-27: 12 moves. Every move is logged against this rule.
04 · RED MEETS BLUE

Every Hop Scored Against Blue Team Telemetry

No more debrief spreadsheets. Hayrok reads your SIEM, EDR and WAF for each hop and records what was prevented, logged, alerted and triaged. Switch views to see the same run from each side.

ENG-27 · Internet → payments-db · 4 hops
HOPRESULTAPPROVALEVIDENCETIME
T1190Internet → checkout-apiSucceededreproducedPlan · medium tierROE ENG-27Savedrequest, response, telemetry02:14UTC
T1552.001checkout-api → service tokenSucceededreproducedAuto · low tierROE ENG-27Savedrequest, response, telemetry02:19UTC
T1078token → payments-dbSucceededreproducedPlan · medium tierROE ENG-27Savedrequest, response, telemetry02:31UTC
T1213Read payment recordsSucceededreproducedPlan · medium tierROE ENG-27Savedrequest, response, telemetry02:34UTC

Four hops, all reproduced, all inside the rules of engagement. Each one is a replayable finding.

05 · EVIDENCE AND REPLAY

Write the Report Once. Retest Forever.

Every hop is saved with its request, response, approval and telemetry. Operator findings and Nectar findings share one format, so the report builds itself and any finding can be replayed after a fix, a change, or on schedule.

01One finding formatOperator and Nectar findings share the same fields, so reports merge cleanly.
02Replay on demandRetest any finding after a fix, a change, or on a schedule, without an operator.
03Export when you need itGenerate the engagement report from the saved findings and approvals.
ENG-27 · Finding 3 of 4 CriticalReproduced

svc-checkout token read from the container environment

FOUND BYNectar · approved by operator j.kim TECHNIQUET1552.001 · Credentials In Files BLUE TEAMEDR did not record the read. No alert.
REPLAY HISTORY07-08 · original runReproduced07-22 · after secrets refactorReproduced08-05 · after token moved to vaultReplay failed · fixed
06 · ENGAGEMENT TYPES

Four Ways to Run It, One Set of Rules

From an always-on baseline to a focused emulation of one threat group. Each type is a plan template your team adjusts and approves. Select one to see what it sets up.

PLAN TEMPLATE · CONTINUOUS VALIDATION
OBJECTIVEKeep every known route to crown jewels closed
CADENCEWeekly, plus on change
SCOPEProduction, read-only and low-risk moves
APPROVALSPlan-level, renewed each quarter
OUTPUTDrift alerts and replay results per route
07 · ATTACK SURFACES

One Engagement Across Every Surface

Real attacks cross boundaries: a web bug leads to a token, the token leads to the cloud. Nectar follows the route wherever the rules of engagement allow.

08 · FAQ

Offensive Security FAQ: What Red Teams Ask

No. It handles breadth and retests. Operators set objectives, approve risky moves, build novel chains and decide what is a finding.

Book a Demo: Run an Engagement With Nectar

We will walk through writing rules of engagement, directing and approving Nectar's moves, reading blue team telemetry per hop, and replaying findings as retests.

✓Rules of engagement enforced on every move ✓Blue team telemetry scored per hop ✓Findings replayed as retests, on demand
Book a Demo