Nick Sullivan: Post-Quantum Cryptography and Security

At a glance

Nick Sullivan is most useful for post-quantum cryptography migration advice, not sponsored posts.

Best for

Cybersecurity companies needing technical advisory for enterprise PQC migration planning.

Not for

Paid audience placement or sponsored posts with guaranteed impressions and metrics.

Key takeaways

NIST's first three post-quantum standards are finalized and explained.
Google and Cloudflare moved post-quantum cryptography into production.
Privacy technology is weakening a common security shortcut.

Check first: Confirm current availability, advisory scope, deliverables, fees, and prior advisory outcomes.

Main ideas: Post-quantum cryptography has shifted from standards work to migration planning · Privacy technology is weakening a common security shortcut · Attestation can matter even without confidential encryption
Audience: 5455 LinkedIn followers
Read first: NIST’s first three post-quantum standards, explained
Ways to work together: Post-quantum cryptography consultation · Technical advisory and brainstorming calls · Consulting projects and board positions

Sources for this section

What they are known for

Nick Sullivan writes about cybersecurity, especially the shift to post-quantum cryptography (PQC), and shares observations on security and privacy problems raised by founders and engineers.

The posts explain both the standards and their practical adoption: they name NIST’s first three finalized PQC standards and describe Google and Cloudflare deployments as examples of the transition reaching real systems.
Readers looking for a view of how cryptography standards connect to business and infrastructure decisions can start with those posts.
Ask for targeted identity research before treating this as a complete account of why people search the name.

The posts connect technical changes to operational questions without reducing PQC to a list of algorithms.

Sullivan distinguishes encryption from digital signatures when explaining NIST’s standards, then uses browser, internal-communications, and origin-server deployments to make adoption tangible.
In advisory conversations, they also discuss software attestation, the limits of IP reputation as privacy tools spread, and the cost and complexity of production security systems.
Together, these examples show a practical lens on security: what a technology does, where it is being deployed, and what problems organizations still need to solve.
Their posts include statements about consulting and work with Cloudflare; ask for credentials and broader career history if those matter to your decision.

Sources for this section

Ideas and priorities

Sullivan's posts frame post-quantum cryptography as an operational migration problem now that NIST standards are final and major platforms are deploying PQC.

They also examine practical security and privacy limits: privacy tools weakening IP reputation, attestation beyond confidential encryption, and costly production security tooling. Sullivan offers advisory and consulting work to help organizations apply this experience.

Post-quantum cryptography has shifted from standards work to migration planning

Sullivan argues that NIST's first three finalized post-quantum standards give organizations concrete algorithms to adopt: FIPS 203 ML-KEM for general encryption, FIPS 204 ML-DSA for digital signatures, and FIPS 205 SLH-DSA as a backup if ML-DSA proves vulnerable.

Since major platforms have already put PQC into production, businesses should move internal and external services to support it, following NIST guidance rather than treating quantum risk as a distant research topic.

Sullivan notes that Google deployed PQC for internal communications in November 2022 and rolled it into Chrome by August 2023.

Cloudflare introduced Chrome-compatible PQC and uses it for internal and origin-server communications.
They also summarize NIST's selection path: launched in 2015, assessed 82 algorithms from 25 countries, narrowed the field to 15, and released draft standards in 2023.

One post tracks proposed NIST standards through rollout; another announces the first three finalized standards. Together, they show Sullivan sees PQC as past the drafting stage and ready for operational migration.

Read original · Original 2

Privacy technology is weakening a common security shortcut

Sullivan argues that privacy tools such as multi-hop proxies, including iCloud Private Relay, are making IP reputation less useful for identifying threat actors.

Security services can no longer assume an address reliably indicates a bad actor's origin, so they need new detection methods.

Drawing on advisory conversations, Sullivan writes that IP reputation 'can no longer be used as a crutch' and teams need new techniques as privacy proxies spread.

Read original

Attestation can matter even without confidential encryption

Sullivan argues that confidential computing's value extends beyond running encrypted workloads on untrusted computers.

