Fit, deployment, proof and limits

01 · COEXISTENCE WITH EXISTING CATEGORIES

A new source for the controls you already operate.

Existing categoryWhat it optimizesWhat HIIH adds
Firewall / IPSinline allow, block and inspectcontrolled off-production interaction and behavioral context
EASM / ASMdiscover and assess exposed assetsobserve what hostile actors do against a selected controlled profile
Vulnerability managementidentify and prioritize weaknessesevidence of real exploit or access pressure on a controlled target
External CTIbroad campaign and infrastructure contextfirst-party observations from the defined Surface mission
SIEM / XDRcorrelate operational telemetrystructured target-side Findings as a new upstream source
Canary / tripwiredeterministic touch alertprotocol context and deeper engagement where required

Honeypots are part of the technical lineage. The HIIH Surface is the managed system, and structured adversary intelligence is the output.

See where HIIH fits

02 · DEPLOYMENT PATTERNS

Selected exposure, partner-managed, or authorized non-public placement.

A · Direct selected exposure
A DNS name or IP address of your choice points at a controlled HIIH environment operated by OHIIHO. Production remains separate.
B · Partner-managed edge service
An MSSP or operator retains the client-facing integration and SOC workflow. OHIIHO operates Surface infrastructure, and the partner retrieves the outputs.
C · Non-public authorized placement
A target discoverable only from an authorized internal or restricted segment, used for high-confidence unexpected-interaction questions. Availability is documented for the deployment.
HIIH does not promise universal deployment in every network topology. Placement and profiles are documented for the deployment.
03 · RESEARCH EVIDENCE

What controlled edge exposure has already revealed.

Finding family: Access
Target-side access validation
Observed — access spraying and validation against an exposed appliance management interface, captured from the target side. Supporting material — authentication patterns, timing and the sequence of what was attempted. Outcome — the controls that interrupted the activity, plus shareable detection content.
FortiBleed from the Target Side: What Stops Them · 2026-06 Read the research →
Finding family: Engagement
Agentic use of edge access and tooling
Observed — AI-enabled tooling assembling and running an intrusion-support workflow inside a controlled environment. Supporting material — session activity, generated artifacts and operating patterns. Outcome — analysis of how AI-assisted tooling reshapes edge access and operator capability.
The AI Did Not Write the Phish. It Built the Business. · 2026-06 Read the research →
Finding family: Access
Repeated infrastructure & cross-region patterns
Observed — residential-sourced access-validation activity, probing across multiple regions, captured target-side. Supporting material — authentication sequences, client characteristics, timing and infrastructure patterns. Outcome — indicators and detection context for access validation distinct from broad scanning.
Residential Broadband Botnet Uses AsyncSSH to Validate Credentials Across Four Regions · 2026-06 Read the research →
04 · LIMITATIONS & TECHNICAL TRUTH

Limits

Honest limits
What the edge application does not claim
  • Not every edge technology or protocol is currently represented; profiles and target types are documented for the deployment.
  • Internet-exposed activity is not automatically customer-targeted.
  • HIIH does not patch, block inline or replace exposure management.
  • A Live Host captures only the behavior that actually occurs.
  • Exact scale, regions and edge availability are documented before use.
  • Research evidence demonstrates capability, not guaranteed future traffic.

Read the Trust page · Understand HIIH Findings