The Post-Quantum Security Workshop

You convene your leadership team for a day. Addie LaMarr, a former U.S. Air Force cryptographer with 15 years in cybersecurity, runs it.

Request the workshop

Your board will ask where you stand on quantum risk. The answer already exists inside your organization, spread across teams, vendors, and systems built by people who have since moved on. It has never been assembled in one place.

One day assembles it. 15 people, a closed room, and a cryptographer to catch what the room gets wrong.

Nobody has to take a consultant's word for it, including you.

What you leave with

  • —

    A shelf-life ranking of your data

    Class by class, against the dates that matter. Most rooms find the exposed set is a different set from the one they expected.

  • —

    An ownership map

    The cryptography-dependent systems your team can name, and the ones nobody in the room can put a name to.

  • —

    A visibility score your team can defend

    Across embedded devices, vendor platforms, machine identities and long-lived archives.

  • —

    Five questions for your vendors

    Written to require a date and a version.

  • —

    A board memo carrying the day's findings

    In your organization's own language.

  • —

    A starting sequence

    Which systems move first, and why.

And the list of everything the room could not answer about itself, each question with a plain sentence on the work that closes it.

Getting that list wrong is what turns a multi-year migration into a wasted one, and 15 executives producing it together is the most accurate scoping you will get before committing budget.

The full day adds four

  • —

    Regulatory Ground Truth

    Which deadlines actually bind.

  • —

    Where Cryptography Hides

    Embedded devices, vendor platforms, machine identities, long-lived archives.

  • —

    The Vendor Interrogation Clinic

    Five questions your team sends on Monday, and how to tell a real answer from an evasive one.

  • —

    The Disclosure Tabletop

    Legal, comms, security and the CEO seat, played by the people who hold them.

Before you walk in

  • —

    A planning call

    Where the four modules are chosen against your sector and against whatever is actually blocking you.

  • —

    A sector pack

    Built from primary sources: which regulations bind you, which deadlines are real, and which are drafts being reported as rules. The firm reads the standards bodies and the research literature weekly and folds what changes into the methodology the same week, so what you are handed is current to the week you book.

  • —

    Your team's pre-work, read in advance

    So the first session opens on your systems instead of on introductions.

You arrive at a room where the research is already done.

After the day

  • —

    Your artifacts, written up and returned within the week

    So what went on the wall becomes a document your team can circulate.

  • —

    A debrief with you

    On what the room revealed, what it avoided, and where the two lists should go next.

  • —

    A board read-out

    Arranged separately, for organizations that want the findings presented to the board rather than forwarded to it.

Fee

FULL DAY

$45,000

  • —Everything your leadership team can account for
  • —Shelf-life ranking of each class of data the room can name
  • —Ownership map of the systems the room can name, and the ones nobody can
  • —Visibility score across devices, vendors, machine identities and archives
  • —Vendor question set, five questions ready to send Monday
  • —Four sector modules, chosen with you
  • —The disclosure tabletop, run in full
  • —Board memo carrying the day's findings
  • —Starting sequence: which systems move first, and why
  • —The unanswered list, each question with the work that closes it

HALF DAY

$24,500

  • —Three data domains you choose beforehand
  • —Shelf-life ranking within the nominated domains
  • —Ownership map within the nominated domains
  • —Board memo carrying the day's findings
  • —Starting sequence within scope
  • —The unanswered list, each question the room could not answer

Most organizations take the full day. The systems nobody owns are usually outside a scope you chose yourself.

Nothing said in the room leaves it.

Request the workshop

Who this is not for

Teams looking for an engineering implementation plan. Organizations wanting a vendor recommendation, which the firm structurally cannot provide. Anyone who would rather be handed a finding than produce one. Anyone who needs the day to conclude that they are already fine.

Tell us about your organization and what is driving the timing. Response within 5 business days.

Request the workshop