Organizations also benefit from verifying that specific software is running, even without cryptographic guarantees of confidentiality.

Sullivan identifies confidential computing as a growing area and distinguishes two needs: encrypted workloads and software attestation. They say attestation is useful even without cryptographic guarantees of confidentiality.

Read original

Production security tooling is getting too complex and costly

Sullivan argues that security scanning and threat-mitigation systems for production workloads are becoming more complex and expensive, in both cost and staffing.

They attribute this to systems often being bolted onto existing infrastructure and major cloud providers under-investing in making them affordable and easy to use.

Sullivan identifies this as one of three themes from conversations with founders and engineers, alongside confidential computing and the IP-reputation problem.

Read original

Advisory work is Sullivan's route for applying hard-won PQC and security experience

Sullivan presents advisory and consulting as practical ways to help founders, engineers, and organizations navigate security, privacy, and post-quantum migration.

They offer brainstorming, company-building advice, consulting projects, board positions, and PQC migration consultations—not just commentary.

Sullivan says launching an Intro profile led to four booked calls.

They offer to discuss security and privacy problems, their approach to helping founders build companies, advisory impact, consulting pitches, and board positions.
In the PQC post, they cite half a decade of involvement and work with Cloudflare on its transition, then invite organizations to connect for consultations.

Read original · Original 2

Sources for this section

Start with their work

NIST’s first three post-quantum standards, explained

Answers the basic newcomer question: what did NIST finalize, and which algorithm is meant for each job?

Start here for the vocabulary and standard names used elsewhere in post-quantum cryptography.

Sullivan marks the arrival of NIST’s first three finalized post-quantum standards: FIPS 203, ML-KEM, for general encryption; FIPS 204, ML-DSA, for digital signatures; and FIPS 205, SLH-DSA, as a backup if ML-DSA proves vulnerable. The post traces the selection process: NIST began in 2015, assessed 82 algorithms from 25 countries, narrowed the field to 15 with help from global cryptographers, released draft standards in 2023, and now encourages cybersecurity experts to incorporate the algorithms.

For brands planning a campaign

For a cybersecurity company assessing Sullivan for a PQC advisory engagement, this shows they can translate standardization outcomes into concrete migration topics. It supports a technical advisory angle focused on algorithm selection, signing versus encryption decisions, and phased adoption of NIST standards.

What founders and engineers are asking about security and privacy

Shows what Sullivan hears when companies and engineers bring them into early conversations.

Useful for newcomers who want to see how they frame live security, privacy, and advisory problems rather than just standards.

Sullivan says they launched an Intro profile and booked four calls, then shares three themes from those conversations.

First, confidential computing is growing, but attesting that specific software is running is useful even without cryptographic confidentiality guarantees.
Second, privacy tools such as multi-hop proxies like iCloud Private Relay are weakening IP-reputation-based security, creating a need for new ways to identify threat actors.
Third, security scanning and threat-mitigation systems for production workloads are becoming complex and expensive in both cost and staffing.
They are often bolted onto existing systems, and major cloud providers have under-invested in making them cheap and easy to use.
Sullivan also offers to discuss their approach to helping founders build companies, their advisory work, and pitches for consulting projects or board positions.

For brands planning a campaign

This post shows the advisory questions Sullivan is already engaging with: confidential computing, privacy-driven changes to threat detection, and the operational cost of security tooling. For a PQC advisory pitch, it positions migration as part of a wider security and privacy strategy, not just an algorithm swap.

Why Google and Cloudflare moved post-quantum cryptography into production

Explains why post-quantum cryptography moved beyond standards exercises and started appearing in real web traffic.

It gives concrete deployment examples and a migration frame for readers who need to understand adoption, not just algorithm names.

Sullivan describes the post-quantum transition as entering an early adopter phase.

