Skip to content

REDAQ+ now cleans Word, Excel, PowerPoint, PDFs and screenshots on your device before they upload to AI chats. See what's new

Nirmal Dahal

How I work

No surprises, for you or your systems.

Every engagement follows the same shape: you know what I'll look at, how, when, and what you'll get at the end.

Process

What working with me looks like.

  1. 01

    You tell me what's at stake

    What you need to protect or prove, and by when.

  2. 02

    I reply with an approach

    Whether I can help and how I'd go about it, usually within two working days.

  3. 03

    We agree scope

    Systems, rules of engagement and timing, in writing, before any work starts.

  4. 04

    The work

    Testing, analysis or advisory, carried out to the scope we agreed.

  5. 05

    Report and debrief

    Detail for engineers, a summary for leadership, and time to walk through both.

Approach

How I work.

  • Attack first, then defend.

    I work on both sides: testing systems the way an attacker would, and building the monitoring that catches the next attempt. Each side keeps the other honest.

  • Evidence over opinion.

    A finding only helps if your team can reproduce it and see why it matters. Every issue I report traces back to the steps and the data behind it.

  • One report, two readers.

    Engineers need detail they can fix from. Leadership needs risk they can decide on. I write for both and brief both in their own terms.

Your data

Handled with care.

  • Scope, rules of engagement and timing are agreed in writing before any work starts.
  • Please don't send credentials, keys or findings through the website's contact form; we agree a channel once we talk.

Website privacy policyResponsible disclosure

Let's scope it together.

Tell me what you need to protect and by when. I'll reply with whether I can help and how I'd approach it.