Skip to content
CISO Marketplace Services

The services arm of CISO Marketplace

Offensive security.
AI security.
Done by operators.

We break into networks, applications and AI systems the way real adversaries do, then show you exactly how to close the path. Fixed scope, published starting prices, evidence behind every finding.

Not sure what you need? Start here — six questions, about ninety seconds.

attack-path.graph objective reached
Illustrative attack path: exposed VPN and a phished user lead to a workstation, then Kerberoasting and a file server, ending at Domain Admin.Exposed VPNT1133Phished userT1566WorkstationT1059KerberoastT1558File serverT1021Domain AdminT1078
Illustrative. Each engagement report maps the real path to MITRE ATT&CK.

Flagship practices

Two disciplines, one team.

Most real breaches now chain a traditional weakness with an AI one. We test both, together.

Not sure where to start?

Start with Phase 0.

The six pillars of the AI security program are not sold off a shelf — they are built into your ecosystem, and that requires knowing the ecosystem first. Phase 0 is a scoped, fixed-fee assessment that maps your environment end to end: every AI system in use (sanctioned and shadow), the DevSecOps reality, the data and identity stack, the SIEM / EDR / tooling landscape, and where testing should start. It defines how each pillar gets built for you (BYOK and open-source first, commercial upgrades where they earn their place), designs the integration seams into what you already run, and plans the deployment topology for distributed sites. The output is the current-state map, the future-state design and a sequenced build plan — and only then does the program get a number. CISO Marketplace members get the Phase 0 fee credited toward the program if they proceed.

From$17.5K

See Phase 0 →

The full practice

182 services across the security program.

When testing finds the gaps, the same team can close them: cloud, incident response, leadership and compliance.

Process

How every engagement runs.

Same six steps whether it's a single web application or a multi-site red team.

  1. 01

    Scoping call

    A practitioner, not a salesperson, walks through targets, constraints and what a good outcome looks like for you.

  2. 02

    Proposal & rules of engagement

    A fixed-scope proposal with tier, price and deliverables. Rules of engagement, contacts and out-of-bounds systems are agreed in writing.

  3. 03

    Sign, then start

    MSA and SOW are signed electronically and the deposit is paid. Only then does testing begin.

  4. 04

    Execution

    Testing runs to the agreed plan. Critical findings are escalated as they are found; you don't wait for the report.

  5. 05

    Report & debrief

    An executive summary plus technical findings with evidence, reproduction steps and fixes, walked through with your team.

  6. 06

    Retest

    Where the tier includes it, we verify your fixes and reissue the report, so auditors and customers see the issues closed.

Timelines are set per engagement in the SOW.

Research

Latest from the blog

All posts on cisomarketplace.com →

operations · Nov 16, 2026

A Bank's Link Scanner Hit Our Ad Beacon 55,000 Times in Six Minutes. It Wasn't an Attack

At 00:57 UTC our ad network's analytics endpoint jumped from a few dozen requests a minute to 11,000. Every request came from one corporate web proxy belonging to a large financial institution, all claiming to come from one of our news articles. Rate limiting absorbed 95% instantly, threat intel was spotless, and the cause turned out to be a security sandbox looping our own carousel beacon. Here is how we worked it out in half an hour, what our stack did on its own, and the one line of code that let it happen.

operations · Nov 16, 2026

The Scan We Fixed Six Weeks Ago Showed Up in a Partner Report: Attack Residue Outlives the Fix

An AI analytics session preparing a partner report flagged strange slot names in our ad network: leaderboard', %2527%2522, (select 198766*667891 from DUAL). It looked like a live SQL-injection attack. It was a scan from six weeks earlier, fixed the same night, whose payloads were still sitting in our analytics. Nothing executed, but attacker text nearly went out in a report. Here is how we triaged it in under an hour, why we couldn't say who sent it, and what we changed.

operations · Nov 16, 2026

What Testers Do to a Marketplace Checkout: Payments, Sign-In, and the Gap Between Our Ledger and Our SOC

We read thirty days of our payments ledger across every store and found that most checkout activity was testing, not buying. Researchers opened payment pages in bursts, tried a quantity of 50, injected a fake discount label and replayed sign-in tokens. Prices held everywhere, but four real issues and several buyer-losing flaws came out of it, and our AI-SOC saw none of the checkout side. Here is what testers do to a marketplace, what we fixed, and how we are wiring payments into the SOC.

Talk to an advisor
Advisor