The post points to Google deploying post-quantum cryptography for internal communications in November 2022 and rolling it out in Chrome by August 2023.
It also says Cloudflare introduced PQ cryptography compatible with Chrome and uses it for internal communications and communication to origin servers.
Sullivan argues that by the end of that year, a substantial percentage of web traffic could be safeguarded by post-quantum cryptography using proposed NIST standards.
The post recommends that businesses move both internal and external-facing services to support post-quantum cryptography and links NIST guidance for the transition.
Sullivan says they have been personally involved in post-quantum cryptography for half a decade, describes their work with Cloudflare on its transition, and offers consultations to help other organizations.

For brands planning a campaign

For a PQC migration advisory engagement, this is the most deployment-focused original.

It offers examples of browser, CDN, internal, and origin-server adoption to anchor a phased migration conversation.
It also shows Sullivan presenting consultation as a way to help organizations move from standards awareness to operational change.

Sources for this section

Topics and approach

Post-quantum cryptography migration

Nick Sullivan explains NIST's first three post-quantum cryptography standards: FIPS 203 ML-KEM for general encryption, FIPS 204 ML-DSA for digital signatures, and FIPS 205 SLH-DSA as a backup.

They note that Google deployed PQC internally in November 2022 and rolled it into Chrome by August 2023, and that Cloudflare introduced compatible PQC and uses it for internal and origin-server communications. They describe this as the early adopter phase and say businesses should transition internal and external services, pointing to NIST guidance.

Tracks adoption through a timeline of NIST, Google, Chrome, and Cloudflare developments, links to primary announcements and guidance, and frames the shift as an operational imperative.

For brands planning a campaign

A cybersecurity company strengthening its PQC offerings can assess Nick Sullivan as a technical communicator or adviser who translates standards and deployments into migration guidance. Focus an engagement on practical transition planning, standards selection, and adoption sequencing rather than general quantum-threat education.

Examples: Source 1 · Source 2

Security and privacy engineering challenges

From conversations with founders and engineers, Nick Sullivan identifies three areas: confidential computing, where attestation can matter even without cryptographic guarantees; privacy technology such as multi-hop proxies, which reduce the usefulness of IP reputation for identifying threat actors; and security scanning and production threat detection, which are becoming complex and expensive, with major cloud providers under-investing in making those tools cheap and easy to use.

Distills conversations into numbered takeaways and ties each to a specific technical or market gap.

For brands planning a campaign

A cybersecurity buyer evaluating advisory or thought leadership can use this to test Nick Sullivan on adjacent product strategy, detection changes as IP reputation weakens, and cloud security economics. It supports positioning a technical engagement beyond PQC, provided the campaign centers on the company's actual offering.

Examples: Source 1

Advisory and consultation for founders and security teams

Nick Sullivan launched an Intro profile, booked four calls, and offers brainstorming with founders and engineers on cybersecurity and privacy, advice on building companies, discussion of advisory impact, consulting projects, board positions, and post-quantum cryptography migration consultations.

The posts direct interested people to a booking link.

For brands planning a campaign

This is direct evidence for a technical advisory engagement.

Scope deliverables, availability, and fit rather than assume a media sponsorship.
Ask for examples of prior advisory outcomes before committing, as the posts describe conversation topics rather than completed project results.

Examples: Source 1 · Source 2

Communicating standards and industry shifts

Nick Sullivan connects technical standards to business action by naming the standards, summarizing their intended roles, citing deployment milestones from major technology companies, and pointing readers to NIST guidance for approaching the transition.

They also state they have been personally involved in post-quantum cryptography for half a decade and describe work with Cloudflare on its PQC transition.

Combines standard names, rollout dates, and named industry examples, then translates them into a call for business action.

For brands planning a campaign

Useful for a brand that needs a credible explainer or advisory voice on PQC migration, especially if the campaign requires someone who can bridge standards bodies, cloud providers, and enterprise adoption. Verify the depth and current status of any commercial relationship before treating it as an endorsement.

Examples: Source 1

Sources for this section

Brands and businesses

Nick Sullivan's posts describe one direct working relationship — with Cloudflare, on its post-quantum cryptography transition — and reference other companies and standards bodies as examples in the field.

