Windows Security 4698 — Scheduled task created
Windows Security 4698 — Scheduled task created. A scheduled task was created; TaskContent carries the task definition XML.
Source and collection
Windows Event Log: Security; archived .evtx is binary, while this fixture is an XML event export.
Configure Audit Other Object Access Events. Read with Get-WinEvent and preserve provider, event ID, version, computer and record ID.
Native example and provenance
publisher documentation example. Published example; no independent capture provenance claimed.
Original publisher / pinned upstream fixture — preformatted example 1
Removed Event Viewer tree expansion markers before XML tags; field values unchanged. Escaped the publisher-rendered TaskContent XML as XML text to restore a well-formed event export; this is a repaired documentation example.
Download the exact sample · Offline research kit
SHA-256: 877d4ff3226ac5276d2470e4171ae70b6ba4e0b18503a880d2dc1989671eda8b
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4698</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12804</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2015-09-23T02:03:06.944522200Z" />
<EventRecordID>344740</EventRecordID>
<Correlation />
<Execution ProcessID="516" ThreadID="5048" />
<Channel>Security</Channel>
<Computer>DC01.contoso.local</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-3457937927-2839227994-823803824-1104</Data>
<Data Name="SubjectUserName">dadmin</Data>
<Data Name="SubjectDomainName">CONTOSO</Data>
<Data Name="SubjectLogonId">0x364eb</Data>
<Data Name="TaskName">\\Microsoft\\StartListener</Data>
<Data Name="TaskContent"><?xml version="1.0" encoding="UTF-16"?> <Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task"> <RegistrationInfo> <Date>2015-09-22T19:03:06.9258653</Date> <Author>CONTOSO\\dadmin</Author> </RegistrationInfo> <Triggers /> <Principals> <Principal id="Author"> <RunLevel>LeastPrivilege</RunLevel> <UserId>CONTOSO\\dadmin</UserId> <LogonType>InteractiveToken</LogonType> </Principal> </Principals> <Settings> <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy> <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries> <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries> <AllowHardTerminate>true</AllowHardTerminate> <StartWhenAvailable>false</StartWhenAvailable> <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable> <IdleSettings> <StopOnIdleEnd>true</StopOnIdleEnd> <RestartOnIdle>false</RestartOnIdle> </IdleSettings> <AllowStartOnDemand>true</AllowStartOnDemand> <Enabled>true</Enabled> <Hidden>false</Hidden> <RunOnlyIfIdle>false</RunOnlyIfIdle> <WakeToRun>false</WakeToRun> <ExecutionTimeLimit>P3D</ExecutionTimeLimit> <Priority>7</Priority> </Settings> <Actions Context="Author"> <Exec> <Command>C:\\Documents\\listener.exe</Command> </Exec> </Actions> </Task></Data>
</EventData>
</Event>
Structure and field interpretation
| Field/path | Serialized type |
|---|---|
Microsoft-Windows-Security-Auditing | XML text |
EventID | XML text |
Version | XML text |
Level | XML text |
Task | XML text |
Opcode | XML text |
Keywords | XML text |
TimeCreated | XML text |
EventRecordID | XML text |
Correlation | XML text |
Execution | XML text |
Channel | XML text |
Computer | XML text |
Security | XML text |
SubjectUserSid | XML text |
SubjectUserName | XML text |
SubjectDomainName | XML text |
SubjectLogonId | XML text |
TaskName | XML text |
TaskContent | XML text |
- System/EventID
- Event identifier within the named provider.
- System/Version
- Version of this event layout.
- System/TimeCreated/@SystemTime
- Event timestamp in UTC.
- EventData
- Named fields; use names, not positional array indices.
- Relevant fields
- TaskName, TaskContent, SubjectLogonId
Investigation uses
- Review task action, principal and trigger; corroborate execution with process and scheduler events.
- Compare event time with ingestion time and retain the original XML for a reviewable evidence trail.
Validation boundaries
Task registration does not prove that the task ran. Later Windows versions add fields; escaped TaskContent needs a second XML parse. This sample uses event version 0.
This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.
For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.
Related sources
Ecosystem connections
- Telemetry Library — ATT&CK data components
- Detection Rules — candidate detection content
- Threat hunting — from intelligence to validated defense
- Practical security learning paths
- AdversaryGraph — evidence-led investigation
References
Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.