Axia Security Help Center

Product overview & system boundaries

What Axia Security does, how data flows through the platform, and who is responsible for what.

What Axia Security does

Axia Security is a data-security platform that watches the channels where your people work, such as email, chat, collaboration tools and AI coding agents. It detects when sensitive or confidential information is shared in a risky way, explains why it matters, and helps your team respond.

Axia combines your existing DLP signals with its own AI analysis. The aim is fewer false alerts and clearer, actionable cases for the people who handle them.

Main capabilities

CapabilityWhat it gives you
ConnectConnect email, chat, DLP, ticketing and AI coding tools with guided setup.
Detect & analyseEvents are enriched and classified. AI analysis decides whether sensitive data was exposed, how severe it is, and why.
CasesFindings become cases with severity, status, owner, timeline and recommendations. Teams investigate and close them with a documented reason.
Command & InsightsA risk command centre, plus posture and operations metrics: alerts vs. true cases, time to resolve, top case types and departments.
IntelA conversational AI advisor for asking questions about cases and risk in plain language.
Act & EnforceChoose which response actions Axia may take (for example coaching the user, holding a message or revoking a share link). Express your policies in plain language.
TicketingCreate and track tickets for cases in Jira or Azure DevOps.

Some capabilities are switched on per workspace. If you don't see a page described here, ask your Axia contact.

How data flows

  1. Ingest. Connected sources send events to Axia, using the access your administrator approved during setup. Examples: a Microsoft Purview DLP alert, an email, an AI coding agent prompt.
  2. Enrich & classify. Axia extracts the relevant content and context, for example organization relations and guidance documents you uploaded.
  3. Analyse. AI models assess whether sensitive information was exposed and how severe it is. Models are accessed through Amazon Bedrock.
  4. Case. Relevant findings become cases in the Axia web application.
  5. Respond. Your team investigates, assigns, opens tickets and takes the response actions your administrator allowed.

System boundaries

Deployment models

ModelWhere it runs
Self-hosted / dedicatedIn a dedicated AWS account (customer-owned, or Axia-managed for one customer), deployed with Terraform. See the Deployment guide.
Axia-hostedIn Axia's AWS environment, managed by Axia.

In scope of the Axia platform

Outside the Axia platform

Shared responsibilities

AreaAxia SecurityYour organization
Application securitySecure development, vulnerability management, penetration testing, fixes and updatesKeeping your deployment updated to supported versions (self-hosted)
AccessRoles, encrypted sessions, single sign-on support, hashed password storageDeciding who gets access and which role; removing leavers; enforcing MFA in your identity provider
IntegrationsRequesting only the permissions each connector needs; protecting stored connector credentialsApproving consents in your tenant; rotating or revoking credentials you issued
DataEncryption in transit (TLS) and at rest; processing only for the serviceChoosing which sources to connect; data-retention decisions for your environment
InfrastructureAxia-hosted: operations, monitoring, backupsSelf-hosted: the AWS account, network, backups and account-level security