Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
ec2_client_vpn_endpoint_connection_logging_enabledProvider: AWS
Service:
ec2Severity: LOW
Categories:
loggingResource type:
AwsEc2ClientVpnEndpointWhat this check verifies
AWS Client VPN endpoints are evaluated for client connection logging that records client connect/disconnect events to CloudWatch Logs. The evaluation detects endpoints where this logging is disabled.Risk
Without Client VPN connection logs, remote access lacks an audit trail, reducing detection and accountability.- Stolen credentials can be used unnoticed
- Lateral movement and data exfiltration persist Impacts confidentiality and integrity; delayed investigation can degrade availability.
Recommendation
Enable client connection logging on all Client VPN endpoints and send events to a centralized log group.- Enforce least privilege on log access
- Define retention and immutability
- Integrate with monitoring/alerts
- Separate VPN operations from log administration
- Review anomalous login patterns
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/what-is.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/ec2-controls.html#ec2-51
- https://docs.aws.amazon.com/config/latest/developerguide/ec2-client-vpn-connection-log-enabled.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = ec2_client_vpn_endpoint_connection_logging_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks