Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Session Audit Implementation

Configure the connector, storage, and integrations required for auditing privileged access sessions

Session Audit captures privileged access session activity after the required connector, network, storage, and integration settings are configured. This article walks through the setup required to enable it.


Limitations

Before you set up Session Audit, review the following limitations.

RDP Session Audit:

  • Windows support: Both the client machine and target machine must run Windows 2012 or later.

  • Concurrent sessions: RDP Session Audit supports up to 100 concurrent sessions.

  • Storage: RDP Session Audit has a 20 GB storage limit for ongoing recordings across all concurrent sessions. If the limit is reached, new audited RDP sessions cannot start until storage space becomes available.

  • Supported Resolution: Windows source machines support resolutions up to 2560 × 1920.

  • Copy and paste: Select-all (Ctrl+A) is not currently supported within an audited RDP session.

When connecting to a Windows Domain Server through RDP using access granted through Apono:

  • Certificate warning: The RDP client may display the following warning. It is safe to click Yes to continue the RDP session.

  • User login: Apono displays an additional Connect to server dialog. Enter the username provided by Apono and the user's domain password, and then click Connect.


Prerequisites

Item
Description

Supported integration

One of the following Apono integrations:

Apono connector

On-prem connection serving as a bridge between the integration and Apono

Required Version: 1.8.4

Learn how to update an existing AWS or Kubernetes connector.

Connector endpoint

DNS address used to establish audited sessions through the connector proxy

Network access

Client machines must be able to resolve the connector endpoint and connect to ports 10020-10024.

Kubernetes Command Line Tool (kubectl)

(Kubernetes) Command-line tool used for communicating with a Kubernetes cluster's control plane

For audited Kubernetes sessions, kubectl 1.24 or later is supported on macOS, Linux, and Windows.


Connector configuration

The Apono connector should be configured according to your deployment type:

Follow these steps to configure the connector:

  1. Set the environment variables.

  1. Verify AWS Load Balancer Controller is installed on the EKS cluster.

If it is not installed, install the AWS Load Balancer Controller before continuing.

  1. Obtain the EKS cluster OIDC provider.

  1. Save the following trust policy as apono-connector-trust-policy.json.

The connector uses IAM Roles for Service Accounts (IRSA) so its EKS pods can access AWS services through this IAM role. The following trust policy allows only the connector service account in this namespace to assume the role via OIDC.

Replace <AWS_ACCOUNT_ID>, <OIDC_PROVIDER>, and <NAMESPACE> before saving the file. The OIDC provider value should not include https://.

  1. Create or update the IAM role trust policy.

  1. Confirm that the role trust policy is configured correctly.

  1. Retrieve the IAM role ARN and save it as an environment variable.

  1. Create and attach the S3 write policy to the role created or updated above.

  2. Add the following configuration to your Helm values file, for example values.yaml. The proxyService block provisions a Network Load Balancer (NLB) that exposes the Apono connector on ports 10020-10024.

Replace <APONO_TOKEN>, <CONNECTOR_ID>, and <SUBNETS> with actual values.

  1. Upgrade the Apono connector Helm chart to v2.1.7 with the values file.

  1. Annotate the connector service account with the IAM role ARN so the connector can authenticate to S3.

  1. Verify that your VPN, security groups, and internal DNS allow developer machines to resolve the NLB DNS name and connect to ports 10020-10024.

The NLB is provisioned as internal by default.

Follow these steps to configure the connector:

  1. Provision a Network Load Balancer (NLB) in front of the ECS connector on ports 10020-10024. Apono will provide a revised CloudFormation Stack template for this step.

  2. Create and configure an S3 bucket in the AWS account that will own the Session Audit bucket.

The bucket policy grants access to connector roles that match the aws:PrincipalTag/apono-connector-s3-access and aws:PrincipalOrgID conditions.

  1. Create and attach the S3 write policy to the connector IAM role.

  2. Verify that your VPN, security groups, and internal DNS allow developer machines to resolve the NLB DNS name and connect to ports 10020-10024.sh

Follow these steps to configure the connector:

  1. Update your Terraform configuration to use the NLB-enabled connector module and configure the NLB settings.

The Terraform module provisions a Network Load Balancer (NLB) for audited sessions and exposes ports 10020–10024. Set nlbScheme and nlbSubnetIds to control NLB visibility and subnet placement. Use nlbIngressCidrs to restrict inbound access to trusted client networks.

