StealthByte Labs · Initiate Engagement

// engagement_request.form

all fields encrypted

Submissions are encrypted in transit (TLS 1.3) and delivered to the lab's operations inbox at ops@stealthbytelabs.com. Use this form for standard inquiries. For active incidents, use the encrypted channels in the side panel — Signal preferred. For responsible disclosure of vulnerabilities affecting our infrastructure, use PGP.

Name *

Organization *

Email *

Role — optional

Engagement interest — select all that apply

red team ai red team adversary emulation quantum pentest research / advisory other

Urgency *

// standard Planning ahead Q3/Q4 budget cycle · response within 24h // priority Need to engage soon Within 30 days · response within 12h // active incident Active breach / IR Use Signal channel · 1h response

Industry — optional

Org size — optional

Briefing *

// transit-encrypted · TLS 1.3 PGP available · see panel

transmission acknowledged

Briefing received.

Your submission was delivered to ops@stealthbytelabs.com. An operator will respond to the email address you provided, within the SLA you selected. For active incidents, please also use the Signal channel — it's monitored 24/7.

// secure_channels verified · 2026-01

// preferred channelsFor sensitive matters

For active incidents, sensitive briefings, or anything you wouldn't email — use one of these.

Signal configure in contact.html
Email (PGP) ops@stealthbytelabs.com
Matrix @ops:stealthbytelabs.com

// response_sla measured · 90-day avg

// response timesWhat to expect back

Standard

< 24h

Priority

< 12h

Incident

< 1h

PGP / Signal

< 4h

// what_happens_next 3 steps · ~5 business days

// processFrom briefing to engagement

01 Acknowledgment. A senior operator reads your briefing within the SLA window and replies to clarify scope.
02 Mutual NDA. Before discussing sensitive details we exchange a one-page mutual NDA. Standard counsel-friendly text.
03 Scoping call. 60–90 minutes with the lead operator who'd run the engagement. Specific. No sales people.
04 Proposal. Within 72 hours of the call, a detailed proposal with timeline, RoE, deliverables, and pricing.

// pgp_public_key rsa-4096 · created 2026-01

// pgp identityFor coordinated disclosure

Use this key for vulnerability disclosure or any communication too sensitive for the form. Click to copy the fingerprint.

7F3A 8B2D 1184 4C92 · A6D5 E081 B73F 22CF

Full key: /.well-known/security.asc

Initiateengagement.

Briefing received.

// preferred channelsFor sensitive matters

// response timesWhat to expect back

// processFrom briefing to engagement

// pgp identityFor coordinated disclosure

Initiate
engagement.