Security and trust

How we protect your environment while we work in it

You are giving us access to identity, email and infrastructure. These are the commitments we work to, and what we ask of you in return.

Access

Access to your systems

Named accounts only

Every engineer uses an individual named account. We do not use shared logins or shared administrator passwords, so every change can be traced to a person.

Least privilege

We ask for the roles the work needs and no more. Where you use Privileged Identity Management or delegated administration, we use it, and you can remove our access at any time.

Access ends with the work

When an engagement finishes we ask you to remove our accounts and delegated roles, and we list the access we held so you can check nothing is left behind.

Confidentiality

Your configuration and data stay yours

  • NDAs are welcome, and we are happy to sign yours before work starts
  • We keep your configuration, documents and data confidential and do not reuse them for other customers
  • We work with the minimum data a task needs and avoid copying production data out of your environment
  • Screenshots and examples we publish, such as the guides at docs.techlabops.com, are redacted or built from sample data
  • We tell you promptly if we find a security problem in your environment while we work
  • Our privacy practices are described in the privacy policy

Change control

How changes are made

  1. 1

    Written plan

    Scope, timing, risks and a rollback path are agreed before anything changes in production.

  2. 2

    Agreed windows

    Disruptive changes are scheduled in a window you approve, with a named contact on your side.

  3. 3

    Restore point first

    We confirm there is a backup or restore point before significant changes to identity, mail or infrastructure.

  4. 4

    Documented handover

    You receive documentation of what was built and changed, as a deliverable of the project.

What we ask from you

  • A named contact who can make decisions
  • Delegated, time-limited administrator access to the systems in scope
  • A recent backup or restore point before major changes
  • Notice of change freezes, compliance rules or contractual limits that apply

Certifications and attestations

We do not claim certifications or partner statuses we do not hold. If your procurement needs a specific standard, such as ISO 27001 or SOC 2, tell us at the start and we will say plainly whether we meet it and how we would work within it.

Report a security concern

If you believe you have found a security problem on this website, email info@techlabops.com with the details. We read every report and reply within one business day.

Have a project in mind?

Tell us what you are trying to achieve. We reply within one business day with next steps.