Contact

WHAT HAPPENS NEXT

01 A person reads it. Not a queue, not an autoresponder sequence.

02 We reply within one working day, usually with questions about topology and operating model.

03 If a review makes sense, you get a written scope with what is covered, what is not, and how testing would be bounded.

04 If it does not, we say so. An assessment of the wrong layer helps nobody.

Request a security review.

The more you can say about the system, the more useful the first reply will be. Topology, vendors, how remote access works today — all of it helps.

Please do not send sensitive material through this form. No network diagrams, credentials, vulnerability details or incident specifics. Describe the shape of the problem; we will arrange a secure channel before you send anything that matters.

Name

Work email

Organisation

System or project type

What are you working with?

Useful: rough capacity, who supplied the BMS and PCS, whether there is remote vendor access, and what prompted you to look at this now.

Spam check by Cloudflare Turnstile. It does not track you across sites and usually resolves without you doing anything.

We use what you send only to answer your enquiry. It is stored on Cloudflare infrastructure in the EU and is not sold, shared or added to a marketing list. See our privacy notice.

This form needs JavaScript to submit securely. If you would rather not enable it, please try again from a browser that allows it — we do not have an alternative channel published yet.

Common enquiries

"We are commissioning a site"

Architecture review before handover, while findings still cost a drawing revision rather than an outage window.

"A customer sent us a security questionnaire"

Vendors needing their product assessed properly before a buyer's team does it for them.

"We inherited a fleet"

Sites built by different integrators, with remote access nobody has fully mapped.

"We are buying the asset"

Technical due diligence on cyber and operational exposure before the transaction closes.