No surprises, start to finish.

Every engagement follows the same shape, whether it is two weeks of offensive testing or a year of vCISO work. You always know what is happening, what we found, and what comes next.

  1. 1

    Discovery call

    30 minutes, free

    You describe what is going on. Maybe a customer is asking for a pentest, an audit is on the calendar, or you have an uneasy feeling about what is exposed. We ask questions about your environment and your constraints.

    You leave with a clear opinion on what to do first, even if the answer is that you do not need us yet.

  2. 2

    Scope and rules of engagement

    Written and signed before work starts

    A written proposal that states the cost and exactly what is included and what is not. For testing work, the rules of engagement are in writing too, covering what is in scope, what is off limits, testing windows, and who to call if something looks wrong.

    We only test what you own or have the right to authorize. No exceptions.

  3. 3

    The work

    Status updates throughout

    Regular, short updates so nothing lands as a surprise at the end. Anything critical is reported as soon as we confirm it is real and affects you, with enough detail to act on immediately.

    Every finding is confirmed by a person before it is written up. False positives stay out of your report.

  4. 4

    Report and readout

    Two audiences, one document

    A one-page executive summary for leadership, and detailed findings for the people doing the fixing, each with its evidence, business impact, and specific steps. Then a call to walk through it, answer questions, and agree on priorities.

  5. 5

    Fix and verify

    Retest included

    We can help with the fixes, scoped to what you need, then retest your critical and high findings to confirm they are actually closed. You end with evidence that the problems are gone, which is what auditors, insurers, and customers want to see.

What we will not do.

  • Sell you fear.

    No breach statistics designed to scare you into a bigger package. If a risk is small, we say it is small.

  • Hand you a scanner dump.

    Automated output is only the starting point. Nothing reaches your report until a person has verified it.

  • Test without authorization.

    Every engagement has written scope and permission. Third-party systems need their owner's sign-off too.

  • Lock you in.

    Documentation, configurations, and findings belong to you. If you move on, everything you need goes with you.

Things people ask on the first call

Will testing break anything in production?

Testing is planned around that risk. Before anything starts we agree in writing on what is in scope, what is off limits, and when testing happens. Anything that could disrupt a service is only used with your explicit sign-off, and you have a direct line to pause testing at any time.

What do I get at the end?

A written report with a one-page executive summary and detailed findings. Each finding includes the evidence, why it matters to your business, and specific steps to fix it. We walk through it with your team on a call and retest fixed critical and high findings to confirm they are closed.

How much does it cost?

It depends on scope, so a real number comes after a short call. You get a written proposal with the cost and exactly what is included before any work begins.

Do you need admin access to our systems?

For external testing and attack surface work, no. We see what an outsider sees. Internal assessments, cloud reviews, and vCISO work need some access, and we will tell you exactly what and why, scoped to the minimum.

We do not have a security person. Is that a problem?

No. Many of our clients do not. We can work with your IT lead or MSP, or act as your security function through vCISO and ongoing advisory work.

We already have a security team. Where do you fit?

Usually on a specific piece of the work, such as an offensive test, an architecture review, specialist support during an incident, or a second opinion on a program. We work inside your process and tooling, and everything we produce stays with your team.

Do you only work in Colorado?

No. Most work is done remotely for clients anywhere. DruidSec is based on the Colorado Front Range and happy to be on site for local clients when it helps.

Do you resell security products?

For managed clients we deploy and run a proven stack and bundle the licensing so there is one bill. Recommendations are based on fit. If something you already own does the job, we will use it.

Do you work with AI?

Yes. We use it to help process large volumes of technical data, identify patterns, and organize material for investigation. For sensitive workloads, inference runs locally on hardware we control.

We also help clients assess where AI can be useful. We look at what data it receives, what it can access, how its output is checked, and what happens when it gets something wrong. Our practitioners remain responsible for the findings and recommendations we deliver.

What if we are in the middle of an incident?

Use the contact form, tick the active incident box, and leave a phone number. We will call you. We work alongside your team, your insurer, and any incident response firm they assign.

Start with step one.

Thirty minutes, free, and you will leave with a clear opinion on what to do first.