[ Handling ]

You are handing us the keys.
Here is how we hold them.

This is the part of the engagement that nobody asks about on the first call and everybody thinks about afterwards. It is written down so you do not have to ask.

Each commitment appears in the engagement agreement.

Commitments

Eight, and they are contractual.

Each of these appears in the engagement agreement. If one of them is a problem for your insurer or your own policy, say so before we start — they can be tightened, and one of them being unworkable is not a reason to abandon the engagement.

01 Permissions · what we hold HEALTH CHECK
Repositoryread read
Serverread · no sudo read
DatabaseSELECT only read
Write accessonly for agreed remediation · then revoked none

A health check requires no write access to anything. If remediation is agreed later, write access is granted for that scope and revoked when it ends.

no write access to anything
Clause 01 of 8 · in the engagement agreement tighten it before we start, if you need to
02 Accounts · created for us NOT SHARED
nexusmind-rocreated day 0 · narrowest scope ours only
Engagement closesdisable the same day day 5
Reminderif you forget, we ask auto

We ask for the narrowest access that lets the work happen, on accounts created for us rather than shared ones, and we ask you to disable them the day the engagement closes. If you forget, we will remind you.

we remind you to disable them
Clause 02 of 8 · in the engagement agreement tighten it before we start, if you need to
03 How a secret reaches us DELIVERY
Password manager share1Password · Bitwarden accepted
One-time secret linkexpires on first open accepted
Emailtreated as compromised · rotate it refused

They come through a password manager share or a one-time secret link. Anything sent to us by email is treated as compromised, and we will say so and ask for it to be rotated.

emailed = compromised
Clause 03 of 8 · in the engagement agreement tighten it before we start, if you need to
04 Restore sandbox · backup test ISOLATED
Environmentisolated · no network to production created
Backup restoredone test · timed · logged done
Destroyednoted in the report day 5

Where a restore or a copy is genuinely required — a backup test, for instance — it happens in an isolated environment that is destroyed at the end, and the report says it happened.

destroyed at the end
Clause 04 of 8 · in the engagement agreement tighten it before we start, if you need to
05 Where working copies live AT REST
Our machinesfull-disk encryption on encrypted
Shared drivesDropbox · Drive · etc. never
Third-party AI toolsyour source never leaves our hardware never

Working copies live on full-disk-encrypted machines, not on shared drives and not in a third-party AI tool. Nothing from your system is used to train anything.

nothing trains anything
Clause 05 of 8 · in the engagement agreement tighten it before we start, if you need to
06 Retention SCHEDULE
Working materialsource copies · logs · dumps day 90
On requestany time immediate
The reportkept — you may ask for it again kept

Working material is destroyed ninety days after the engagement closes, or immediately if you ask. The report itself we keep, because you may ask us for it again.

or immediately, if you ask
Clause 06 of 8 · in the engagement agreement tighten it before we start, if you need to
07 Who hears about a finding DISCLOSURE
Youfirst · same day if serious always
Case studies · talkseven anonymised never
Anyone elsewithout your written permission never

A vulnerability we find is yours. It is not a case study, it is not a conference talk, and it is not mentioned to anyone — including in anonymised form — without written permission.

yours, not ours
Clause 07 of 8 · in the engagement agreement tighten it before we start, if you need to
08 Incidents · caused by us IN THE REPORT
Query loaded the serverday 2 · 09:41 · 3 min · reported named
Account locked by our loginnone this engagement none
Anything elsegoes in section 1, not in a footnote always

Read access still occasionally causes something: a query that loads a server, a login that locks an account. If we cause it, it is in the report, named, whether or not you noticed.

named, whether or not you noticed
Clause 08 of 8 · in the engagement agreement tighten it before we start, if you need to

If we find something serious

Disclosure runs to you, immediately, ahead of the report.

If we find something that appears to be under active exploitation, or credentials already published in a breach corpus, you hear about it the same day by telephone. It does not wait for the report, and it does not wait for the invoice.

If the finding touches personal information in a way that may trigger a reporting obligation under Quebec's Law 25, we will say so plainly and in writing — and then point you at a lawyer, because we are not one and the deadline is yours to meet, not ours.

The order things happen in

Same day · by telephoneACTIVE EXPLOITATION · BREACHED CREDENTIALS You hear about it before anything else does. Not the report, not the invoice.
In writing · plainlyLAW 25 · PERSONAL INFORMATION If a reporting obligation may be triggered, we say so — then point you at a lawyer. The deadline is yours to meet, not ours.
Then the reportTO YOU · ONLY TO YOU The finding is yours. Not a case study, not a talk, not mentioned to anyone without written permission.

What we are not

Honest limits.

×

No SOC 2 report

We are a small studio, not a certified assessor. There is no SOC 2 report behind this page and we are not going to imply otherwise — if your procurement process requires one, we are the wrong supplier and we would rather tell you now than at the end of a proposal.

×

Not a penetration test

A health check is a posture review conducted with source access. It is not a penetration test and does not replace one. Where a finding needs a specialist, the report says so and names what to ask for.

Ask about anything here.

If a commitment is a problem for your insurer or your policy, say so before we start. They can be tightened.

Start a conversation hello@nexusmind.dev