They also take consulting and advisory inquiries through the booking platform Intro. No post states an employment relationship, sponsorship, affiliate arrangement, or investment; ask Sullivan to clarify any such ties before engaging.

Cloudflare

Disclosed partnership

Sullivan writes that working with Cloudflare on its post-quantum cryptography transition was a high point in their work in the field.

They point to Cloudflare's use of post-quantum cryptography for internal communications and to origin servers. Ask Sullivan to clarify whether the relationship was employment, contract work, or a collaboration.

View example

Intro

Mention

Sullivan says they launched a profile on Intro and booked four calls through it.

They link to the same booking page when offering consultations, advice to founders, consulting pitches, and board positions.

Intro is the platform they use to take inbound inquiries.
Ask about commercial terms before booking.

View example

NIST

Mention

NIST is a recurring reference point in Sullivan's post-quantum cryptography writing.

They summarize the release of the first three NIST post-quantum standards (FIPS 203, 204, and 205) and point businesses to NIST guidance for planning the transition.

View example

Google

Mention

Sullivan cites Google's deployment of post-quantum cryptography for internal communications and its later rollout in the Chrome browser as milestones in the wider transition.

View example

Sources for this section

Topics and similar creators

Nick Sullivan writes about post-quantum cryptography as a migration problem that has moved from standards drafting into deployment.

Their posts explain NIST's first three finalized PQC standards, track Google and Cloudflare rollouts, and draw practical lessons from advisory conversations about confidential computing, privacy tools weakening IP reputation, and costly production security tooling.

Start with the NIST standards post and the Google/Cloudflare deployment timeline, then read the advisory takeaways for a view of the security and privacy problems they track.
They also offer consultations, company-building advice, and board work for readers seeking advisory help.

Post-quantum cryptography Cybersecurity Cryptography standards Quantum migration Privacy technology Confidential computing Cloud security Security advisory LinkedIn posts Cybersecurity professionals Founders and engineers

Kostiantyn Polosukhin

Polosukhin also covers post-quantum cryptography as a business risk.

Their HarvestGuard post explains harvest-now-decrypt-later through travel-industry fraud and calls for migration before Q-Day.

Polosukhin's posts range across manufacturing technology and industrial automation. Their PQC post promotes HarvestGuard rather than explaining standards and platform deployments.

Read original · Original 2

Ben Volkow

Volkow tracks the same policy and operational shift in PQC, covering Executive Order 14412 and the G7/ANSSI and CISA calls for quantum readiness, including crypto inventories, CBOMs, and migration roadmaps.

Volkow writes from a vendor-execution perspective, focusing on gaps in federal funding, sector guidance, and production-ready ecosystems. Sullivan's posts combine standards explanations with personal advisory availability.

Read original · Original 2

Chaitanya Challa

Challa also treats PQC as an execution phase, writing about crypto agility, dependency mapping, and the U.S.

Treasury's Quantum-Readiness Task Force.

Challa frames the challenge around modernizing cryptography across applications, devices, OT, and supply chains, and asks how to orchestrate ecosystem-wide migration. Sullivan's available posts focus more on NIST standards, major-platform deployments, and advisory takeaways.

Read original · Original 2

Sources for this section

Audience

Use this section to assess whether Nick Sullivan’s LinkedIn audience can support a post-quantum cryptography technical advisory engagement aimed at PQC decision-makers.

Their LinkedIn following was 5,455 as of October 23, 2026, and they published three posts from August 2023 to September 2024 about PQC standards, Google/Cloudflare adoption, and security/privacy technology.

These posts show topical appeal, but provide no measured audience data on geography, age, gender, employer, occupation, seniority, impressions, reach, or engagement.
For a PQC advisory engagement, request recent LinkedIn analytics for comparable PQC and security posts, including follower geography, industry and seniority breakdowns if available, impressions and engagement, plus any audience survey results covering employer, occupation, or job seniority.
Follower count alone does not indicate whether the audience includes cryptography decision-makers or migration buyers.

LinkedIn followers

5455

LinkedIn profile snapshot · 2026-10-23

