HIIH loop step: Surface

Anatomy and engagement assets

01 · PUBLIC SURFACE ANATOMY

The Surface combines exposure, engagement, evidence, intelligence and operations.

This map shows the roles inside a Surface and the direction of causal flow. Each component has a job; together they turn selected hostile interaction into material an analyst can use.

HIIH loop step: Surface
Selected exposure
The Surface is placed where the question exists: a public profile or an authorized non-public presence, with the context required for analysis preserved.
HIIH loop step: Surface
Engagement Gateway
OHIIHO’s engagement layer. It governs how each hostile interaction is engaged across the Surface, and what is recorded.
HIIH loop step: Surface
Contact Point
Presents a protocol-aware service or appliance interaction, collecting authentication material and early behavioral signal without providing a full operating-system session.
HIIH loop step: Surface
Live Host
Provides a real operating-system target that can sustain deeper post-access interaction and record commands, files, tooling and related activity.
Outbound control
Outbound activity from engagement targets is governed by the operating policy and deployment controls, so the environment is not unrestricted hostile infrastructure.
HIIH loop step: Observe
Evidence and analysis
Preserves observations, session records and related artifacts, and qualifies selected activity into Findings.
HIIH loop step: Retrieve
Surface Console + delivery
Makes engagements and Findings inspectable, and exposes available outputs for your security tools to retrieve.
Operations layer
OHIIHO deploys, monitors and operates the platform: hours, not months, no agents in your production.
This map is at the level required to understand deployment and value. It deliberately omits machine count, addressing, ports and placement. The technical edition of the architecture brief covers them, on request.

See the end-to-end operating model

02 · ENGAGEMENT ASSETS

Different targets answer different questions.

The adversary encounters a target, not the platform. What that target can be is what determines how much becomes defensive knowledge.

Contact Point

Role — economical, protocol-aware early signal.

The adversary encounters a service or appliance interaction able to receive authentication and protocol behavior, with no full operating-system session behind it.

The defender receives

  • access material presented
  • interaction and protocol sequence
  • selected tool or client characteristics
  • associated timing and source context

Boundary — no full operating-system session.

Medium interaction · available today
Live Host

Role — deeper observation of post-access behavior.

The adversary encounters a credible, real operating-system target.

The defender receives, where applicable

  • terminal session record and replay
  • commands, including non-interactive execution
  • files transferred and their hashes
  • tools deployed and client fingerprints
  • pivot indicators
  • related network activity and artifacts

Boundary — available claims refer to controlled deployments; they do not generalize to every operating system or protocol.

High interaction · full operating-system session
03 · ENGAGEMENT-DEPTH LADDER

Breadth for signal. Depth for behavior.

The lower-cost layers create wider visibility and early warning. Live Hosts are reserved for questions that require deeper observation of what an actor does after access. A Surface can combine these layers according to the mission and operating constraints.

DepthHIIH assetWhat the adversary encountersCurrent status
Protocol & authenticationContact Pointa protocol-aware service or appliance interactionavailable today
Full OS interactionLive Hosta real operating-system sessionavailable today
The Surface target mix is designed and managed explicitly. In conventional terminology these capabilities span low-, medium- and high-interaction deception; HIIH uses that lineage inside a larger Surface architecture.