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
Supported integration
One of the following Apono integrations:
Kubernetes: Kubernetes
SSH: SSH Servers or AWS EC2 SSH Servers
Windows Domain Servers: Windows Domain Servers
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:
Use the EKS steps for Kubernetes-based connectors
Use the ECS CloudFormation or ECS Terraform steps for ECS-based connectors.
Follow these steps to configure the connector:
Set the environment variables.
Verify AWS Load Balancer Controller is installed on the EKS cluster.
Obtain the EKS cluster OIDC provider.
Save the following trust policy as apono-connector-trust-policy.json.
Create or update the IAM role trust policy.
Confirm that the role trust policy is configured correctly.
Retrieve the IAM role ARN and save it as an environment variable.
Create and attach the S3 write policy to the role created or updated above.
Add the following configuration to your Helm values file, for example values.yaml. The
proxyServiceblock provisions a Network Load Balancer (NLB) that exposes the Apono connector on ports10020-10024.
Upgrade the Apono connector Helm chart to v2.1.7 with the values file.
Annotate the connector service account with the IAM role ARN so the connector can authenticate to S3.
Verify that your VPN, security groups, and internal DNS allow developer machines to resolve the NLB DNS name and connect to ports
10020-10024.
Follow these steps to configure the connector:
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.Create and configure an S3 bucket in the AWS account that will own the Session Audit bucket.
Create and attach the S3 write policy to the connector IAM role.
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:
Install a new ECS connector with AWS permissions.
Update your Terraform configuration to use the NLB-enabled connector module and configure the NLB settings.
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"]
Create and configure an S3 bucket in the AWS account that will own the Session Audit bucket.
Create and attach the S3 write policy to the connector IAM role.
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:
Save the following S3 write policy locally as apono-connector-s3-session-audit-policy.json.
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.
Copy the ARN. This will be used to attach the policy to the IAM role.
Define the following environment variable.
Attach the policy to the existing connector IAM role.
Tag the connector IAM role so it matches the
aws:PrincipalTag/apono-connector-s3-access conditionin the S3 policy.
Create an S3 bucket
Follow these steps:
Set the bucket variables.
Create the region-specific S3 bucket.
Block public access on the S3 bucket.
(Recommended) Set S3 Object Ownership to
BucketOwnerEnforced.
(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.
(Recommended) Enable S3 Versioning to help recover Session Audit object that are accidentally deleted or overwritten.
Tag the bucket.
(Recommended) Configure Object Lock retention according to your organization’s audit log retention policy.
Save the following bucket policy locally as apono-session-audit-bucket-policy.json.
Apply the bucket policy from the AWS account that owns the S3 bucket to grant the Apono connector permissions to the bucket.
Confirm that the bucket policy was applied.
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.
Connector enablement

Follow these steps to enable Session Audit for the connector:
On the Connectors tab, in the row of the Apono connector associated with the integration, click ︙ > Edit. The Edit Connector page appears.
Toggle Audit sessions to ON. The toggle will appear green when enabled.
Under Session History Bucket ARN, enter your S3 bucket ARN.
Enter the Connector Endpoint.
Click Update Connector.
Integration enablement

Follow these steps to enable Session Audit for the integration:
On the Connected tab, in the row of a supported integration, click ︙ > Edit. The Edit Integration page appears.
Under Get more with Apono, toggle Audit sessions to ON. The toggle will appear green when enabled.
Last updated
Was this helpful?