Sources for this section

Partnership options

Sullivan's public posts document consulting and advisory work, not sponsorship products.

In a September 2023 post, they say they are open to consultations on post-quantum cryptography migration and cite their involvement in Cloudflare's industry-leading transition to post-quantum cryptography.

In an August 2023 post, they describe launching a profile on Intro, booking calls with founders and engineers, and welcoming pitches for consulting projects or board positions.
The practical shape of an engagement is technical advisory on security and privacy problems rather than audience promotion.
The posts provide no rate card, sponsored-content format, deliverable list, audience-package description, or official partnership inquiry route; ask directly about terms.
They cover only three posts between August 2023 and August 2024, so may not reflect Sullivan's current commercial posture.

Post-quantum cryptography consultation

Buyer requirement

Sullivan says they are open to consultations helping organizations navigate the post-quantum transition, drawing on their work with Cloudflare on its post-quantum rollout.

Buyers should bring a specific migration problem, such as where they are in the transition from classical to post-quantum algorithms or how to sequence internal versus external-facing services.
This is advisory, not a sponsored post or audience placement.

Technical advisory and brainstorming calls

Buyer requirement

Through their Intro profile, Sullivan books calls with founders and engineers working on security and privacy problems.

They summarize recurring subjects raised in those calls: attestation for confidential computing, the declining usefulness of IP reputation as privacy proxies spread, and the growing cost and complexity of production security scanning.
Buyers should arrive with a defined technical question and expect a working discussion; the post describes conversations and brainstorming, not promotional deliverables.

Consulting projects and board positions

Buyer requirement

Sullivan says they are happy to discuss consulting projects or board positions and talk about their approach to helping founders build companies.

Buyers seeking a longer commercial relationship should make a direct pitch.
The posts publish no scope, fee structure, exclusivity term, or contract terms; agree these case by case.

Sources for this section

Campaign fit

A campaign to shortlist

Good fit for a scoped technical advisory engagement; poor fit for paid audience placement. The value depends on scoping the work as advisory, not promotion.

Brief

A cybersecurity company with post-quantum cryptography offerings wants a technical adviser to help enterprise customers plan a PQC migration: which NIST standards apply where, how to sequence internal and customer-facing services, and how to move customers from standards awareness to operational rollout. The proposed engagement focuses on PQC migration strategy.

Limits

No published fee, engagement scope, deliverable list, exclusivity term, or contract terms appear in the posts. Agree on these directly.

The posts show availability and subject-matter expertise, not completed advisory outcomes. Ask for examples of prior advisory work before committing to a customer-facing engagement.

Commercial evidence covers three posts dated 23 August 2023, 29 September 2023, and 13 August 2024. Confirm Nick Sullivan’s current availability and commercial posture.

The only audience evidence is a follower count of 5,455 from 23 October 2026, with no measured composition. Don’t sell the engagement internally as audience reach.

Don’t buy this as a sponsored post or audience placement. The posts document consultations, calls, and openness to pitches for consulting projects or board positions—not sponsorship products.

Why it fits

Nick Sullivan publicly offers post-quantum cryptography consultations and points to work on Cloudflare’s post-quantum transition as relevant experience. That closely matches the expertise this brief requires.

Nick Sullivan explains the three finalized NIST standards in usable terms: FIPS 203 ML-KEM for general encryption, FIPS 204 ML-DSA for digital signatures, and FIPS 205 SLH-DSA as a backup if ML-DSA proves vulnerable. The engagement can therefore address algorithm-level choices rather than repeat generalities about quantum threats.

Sullivan treats the transition as an operational imperative and recommends moving both internal and external-facing services to support post-quantum cryptography. That’s the sequencing decision the brief asks about.

The deployment timeline Sullivan tracks gives the engagement concrete reference points: Google deployed post-quantum cryptography for internal communications in November 2022 and rolled it into Chrome by August 2023; Cloudflare introduced Chrome-compatible post-quantum cryptography and uses it for internal and origin-server communications.

