Working session
30 minutes on a screen-share with the engineering team. Pick the question; we'll spend the time on that question.
Tell us which question you want answered first and we'll spend the whole half-hour on that one. Most engineers leave with a sample IOC payload from their own environment and a working integration into one of their existing tools. If you want a slide deck instead, you're on the wrong page; the public marketing site has those.
Standard agenda
The first 30 minutes typically cover:
- Your detection-engineering priorities and stack
- A live walk-through of the actual record format and event payloads
- One specific integration glue (SIEM, SOAR, ITSM, EDR, pick one)
- The threat-model conversation, including what we do not claim
- Sizing for a 30-day pilot on one of your sites
What we will NOT do
The first 30 minutes will not:
- Show you a marketing slide deck
- Quote you a price without scope clarity
- Ask for an org chart, decision criteria matrix, or budget conversation
- Promise things the product does not actually do
- Require a procurement-process commitment to keep talking
Get in touch
Two paths. Either works. The form below is faster on our side; direct email is faster on yours if you prefer.
Engineering team mailbox (monitored by humans, not a chatbot): seceng@cybriq.io
For vulnerability disclosure: security@cybriq.io · PGP key & policy
Request a working session
Form posts to the same contact pipeline as the general site, with a ?topic=seceng tag so engineering-team routing applies.
Pilot terms (when you're ready)
- No fee. The 30-day pilot itself is no charge. Customer (or partner integrator) supplies the External Scan Engine to our spec and handles physical installation.
- One site, one scope. Pick one building or one set of conference rooms. Defining scope is what we'll do together in the working session.
- Three deliverables. (1) Layer 1 inventory of every device in scope. (2) 30-day drift report. (3) Framework-mapped evidence pack for the controls you select (PCI / SOC 2 / HIPAA / NIST / CMMC).
- Customer keeps everything. Inventory, drift report, evidence pack, all yours regardless of whether you go forward.
- Clean abort path. If the pilot turns out to show this isn't the right tool for your environment, we'll say so on the wrap call. The next step from there isn't a procurement conversation; it's whichever conversation makes sense for the gap we actually found.