Authorized offensive research. Engineered remediation.

Break the path. Fix the failure.

We test software, infrastructure, and AI systems that we own or have written permission to assess. We reproduce exploitable paths under controlled conditions, repair the root cause, and retest the original path and its nearest variants.

The exploit-to-patch loop

A finding closes when evidence shows the attack path is gone.

Our sequence follows the core logic of a technical security assessment: plan the test, conduct it, analyze the evidence, mitigate the weakness, and validate the mitigation. A scanner can start the search; it cannot finish the proof.

01 / DEFINE

Set the rules of engagement

Name the assets, identities, data, techniques, timing, observers, stop conditions, and evidence route before testing begins.

AI assistanceOrganize the test plan and identify unclear assumptions. The accountable operator confirms permission and scope.

02 / PROVE

Reproduce the attack path

Trace the violated trust boundary and build the smallest controlled proof that establishes impact without expanding the agreed scope.

AI assistanceAnalyze the suspected failure and develop minimal reproduction cases, prioritizing isolated targets and synthetic data.

03 / REPAIR

Remove the root cause

Change the broken invariant in code, configuration, identity, or architecture. Where possible, remove the whole defect class instead of one symptom.

AI assistancePropose corrective changes and regression tests. An accountable engineer reviews the change and its evidence before deployment.

04 / RETEST

Challenge the fix

Replay the exploit, test realistic variants, and save regression evidence. The result states what was tested, what changed, and what remains outside scope.

AI assistanceGenerate relevant variants and compare results. Closure depends on observed behavior in the tested version and environment.

Research and engineering

Research that ends in a stronger system.

The deliverable is a defensible change: a reproducible trigger, an impact boundary, a root-cause repair, and evidence from the retest.

Vulnerability and zero-day research

Source-assisted and black-box investigation of new failure modes, exploit primitives, trust-boundary mistakes, and assumptions that routine checks do not exercise.

Exploit engineering and impact validation

Bounded proofs with explicit prerequisites, observable effects, blast-radius controls, and evidence that separates a theoretical weakness from a usable attack path.

Remediation and exploit regression

Defensive code, identity and configuration changes, reproduction harnesses, regression tests, and a retest of both the original trigger and practical variants.

AI and agent security testing

Prompt injection, tool and API abuse, excessive agency, memory poisoning, data exfiltration, model and dependency supply-chain risk, and failures in human approval boundaries.

AI as an amplifier

More hypotheses. Accountable decisions.

We use AI to inspect more code, correlate signals, generate test cases, and challenge assumptions. It does not authorize access, expand scope, or declare a system safe. People remain accountable for those decisions and for every action that reaches a real system.

AUTHORIZED_RESEARCH / CONTROLLED_ENVIRONMENT
[scope]    target and stop conditions recorded
[prove]    trust boundary violation reproduced
[repair]   authorization invariant enforced
[retest]   original and adjacent paths replayed
[result]   exploit blocked; evidence preserved

Requirements for specialist-model workflows

The following controls must be verified before a specialist-model workflow is put into operation. They describe our deployment requirements, not an attestation that a particular provider setup is already active.

Review before execution.Check each sensitive tool call against the approved scope. Reject unauthorized actions and refer ambiguous or high-impact changes to a human. If scope review is unavailable, the action must not run.
Enforce the boundary.Restrict access to named operators and approved systems. Use only the permissions needed for the task, with filesystem and network limits enforced independently of the model.
Keep reviewable evidence.Record the scope, operator decisions, relevant actions, and test results. Minimize sensitive data and confirm the applicable retention terms before sending research material to a provider.

Read our proposed Daybreak Red use and access boundaries →

Research boundaries

Capability needs discipline.

Written authorization first.Ownership, assets, allowed techniques, data handling, timing, observers, and stop conditions are agreed before testing.
Minimize real-world impact.Use isolated targets and synthetic data where possible. Collect only the evidence required to prove and repair the flaw.
Disclose for remediation.Coordinate with the owner, protect sensitive details, and give the patch a fair path before public technical discussion.
Evidence over theatre.Separate observed behavior from inference. Preserve the trigger, environment, prerequisites, and limits of every conclusion.
Repair belongs in scope.A report is not the end state. We connect the exploit to code, configuration, identity, monitoring, and a repeatable verification step.
No silent expansion.Finding a new path does not expand permission. Testing pauses at the boundary until the owner explicitly changes the scope.

Proposed Daybreak Red use

From controlled proof to verified repair.

Our proposed use of OpenAI Daybreak Red is to reproduce vulnerabilities, validate their impact, and challenge fixes in Aerolambda-owned research environments. Specialist capabilities would support the Prove and Retest stages of our four-step method.

A bounded first workflow

Investigate an authorization flaw in an isolated Aerolambda test deployment. Establish a minimal reproducible result, repair the access-control failure, and replay the original case and relevant variants. Preserve the before-and-after evidence and state the limits of the test.

Client permission and provider approval

A client's written authorization does not by itself permit the use of a restricted model. Any use for client engagements would require explicit confirmation from OpenAI. The proposed initial scope is internal research; customer access, externally offered services, and downstream product use are outside that scope.

Access is conditional. This proposal does not claim Daybreak approval, certification, or endorsement. Use depends on approval for the relevant users, workspace or API project, model, and product surface. GPT-6 Cyber requires additional model approval.

Published access requirements and sources

OpenAI requires enforced single sign-on and multi-factor authentication for the API organization holding Daybreak Red access. Approved project controls can provide separation without a dedicated organization. GPT-6 Cyber API access requires IP allowlisting. Zero Data Retention requires separate approval and, where applicable, Private Safety Processing.

These are provider requirements to satisfy before use, not claims about our current configuration. Requirements reviewed on ; the provider's current documentation and written approval govern access.

Public reference points

Methods grounded in open security guidance.

These sources inform our operating model. They are reference points, not certifications or endorsements.

Start with authorization

Name the system, the decision you need to make, and the boundary we must never cross.

We begin with authorization, scope, stop conditions, evidence handling, and the route from a confirmed exploit to a verified repair.

[email protected]