Sullivan’s advisory calls with founders and engineers cover live security problems, including attestation for confidential computing, the weakening of IP-reputation-based detection as privacy proxies spread, and the cost and complexity of production security scanning. If a customer’s migration touches those areas, the discussion can extend beyond an algorithm swap.

Sullivan has stated personal involvement in post-quantum cryptography for half a decade, supporting the view that migration is an established area of expertise rather than a newly adopted topic.

When to choose a specialist

Poor fit.

Brief

A general-professional software brand wants eight sponsored LinkedIn posts over three months to raise awareness of a new quantum-computing explainer hub. The brief requires a defined deliverable list, guaranteed impressions, and audience-package metrics for an 18–44 general-professional following.

What would change it

A documented sponsorship format and audience analytics would make this brief assessable. On current evidence, take it to a creator with a published placement offer and measured audience composition.

Why it fails

The posts show no sponsored-content product. Sullivan offers consultations and brainstorming calls, and is open to pitches for consulting projects or board positions—not posts for placement.

There’s no published rate card, deliverable list, audience package, or sponsorship disclosure, so the required commercial terms can’t be planned against.

The only audience evidence is a follower count of 5,455, with no measured geography, industry, seniority, occupation, impressions, or engagement. Guaranteed impressions and general-professional targeting can’t be assessed from that.

Sullivan’s posts offer technical explanation and advisory availability, not promotional placement. A campaign seeking brand-message amplification rather than a practitioner’s analysis is buying the wrong thing.

The subject matter is specialist. Sullivan explains PQC standards and deployments and works through security engineering problems with founders and engineers; the posts provide no evidence of a general-professional audience for an explainer hub.

A worked campaign example

Angle

Run the engagement as a three-part advisory sequence focused on migration decisions rather than general education, with an optional extension module for adjacent architecture questions.

Brief

The same PQC advisory brief: a cybersecurity company with post-quantum cryptography offerings seeks a technical advisory engagement on PQC migration strategy.

Deliverable

Deliver a written migration decision brief covering the service inventory, standards mapping, phased sequence, and open questions, plus two working sessions. The posts don’t state the fee, scope, or availability; agree on these directly.

Steps

Detail: Start with Sullivan’s framing of the transition as an early-adopter phase in which businesses should move both internal and external-facing services. Use the call to establish where the company and its customers sit between classical and post-quantum algorithms, and which services must move first, rather than opening with a primer on quantum threats.
Title: Scoping call

Detail: Map the company’s cryptographic inventory to the three finalized standards: FIPS 203 ML-KEM as the primary general-encryption standard, FIPS 204 ML-DSA as the primary digital-signature standard, and FIPS 205 SLH-DSA as a backup if ML-DSA proves vulnerable. Sullivan’s explainer sets out those roles and the selection process behind them—the terminology the company’s customers will encounter.
Title: Algorithm and standard teardown

Detail: Build the sequence from the deployment examples Sullivan tracks: internal communications first at Google in November 2022, then browser and web traffic in Chrome by August 2023, then Cloudflare's internal and origin-server communications. The company can reuse that ordering as a decision framework for customers and attach NIST's transition guidance.
Title: Phased rollout plan

Detail: Include Sullivan's advisory topics—attestation for confidential computing, threat detection as IP reputation weakens under privacy proxies, and the cost and complexity of production security scanning—only where a customer's migration touches them.
Title: Optional extension module on adjacent architecture

What to confirm

Ask for examples of prior advisory outcomes; the posts document availability and conversation topics, not finished projects.

Confirm current availability and rates; the commercial evidence reviewed dates from August 2023 to August 2024.

Keep the engagement advisory. Ask whether sponsored posts or guaranteed-reach placements are available; neither is documented in the posts here.

Sources for this section

Who else to consider

Kostiantyn Polosukhin

Choose Polosukhin when the buyer's hard problem is finding quantum-vulnerable cryptography in code, configuration files, keys, and certificates, or when the engagement needs a working scanning habit rather than a strategy document.

