# Review successful SonicOS SSL VPN logins

Use this small hunt pack to collect successful SSL VPN logins and review account/source combinations. It does not identify CVE-2026-19868 exploitation or determine the authentication method. A missing identity-provider event alone does not establish a SAML or MFA bypass.

## Start with the firewall

On SonicOS 7.X, open **Device > Log > Settings > Users > Authentication Access**, locate **Successful SSLVPN User Login**, event **1080**, and enable its logging. Configure forwarding to your existing syslog receiver, including the event's Syslog option, and ensure the logging level includes its priority. Check that an ordinary, authorized SSL VPN login reaches the receiver. SonicWall documents event 263 for logout, which can provide additional context. [SonicWall login-monitoring instructions](https://www.sonicwall.com/support/knowledge-base/monitoring-sslvpn-user-logins/kA1VN0000000JQz0AM)

Retain the source export and record its appliance, firmware, collection period, timezone, and collection gaps. Do not read an empty result as evidence that access did not occur.

## Any SIEM or raw syslog receiver

For native SonicOS key/value syslog, select the **message ID field `m` equal to `1080`**. Use your receiver's exact field filter. A free-text search for `1080` can also match another field or message content. The native event reference documents `m`, `time`, `sn`, `usr` (or `user`), and `src`; `src` can contain an address plus optional port/interface information. [SonicOS/X 7.0.1 event reference, event 1080 and Syslog Events](https://www.sonicwall.com/ja-jp/techdocs/pdf/SonicOS-X_7.0.1_LogEvents_ReferenceGuide.pdf#page=60)

For a UTF-8 text export with one key/value event per line, the optional Python 3 selector requires only the standard library:

```text
python select_native_1080.py sonicwall.log > successful-ssl-vpn.log
```

Run it on an export already restricted to your SonicOS firewalls. It selects an exact `m=1080` token, retains the event text, and reports missing IDs, duplicate IDs, and malformed quoting separately to standard error. Review those counts and the source records; skipped lines are a collection/parsing question. This selector does not support CEF/ArcSight, CSV, JSON, wrapped events, or vendor-specific escaping beyond shell-style quoted key/value text. Keep the source file for evidence.

## Elastic, if the standard integration already works

Use the `logs-sonicwall_firewall.log-*` data view in **Discover**, set your investigation time range, select **KQL** (Kibana Query Language), and paste `elastic-successful-ssl-vpn-logins.kql`:

```kql
data_stream.dataset:"sonicwall_firewall.log" AND event.code:"1080"
```

Add `@timestamp`, `observer.serial_number`, `user.name`, and `source.ip` as columns. `elastic-reviewable-ssl-vpn-logins.kql` adds existence checks for the last three fields. Compare the two result sets so incomplete events remain visible. Empty strings can satisfy KQL existence checks; inspect and remediate empty identity fields before grouping. [KQL syntax](https://www.elastic.co/docs/reference/query-languages/kql)

Prerequisites: Elastic Agent with the SonicWall Firewall integration, Enhanced Syslog or a supported log-file input, and working timestamp/field parsing. The integration is listed at Basic subscription level. Its compatibility statement explicitly names SonicOS **6.5 and 7.0**; it does not establish compatibility with **7.3 or 8.2**. On those releases, verify event 1080 and the actual parsed fields with an authorized normal login before relying on the query. Use the raw-event route if parsing is incomplete. [Elastic integration and setup](https://www.elastic.co/docs/reference/integrations/sonicwall_firewall)

For ongoing anomaly review, Elastic also provides [First Seen SonicWall Remote Access Login by User and Source](https://www.elastic.co/docs/reference/security/prebuilt-rules/rules/network/initial_access_first_seen_sonicwall_remote_access_identity_source). It reviews new appliance/user/source combinations against a 14-day history and covers other remote-login IDs in addition to 1080. Follow its setup and current rule prerequisites rather than treating this pack's basic filter as an alert rule.

## Review the retained events

Compare each appliance/account/source combination with your historical records and expected users. Prioritize newly seen combinations, unexpected privileged accounts, unusual times, and user-reported unauthorized sessions. Validate travel, changing ISP addresses, new users, and approved support access before escalating. Preserve separate account realms and appliance identity; do not merge users on a short username alone.

For a suspicious session, establish its time, account, source, and assigned tunnel address from the available records. Review relevant identity-provider, authentication-server, firewall, and endpoint evidence using your incident process. First check clock alignment, retention, export scope, and account mapping when identity-provider evidence is absent. Confirmed unauthorized access warrants containment and credential review under that process; absence of an IdP record does not by itself attribute the session to this CVE.

## Validation included

The fixtures are synthetic, use a demonstration appliance name and documentation IP addresses, and contain no exploit traffic. In `fixtures/native-events.log`, lines 1 and 6 select; lines 2 to 4 do not; lines 5, 7, and 8 are missing-ID, duplicate-ID, and malformed-quote cases. Line 6 stays visible despite missing account/source data. In `fixtures/elastic-events.ndjson`, the broad filter should match lines 1 and 5; the existence filter should match only line 1. These are matching expectations, not captured appliance output.

The raw selector was executed against these fixtures. The KQL expressions were checked against the documented syntax and fixture predicates; they were **not executed in Kibana or a customer tenant**, and no real SonicOS parser, appliance, SAML flow, or exploit was tested. Verify your own collection and parser before operational use.
