3a77b44a featured anyx admin conceptswhat is agilicus

What is Agilicus AnyX?

CONTACT

Agilicus AnyX is a cloud-based zero trust network access platform. It gives users secure, granular access to an organisation’s applications, desktops, file shares, databases, and other resources without a traditional virtual private network (VPN) and without exposing any inbound network ports.

The platform is built on three capabilities that work together:

  1. Unified authentication. Users sign in with their existing corporate credentials (single sign-on). The platform integrates with identity providers such as Google, Microsoft, Apple, Active Directory, and Yahoo, so there are no shadow accounts to maintain. When a user leaves the organisation, their access is decommissioned automatically because their identity goes with them.
  2. Precise authorisation. Access is granted per user, per resource, down to the individual role or application. An administrator can give one user read-only access to a remote desktop and another user full control, all within the same portal. There is no all-or-nothing network access.
  3. Seamless access. Users connect from any network, including carrier-grade network address translation, with nothing to install for browser-based access. A lightweight connector runs outbound from your site to the Agilicus cloud, so your resources are never directly reachable from the internet.

The administrative portal

This guide documents the administrative portal: the web interface at your organisation’s admin domain where you manage every part of the platform. Through the portal you can:

  • manage your organisation, sub-organisations, and billing;
  • configure how users authenticate (identity providers, multi-factor authentication, sign-in theming);
  • create and manage users, groups, service accounts, and permissions;
  • define and secure resources: web applications, file shares, desktops, databases, SSH services, launchers, and networks;
  • deploy and monitor connectors that link your sites to the cloud;
  • apply policies that control who can access what, when, and from where;
  • review audit logs, sessions, and metrics; and
  • diagnose access problems.

The portal is organised into the sections shown below.

%%{init: {"theme": "base", "themeVariables": {"background": "#ffffff", "primaryColor": "#e8f1fb", "primaryBorderColor": "#1f4e79", "primaryTextColor": "#111111", "lineColor": "#4a4a4a", "secondaryColor": "#f5f5f5", "fontFamily": "Inter, sans-serif"}} }%%
flowchart TD
    subgraph Portal["Administrative portal"]
        GS[Getting Started]
        ORG[Organisation]
        AUTH[Authentication]
        ACC[Access]
        RES[Resources]
        MET[Metrics]
        PRF[Profile]
    end
    GS --> GS1[Connect to sites]
    GS --> GS2[Identify users]
    GS --> GS3[Expose a resource]
    ORG --> ORG1[Billing]
    ORG --> ORG2[Sub-organisations]
    ORG --> ORG3[Audit and sessions]
    AUTH --> AUTH1[Identity providers]
    AUTH --> AUTH2[Sign-in theming]
    AUTH --> AUTH3[Authentication policy]
    ACC --> ACC1[Users and groups]
    ACC --> ACC2[Permissions]
    ACC --> ACC3[Policies]
    ACC --> ACC4[API keys]
    RES --> RES1[Applications]
    RES --> RES2[Connectors]
    RES --> RES3[Shares, desktops, databases, SSH]
    RES --> RES4[Launchers and networks]
    MET --> MET1[Top users]
    MET --> MET2[Active users]

How it fits together at a high level

%%{init: {"theme": "base", "themeVariables": {"background": "#ffffff", "primaryColor": "#e8f1fb", "primaryBorderColor": "#1f4e79", "primaryTextColor": "#111111", "lineColor": "#4a4a4a", "secondaryColor": "#f5f5f5", "fontFamily": "Inter, sans-serif"}} }%%
sequenceDiagram
    participant U as User
    participant P as Agilicus cloud (identity-aware proxy)
    participant C as Connector (at your site)
    participant R as Resource
    U->>P: Sign in with corporate identity
    P-->>U: Session established (multi-factor authentication if required)
    U->>P: Request access to a resource
    P->>P: Evaluate authentication policy and authorisation
    alt Allowed
        P->>C: Forward request over outbound-only tunnel
        C->>R: Connect to the resource
        R-->>C: Response
        C-->>P: Response
        P-->>U: Resource content
    else Denied
        P-->>U: Access denied (audit recorded)
    end

See also

Web guide