> Source: [sk176023](https://support.checkpoint.com/results/sk/sk176023)

# sk176023 - Logs show non-compliant Remote Access user as "default"

| Property | Value |
|----------|-------|
| Solution ID | sk176023 |
| Date Created | 2021-10-25 |
| Last Modified | 2021-10-31 |
| Technical Level | General |
| Products | Endpoint Security |
| Versions | Cloud, E89.X, E88.X |
| OS | Gaia |

## Symptoms

- * Remote Access user signs in and the logs show the non-complaint user name as "default".
* 15 seconds after signing in, the logs show the non-complaint user with the correct user name.

## Solution

No fix is required; the system is functioning as designed.  
The client continuously runs the compliance check, even when it is not connected to VPN. During that time the client does not know the user name. When the client connects to the gateway again, it sends out all accumulated logs with a user name of "default". Shortly after connecting to VPN again the logs reflect the correct user name, since the client is now aware of the user.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content