V 2.0 : EVID 4697 : Service Installed

Vendor Documentation

https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4697

Classification

Rule Name	Rule Type	Common Event	Classification
V 2.0 : EVID 4697 : Service Installed	Base Rule	Software Installed	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. The EventSourceName attribute is included if a legacy event provider (using the Event Logging API) logged the event.
EventID	<vmid>	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>	String/Number/Text	The severity level defined in the event.
Task	<vendorinfo>	Text/String	The task 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 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 time stamp 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	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	The SID of account that was used to install the service.
SubjectUserName	<login>	Text/String	The name of the account that was used to install the service.
SubjectDomainName	<domainorigin>	Text/String	The 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>	Text/String	A hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID.
ServiceName	<objectname>	Text/String	The name of installed service.
ServiceFileName	<object>	Text/String	This is the fully rooted path to the file that the Service Control Manager will execute to start the service. If command-line parameters are specified as part of the image path, those are logged. Note that this is the path to the file when the service is created. If the path is changed afterwards, the change is not logged. This would have to be tracked via Process Create events.
ServiceType	<objecttype>	Text/String	Indicates the type of service that was registered with the Service Control Manager.
ServiceStartType	<status>	Text/String	The service start type
ServiceAccount	<account>	Text/String	The security context that the service will run as when started. Note that this is what was configured when the service was installed. If the account is changed later, that is not logged. The service account parameter is only populated if the service type is a Win32 Own Process or Win32 Share Process (displayed as User Mode Service.). Kernel drivers do not have a service account name logged. If a service (Win32 Own/Share process) is installed but no account is supplied, then LocalSystem is used.