Contact us
Both principals read everything that arrives, so this address reaches a real inbox within a day rather than a shared folder nobody owns. There is no ticket number and no form that disappears into a CRM.
New enquiries, scoping a piece of work, and anything commercial or contractual, including questions about how we handle your tenant data. Technical depth, existing engagements and Warden itself — a check you think is wrong, a dataset you want added, or a finding you want to argue with — all arrive at the same place.
Write to usAlan and Ross. Both principals work on every engagement, so the person who answers your email is the person who will read your tenant. We publish a shared address rather than our own because a named address on a public page is a better target for anyone pretending to be us — see the note below.
Who we areWhere to start
These are the four things people actually write to us about, with what makes each one fast to answer.
| If you want | Put in the email | Realistic reply |
|---|---|---|
| An assessment quoted | How many tenants, roughly how many users and groups, whether PIM is in use, and the one thing you are most worried about. A screenshot of your Conditional Access list is more use than a paragraph. | Same day, or next working day if it arrives late. |
| A lab run before deciding | Say it is non-production and we will not scope it as production. Give us the tenant domain when you have set up the app registration. | Access set up, run within a few days. |
| To add a tenant or re-run | Existing clients: reply to the engagement thread. New tenant: client ID and Tenant ID, or use the access page. | Within one working day. |
| To report a security concern | Say which system, and whether active exploitation is suspected. If you think an email from us is spoofed, include the full headers — do not rewrite them. | Same day, urgently. |
Please don't
We are an identity company. Sloppy credential handling in our own inbox would be a special kind of hypocritical.
We will never ask for a client secret, password or private key by email
link, web form, phone or chat message. If that happens, do not click
and do not reply. Forward the full message with headers to
info@subtlecyber.com
by a route you already trust, and revoke the credential you were asked
about. Worth knowing when you read a message's authentication header:
this domain publishes an SPF record and a DMARC policy of
p=reject, so a message that claims to come from
subtlecyber.com but fails DMARC alignment was not sent by
us, whatever its From header says. Ask us for the exact records if you
want to check them yourself.
