Data, collection and responsibilities

01 · WHAT HIIH MAY COLLECT

The data classes a deployment may produce.

Network & protocol observations
Source context, connection metadata and service interaction supplied to a HIIH target during hostile contact.
Authentication material
Usernames, passwords, tokens, keys or other material an actor presents to a HIIH target — captured as the adversary supplies it.
Session activity
Commands, terminal activity, files, tools and post-access behavior on supported targets, where the engagement depth allows.
Evidence artifacts
Captured binaries, session recordings or related artifacts, where the target and engagement support them.
Structured HIIH Findings
Observed facts, assessment, confidence, relevance, recommended actions and links to the supporting observations behind them.
Customer-supplied context
Exposure profile, mission question, target characteristics and delivery configuration provided to deploy the Surface.
Data presented by an adversary may concern third parties, victims or compromised infrastructure. Handling, access, retention, redaction and export therefore belong to the deployment record and contract — not to a blanket claim that the customer “owns everything.”
02 · DATA HANDLING AND ACCESS PRINCIPLES

Principles stated publicly; contractual detail sits in the data processing agreement (DPA).

Purpose limitation — data are collected to operate the Surface, analyze hostile activity, produce Findings and support the outputs you retrieve.
Access limitation — access is restricted to authorized OHIIHO personnel, authorized partner operators and customer users according to the service model.
Retention by deployment — retention periods depend on the data class, deployment and contract.
Redaction and minimization — sensitive third-party data are minimized or redacted for briefings, Research and redistribution where required.
Controlled export — export rights and formats are documented for your deployment. Public Research is not an automatic downstream use of customer data.
Customer separation — customer-specific evidence and outputs are logically separated; any future cross-Surface correlation requires a separately governed path.
Publication review — Research publication requires sanitization and approval appropriate to provenance and sensitivity.
Data handling is documented for your deployment. The public page states principles, not a universal retention period or jurisdiction guarantee.
03 · RESPONSIBILITY MODEL

OHIIHO operates the engagement environment. You define the mission and use the intelligence.

AreaOHIIHOMSSP / partnerCustomer
Surface design & operationprimarycontributes service contextbrings the mission
Engagement environmentbuilds, hosts and managesdoes not operate hostile infrastructuredoes not host hostile execution
Exposure configurationdeploys the exposuremay implement with customercontrols customer-side change
Evidence & Findingscollects and structuresconsumes, triages and packages for serviceuses under its access rights
SOC responseplatform / research supportL1/L2 and client workflow in partner modelacts through its security process
Data governanceimplements the controlsfollows service obligationssets contractual terms and authorized users

Typical managed model. The exact split may vary by contract.

HIIH does not ask every customer or MSSP to become a honeypot operator. OHIIHO operates the specialized engagement environment. The customer or partner brings the mission, chooses the exposure and uses the resulting signal inside its existing security process.

For partners · Delivery & integrations