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 timeMedium moves in ENG-27: 12 moves. Every move is logged against this rule.
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.
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.
Tests are point in time
An engagement shows one quarter. By the next one, half the environment has changed.
Retests eat the calendar
Every fix needs a retest, and every retest pulls an operator off new work.
Blue team results are manual
Matching each hop to what the SOC saw happens in a spreadsheet, days later.
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.
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.
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.
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.
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.
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.
External perimeter
T1190T1133T1595Internet-facing services, VPNs and exposed admin panels.
Learn more →02Applications and APIs
T1190T1213T1552Authenticated behavior, business logic and tenant isolation.
Learn more →03Identity
T1078T1098T1110Accounts, roles, tokens and the permissions between them.
Learn more →04Cloud
T1580T1552.005T1078.004Metadata, IAM, storage and cross-account trust.
Learn more →05Internal network
T1021T1210T1003Lateral movement, credential access and segmentation.
Learn more →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.