V 2.0 : Scheduled Task Events
Vendor Documentation
Classification
| Rule Name | Rule Type | Common Event | Classification |
|---|---|---|---|
| V 2.0: Scheduled Task Events | Base Rule | Configuration Modified: System | Configuration |
| V 2.0: EVID 4698: Scheduled Task Created | Sub Rule | Scheduled Task Created | Information |
| V 2.0: EVID 4699: Scheduled Task Deleted | Sub Rule | Configuration Deleted: System | Configuration |
| V 2.0: EVID 4700: Scheduled Task Enabled | Sub Rule | Configuration Enabled: System | Configuration |
| V 2.0: EVID 4701: Scheduled Task Disabled | Sub Rule | Configuration Disabled: System | Configuration |
| V 2.0: EVID 4702: Scheduled Task Updated | Sub Rule | Configuration Modified: System | Configuration |
Mapping with LogRhythm Schema
| Device Key in Log Message | LogRhythm Schema | Data Type | Schema Description |
| Provider | N/A | N/A | Identifies the provider that logged the event. The Name and Guid attributes are included if the provider used an instrumentation manifest to define its events; otherwise, the EventSourceName attribute is included if a legacy event provider (using the Event Logging API) logged the event. |
| EventID | <vmid> <tag1> | Number | The identifier that the provider used to identify the event. |
| Version | N/A | N/A | The version number of the event's definition. |
| Level | <severity> | Text/String | The severity level is defined in the event. |
| Task | <vendorinfo> | Text/String | The task is defined in the event. Task and opcode are typically used to identify the location in the application from where the event was logged. |
| Opcode | N/A | N/A | The opcode is defined in the event. Task and opcode are typically used to identify the location in the application from where the event was logged. |
| Keywords | <result> | Text/String | A bitmask of the keywords defined in the event. Keywords are used to classify types of events (for example, events associated with reading data). |
| TimeCreated | N/A | N/A | The time stamp that identifies when the event was logged. The timestamp will include either the SystemTime attribute or the RawTime attribute. |
| EventRecordID | N/A | N/A | The record number assigned to the event when it was logged. |
| Correlation | N/A | N/A | The activity identifiers that consumers can use to group related events together. |
| Execution | N/A | N/A | It contains information about the process and thread that logged the event. |
| Channel | N/A | N/A | The channel to which the event was logged. |
| Computer | <dname> | Text/String | The name of the computer on which the event occurred. |
| SubjectUserSid | N/A | N/A | SID of account that requested the “create scheduled task” operation. |
| SubjectUserName | <login> | Text/String | the name of the account that requested the “create scheduled task” operation. |
| SubjectDomainName | <domainorigin> | Text/String | subject’s domain or computer name. Formats vary, and include the following: Domain NETBIOS name example: CONTOSO Lowercase full domain name: contoso.local Uppercase full domain name: CONTOSO.LOCAL For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is “NT AUTHORITY”. For local user accounts, this field will contain the name of the computer or device that this account belongs to |
| SubjectLogonId | <session> | Number | hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID |
| TaskName | N/A | N/A | new scheduled task name. The format of this value is “\task_path\task_name”, where task_path is a path in the Microsoft Task Scheduler tree starting from the “Task Scheduler Library” node |
| TaskContent | <LogonType>:- <sessiontype> OR <LogonTrigger> OR <BootTrigger>:- <subject> <LogonTrigger><Enabled> OR <BootTrigger><Enabled>:- <status> | Text/String | the XML content of the new task. If Task.Actions contain: <Exec> "Command" (mandatory) "Arguments" (optional) "WorkingDirectory" (optional) </Exec> |
| TaskContent | N/A | N/A | the XML content of the new task. If Task.Actions contain: <ComHandler> "ClassId" (mandatory) "Data" (optional) </ComHandler> |
| TaskContent | N/A | N/A | The XML content of the new task. For now, we don't have the log sample for this category. If Task.Actions contain: <SendEmail> "Server" (mandatory) "Subject" (optional) "To" (optional) "Cc" (optional) "Bcc" (optional) "ReplyTo" (optional) "From" (optional) "HeaderFields" (optional) "Body" (optional) "Attachments" (optional) </SendEmail> |
| TaskContent | <Title>:- <object> <Body>:- <objectname> | Text/String | the XML content of the new task. If Task.Actions contain: <ShowMessage> "Title" (mandatory) "Body" (mandatory) </ShowMessage> |
| ClientProcessStartKey | N/A | N/A | Windows 10 Versions 1903 and above augments the event with these additional properties: Event Version 1. |
| ClientProcessId | <processid> | Number | Windows 10 Versions 1903 and above augments the event with these additional properties: Event Version 1. |
| ParentProcessId | <parentprocessid> | Number | Windows 10 Versions 1903 and above augments the event with these additional properties: Event Version 1. |
| RpcCallClientLocality | N/A | N/A | Windows 10 Versions 1903 and above augments the event with these additional properties: Event Version 1. |
| FQDN | N/A | N/A | Windows 10 Versions 1903 and above augments the event with these additional properties: Event Version 1. |