Separation, exposure and outbound
01 · SEPARATION FROM PRODUCTION
Hostile execution happens on HIIH targets, not your production endpoints.
HIIH is designed so adversaries interact with HIIH engagement targets, not the customer’s production endpoints.
- Selected exposure is placed where the question exists: a public profile or an authorized non-public presence.
- Hostile interaction happens inside the HIIH engagement environment.
- Contact Points and Live Hosts are HIIH targets, not customer systems.
- Production systems are not used as sacrificial evidence sources.
- HIIH does not replace endpoint, network or perimeter controls.
Adversary trafficinbound
→HIIH engagement environmentContact Points · Live Hosts
→Observations / Findingsto SOC · CTI
Production assets remain outside the hostile execution path.
Separation is not diversion. HIIH does not claim to pull all hostile traffic away from production, to sit inline in front of every asset, to guarantee observation before a real incident, to mirror the entire attack surface, or to air-gap the Surface. It adds a controlled adversary-facing source alongside your existing controls.
02 · CONTROLLED EXPOSURE AND ENGAGEMENT
“Designed to be attacked” is a deliberate operating model, not uncontrolled exposure.
A HIIH Surface exposes only the services, identities and targets defined for the mission. The placement, interaction depth and observation depth are selected deliberately. Early protocol-level contact and deeper post-access behavior are handled by different target classes inside the same managed system.
| What is exposed | What the adversary can do | What OHIIHO observes |
|---|---|---|
| selected services, identities and targets defined for the engagement | interact with a protocol-aware Contact Point or a real operating-system Live Host | authentication material, protocol behavior, commands, tooling and post-access activity |
Publicly nameable components:
HIIH loop step: Surface
Contact Point — early protocol-level signal and interaction.
HIIH loop step: Surface
Live Host — deeper post-access behavior on a real operating system.
HIIH loop step: Surface
Engagement Gateway — OHIIHO’s engagement layer.
HIIH loop step: Retrieve
Surface Console — where Findings and their evidence are inspected.
Placement and low-level configuration are deployment-specific; the technical edition of the architecture brief covers them, on request. Each target class links back to what a Surface contains.
03 · OUTBOUND CONTROL AND SAFE OPERATING BOUNDARIES
A compromised engagement target should not become infrastructure for attacking others.
Outbound activity from HIIH targets is governed by the operating policy and deployment controls. The default commercial posture does not provide unrestricted Internet access from an engagement target.
- Permitted outbound behavior, where enabled, is mission-specific and documented for the deployment.
- The customer’s production network is not an outbound path.
- How outbound control is implemented is not described publicly.