The offering and operating model

01 · ONE PARTNER PLATFORM, THREE SERVICE LAYERS

Three service layers on one platform.

Layer 1 — Managed preventive signal
High-context alerts from controlled targets, Contact Point and selected non-public signal, SOC enrichment.
Layer 2 — Controlled deep engagement
Live Host engagement, session and artifact analysis, post-access behavior observed separately from production, specialist escalation.
Layer 3 — First-party adversary intelligence
Structured Findings, briefing material for the recurring threat briefings your team delivers, detection and hunting content, sector or customer-specific analysis where relevance supports it.
These are layers of one product, not three separate deployments. Distribution or resale rights are governed by the partner agreement — the page does not imply unrestricted commercialization of raw evidence.
02 · WHAT THE PARTNER CAN OFFER NOW

Concrete offers available today.

Early-Signal Service
What is reaching this profile? Contact Points, alerts and structured context, handled by your L1/L2.
Engagement & Evidence Service
What happens after access? Live Host interaction, session and artifact review, HIIH Findings, OHIIHO L3 support.
Intelligence Briefing Material
What should the client understand? Periodic synthesis of observed activity, delivered by your team.

These are managed-service offers, not a public price list or marketplace. The partner dossier details each one.

03 · OPERATING MODEL

OHIIHO is the product. You are the service.

OHIIHOMSSP / PartnerEnd customer
deploys, hosts and operates the HIIH Surfaceowns the commercial and service relationshipchooses the exposure and brings the mission
operates engagement targets, control and evidence collectionintegrates outputs into SOC workflowsprovides relevant environment and risk context
handles platform support and L3 escalationruns L1/L2 monitoring, triage and responseuses Findings and decides on actions
provides Research and detection-content support where includeddelivers reporting, briefings and customer successacts through its own governance process
maintains product and deployment truthpackages the managed servicesets data and access terms by contract

OHIIHO never takes the partner’s place: no client meetings, no custom integration, no L1/L2. Your team never has to build or run a honeypot engineering practice either: OHIIHO deploys and operates the Surface behind your service, with L3 support.

04 · WHAT THE PARTNER SOC RECEIVES

The same first-party material, flowing into the workflow you already run.

HIIH Findingstructured object
→
MCP · APIpull path
→
Partner L1/L2triage · response
→
Clientescalation · reporting

OHIIHO provides L3 support behind the partner when a case requires it.

The partner SOC receives a preventive alert or Finding summary, Surface and target context, observed facts and assessment, confidence and relevance, related session or artifact links where available, a suggested analyst action, and briefing material or detection content by offer.

Where delivery stands
Pull-based delivery, one Finding identity
A Finding keeps its identity across the MCP and API pull paths, which the partner retrieves on its own schedule; STIX 2.1 over TAXII 2.1 is available by engagement. The Access Finding family is live and inspectable in the Console. A first deployment is evaluated through collection, workflow and real Findings — not through a promise that a rare advanced actor will arrive during that period.