Ensure that the Terraform input variables referenced in the configuration are defined in your root module.

Parameter
Description

nlbScheme string

Defines the NLB visibility

Set to internet-facing if the connector needs to be reachable from outside your VPC.

Default: internal

nlbSubnetIds list(string)

Subnets to associate with the NLB

Default: []

nlbIngressCidrs list(string)

IPv4 CIDR ranges allowed to reach the NLB on TCP ports 10020–10024.

Restrict access to trusted client networks.

Default: ["0.0.0.0/0"]

  1. Create and configure an S3 bucket in the AWS account that will own the Session Audit bucket.

The bucket policy grants access to connector roles that match the aws:PrincipalTag/apono-connector-s3-access and aws:PrincipalOrgID conditions.

  1. Create and attach the S3 write policy to the connector IAM role.

  2. Verify that your VPN, security groups, and internal DNS allow developer machines to resolve the NLB DNS name and connect to TCP ports 10020–10024.

Create a policy

Follow these steps:

  1. Save the following S3 write policy locally as apono-connector-s3-session-audit-policy.json.

Replace <BUCKET_NAME_PREFIX> and <PRINCIPAL_ORG_ID> with their actual values before saving the file. The organization ID can be found in the CloudFormation stack.

  1. Create the policy in AWS. The output will include a policy ARN that resembles: arn:aws:iam::<AWS_ACCOUNT_ID>:policy/apono-connector-s3-session-audit-policy.

  1. Copy the ARN. This will be used to attach the policy to the IAM role.

  2. Define the following environment variable.

  1. Attach the policy to the existing connector IAM role.

  1. Tag the connector IAM role so it matches the aws:PrincipalTag/apono-connector-s3-access condition in the S3 policy.

Without this tag, the connector role can be denied S3 access, even after the policy is attached.

Create an S3 bucket

Follow these steps:

  1. Set the bucket variables.

  1. Create the region-specific S3 bucket.

  1. Block public access on the S3 bucket.

  1. (Recommended) Set S3 Object Ownership to BucketOwnerEnforced .

  1. (Recommended) Configure S3 default encryption with SSE-S3 (AES256). To use SSE-KMS, replace the encryption configuration with your approved customer-managed KMS key configuration.

  1. (Recommended) Enable S3 Versioning to help recover Session Audit object that are accidentally deleted or overwritten.

  1. Tag the bucket.

  1. (Recommended) Configure Object Lock retention according to your organization’s audit log retention policy.

This step applies only if Object Lock was enabled when the bucket was created in step 2.

Object Lock retention helps protect session audit data from being deleted or overwritten for a defined period.

  1. Save the following bucket policy locally as apono-session-audit-bucket-policy.json.

Same-account deployments do not always require an additional bucket policy. However, one may still be required if access is restricted by an existing bucket policy, key policy, organization guardrail, or other control.

Additionally, the organization ID can be found in the CloudFormation stack.

Replace <BUCKET_NAME_PREFIX> and <PRINCIPAL_ORG_ID> with their actual values before saving the file.

  1. Apply the bucket policy from the AWS account that owns the S3 bucket to grant the Apono connector permissions to the bucket.

  1. Confirm that the bucket policy was applied.

⬆️ Return to EKS or ECS.


Enable Session Audit

You must enable Session Audit within the Apono connector and the supported integration.

Once the connector configuration is completed, notify your Apono contact to enable the feature together.

After Session Audit has been enabled, you can review and download session information from the Session History tab.

Connector enablement

Edit the connector page

Follow these steps to enable Session Audit for the connector:

  1. On the Connectors tab, in the row of the Apono connector associated with the integration, click ︙ > Edit. The Edit Connector page appears.

  2. Toggle Audit sessions to ON. The toggle will appear green when enabled.

  3. Under Session History Bucket ARN, enter your S3 bucket ARN.

  4. Enter the Connector Endpoint.

  5. Click Update Connector.

Integration enablement

Audit sessions toggle

Follow these steps to enable Session Audit for the integration:

  1. On the Connected tab, in the row of a supported integration, click ︙ > Edit. The Edit Integration page appears.

  2. Under Get more with Apono, toggle Audit sessions to ON. The toggle will appear green when enabled.

Last updated

Was this helpful?