Two-factor sign-in for every userOperational
Required for all accounts, using authenticator apps with recovery codes.
Security & trust
Intelligence you can rely on.
Highground is built around accountability: who can see what, who must approve what, and a record of everything that happened. This page describes controls in the current build — and is clear about what is still in development.
Access & identity
Strong sign-in. The right permissions.
Enterprise single sign-onIn Development
OIDC and SAML 2.0 (e.g. Entra ID, Okta, Google Workspace) are implemented and tested; the first connection is set up with each client's IT team.
Role-based accessOperational
Permissions follow roles — analyst, senior analyst, supervisor, intelligence manager, client administrator and client users.
Configurable permissionsOperational
Access is configured per organization — including who may view personal contact details and who receives handed-off alert results.
Organization isolationOperational
Each organization's data is kept separate; every query is scoped to the organization at application level. Additional database-level enforcement is built and will be enabled after independent review.
Personal data views recordedOperational
Opening a person's contact details or profile is recorded in the audit trail.
Governance
Two sets of eyes where it matters
Highground separates the person who prepares from the person who approves.
- Approval workflowsAnalyst-created incidents and every edit to a published incident require senior approval. Nobody approves their own work.
- Human-governed communicationsNo external message is sent without a deliberate human send and the applicable approval — not by workflows, not by AI, not on a timer.
- Source attributionIncidents keep their sources and provenance; translations are shown only with recorded provenance.
- Tamper-evident audit trailAn append-only, hash-chained record of who viewed, changed, approved or sent what.
app.thehighground.io
Separation of duties — senior approval of a proposed change
Data & AI
Retention by policy. AI under your control.
Data retention controlsIn Development
Retention is configurable by organization and data class, with legal holds that override deletion. Retention policy values are provisional and the engine runs in review mode until policies are approved.
Responsible AI useIn Development
AI features are individually switchable per organization with spending caps, and all are off in the current build. AI may draft and recommend; it never publishes incidents or sends communications. Confidential investigations are blocked from AI by data policy.
Ready to see Highground in action?
Gain a global advantage
Discover how Highground can support your organization's intelligence, security, and operational risk management needs.