Purple TeamCybersecurity

Home/Contact

Start the conversation

Start with the rough version.

Send the deadline, systems involved, evidence you already have, who is asking, and what answer you need to give. Purple Team will help shape the first owner map, sprint brief, or risk memo.

Start with the problem Explore focused sprints

Guided intake

Start with the problem.

Answer a few high-level questions and the site will route you toward the most likely Purple Team next step. Nothing is stored by this page; it prepares a summary you can review, copy, or send by email.

Keep this high level. Do not include credentials, secrets, regulated data, exploit details, or sensitive incident details. If this is an active incident, send only enough context to schedule a safer conversation.

Pick the pressure that triggered the conversation.
Example: what to fix first, whether to launch, how to answer a customer, or who owns the work.
A board date, audit window, launch target, customer deadline, or "not sure" is enough.
Keep names and details general until the right channel is established.
This helps shape the first useful work product.
Email directly instead

Contact options

Prefer a direct email?

The guided intake is the easiest path. These direct email links remain available if you already know what kind of conversation you need.

Direct email: purpleteamcyber@protonmail.com

Focused sprint

Start a security sprint

For scanner findings, customer evidence requests, audit deadlines, incident-readiness gaps, or launch reviews that need a short action path.

Start a security sprint
AI risk review

Ask about AI/LLM security

For teams launching or operating AI-enabled workflows that need prompt-injection, tool-use, data exposure, or governance review.

Ask about AI/LLM security
Founder-led advisory

Talk with Andrew

For leaders who need a second set of senior eyes on a launch, board packet, audit response, tabletop, or backlog tradeoff.

Talk with Andrew

What happens next

  1. 1

    Andrew reviews the business context and pressure behind the request.

  2. 2

    You align on the deadline, systems, evidence, owners, and audience for the answer.

  3. 3

    Purple Team recommends a sprint, advisory path, or specialist support model.

  4. 4

    The work produces artifacts such as a risk memo, owner map, matrix, or action backlog.

Do not send sensitive credentials, secrets, regulated data, or incident details by email. Start with the business context and Purple Team will establish the right channel.