The HarvestGuard post describes a tool that scans those assets before an attacker does, and the manufacturing-tech post shows how advanced technologies are translated into an operator's integration checklist. For a cybersecurity company whose customers ask where their cryptography is rather than which NIST standard applies, this is a more concrete starting point than a standards-and-deployment narrative.

The tradeoff is a stronger focus on product-led tooling and industrial-tech scanning.

These posts offer less detail on NIST algorithm roles and on sequencing internal versus customer-facing service migrations.
Buyers who need an algorithm-level teardown and phased migration plan should ask for that specificity.
The manufacturing and travel examples also appear alongside a commercial tool, so treat the scan positioning as vendor positioning and verify its fit for the buyer's environment.

Examples: Source 1 · Source 2

Ben Volkow

Choose Volkow when the buyer needs a governance- and inventory-first readiness program, especially in federal or regulated critical-infrastructure contexts.

The G7 and ANSSI post lays out the operational fundamentals in order: discover where cryptography is used, keep a cryptographic inventory, use a machine-readable CBOM to map dependencies, assess quantum risk, and establish governance and a migration roadmap.

The executive-order post focuses on turning federal mandates into funded, measurable execution across healthcare, finance, energy, and telecom.
For buyers whose PQC engagement starts with the fact that they cannot manage what they have not inventoried, this is a better match than an explainer on finalized standards and early deployments.

The tradeoff is distance from algorithm selection.

The posts center on inventory, CBOM, funding, and ecosystem readiness; they do not walk through FIPS 203, 204, and 205 roles.
Buyers who need help choosing between ML-KEM, ML-DSA, and SLH-DSA, or explaining those choices to engineers, will find less of that here.
The posts also reflect a vendor or consulting position around QIZ, so confirm whether the engagement is advisory or platform-led.

Examples: Source 1 · Source 2

Chaitanya Challa

Choose Challa when the buyer's bottleneck is dependency mapping and migration orchestration across a large regulated enterprise, particularly in banking, healthcare, or critical infrastructure.

The Treasury post describes a sequence: discovery, dependency mapping, risk prioritization, crypto agility, migration orchestration, continuous readiness.

It explains that a bank can migrate its own RSA and ECC implementations while exposure remains in SaaS platforms, HSMs, payment systems, APIs, software libraries, and market infrastructure.
The executive-order post adds the operational reality of modernizing cryptography across applications, devices, OT, medical technology, hardware, supply chains, and accumulated technical debt.
For buyers whose PQC strategy keeps stalling on third-party and legacy-system dependencies, that framing is more useful than a standards summary.

The tradeoff is a focus on industry analysis and commentary.

These posts offer less direct insight into NIST's finalized standards, Cloudflare's deployment timeline, or publicly offered consultations.
Buyers who need an algorithmic teardown or a known advisory offer should ask what is available.
Challa's posts also gesture at a series on national security, so confirm whether the relevant sector depth is available for the buyer's specific regulatory context.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Campaign brief: Nick Sullivan

Download

Completed example: PQC migration advisory

Download

Sources for this section

Research methodology

Nick Sullivan's three full LinkedIn posts cover NIST's first three finalized post-quantum cryptography standards, Google's and Cloudflare's post-quantum deployments, takeaways from advisory calls about confidential computing, IP reputation, and production security tooling, and Sullivan's description of offering consultations and taking work through the booking platform Intro.
The posts are dated 23 August 2023, 29 September 2023, and 13 August 2024, though the post texts themselves do not give dates.
A LinkedIn profile snapshot dated 23 October 2026 shows a follower count of 5,455.
Three comparable creator accounts provide context for the similar-creator comparisons.
The posts here are a small set, not a full career corpus.
They do not include a signature book, show, business, or earlier body of work, transcripts, reports or press coverage, or audience analytics beyond the follower count, so this page does not claim a complete account of why people search this name, and its conclusions rest on the three posts alone.
Nick Sullivan's posts do not mention a sponsorship offer; that is a gap in what the posts say, not proof that none exists.

Brands they talk about

Google