Did my best friend jack all my data?

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Bbogtrotter

Thread Starter
Joined
Nov 4, 2011
Messages
1
I had always felt as if a very good friend of my installed some sort of keylogger on my PC as he had on his girfriends computer and phone. So he has the know how. Why? No idea why except people are control freaks and need to be one up on ya. Ran KL Detector and seems my computer is busy producing logs to send somewhere for someone's enjoyment. I was looking through my event log eventhough most keylogger programs leave almost no trace. In my security audit I stumbled across his name as if he had created a method to which he could log on remotely or he was actually logging on at the moment. I know just a tiny bit less than to be 100 % he had done so but could someone look at a couple of files which was produced to see if you can tell if there is anything malicious going on Please


(((((((((((((((((((((((JosiahLog Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 5:57:18 AM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An account was successfully logged on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

New Logon:
Security ID: ANONYMOUS LOGON
Account Name: ANONYMOUS LOGON
Account Domain: NT AUTHORITY
Logon ID: 0x1ddd11
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x0
Process Name: -

Network Information:
Workstation Name: JOSIAH-PC
Source Network Address: 192.168.1.109
Source Port: 49169

Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V1
Key Length: 128

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<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>4624</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T10:57:18.901180000Z" />
<EventRecordID>66507</EventRecordID>
<Correlation />
<Execution ProcessID="596" ThreadID="4452" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-5-7</Data>
<Data Name="TargetUserName">ANONYMOUS LOGON</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0x1ddd11</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">JOSIAH-PC</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">NTLM V1</Data>
<Data Name="KeyLength">128</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">192.168.1.109</Data>
<Data Name="IpPort">49169</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 7:07:20 AM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An account was successfully logged on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

New Logon:
Security ID: ANONYMOUS LOGON
Account Name: ANONYMOUS LOGON
Account Domain: NT AUTHORITY
Logon ID: 0x367314
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x0
Process Name: -

Network Information:
Workstation Name: JOSIAH-PC
Source Network Address: 192.168.1.109
Source Port: 49887

Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V1
Key Length: 128

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<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>4624</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T12:07:20.497340500Z" />
<EventRecordID>66521</EventRecordID>
<Correlation />
<Execution ProcessID="596" ThreadID="6136" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-5-7</Data>
<Data Name="TargetUserName">ANONYMOUS LOGON</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0x367314</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">JOSIAH-PC</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">NTLM V1</Data>
<Data Name="KeyLength">128</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">192.168.1.109</Data>
<Data Name="IpPort">49887</Data>
</EventData>
</Event>))))))))))important josiah)))))))))))))))))))))))))))))))))))))))))) Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 7:07:20 AM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An account was successfully logged on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

New Logon:
Security ID: ANONYMOUS LOGON
Account Name: ANONYMOUS LOGON
Account Domain: NT AUTHORITY
Logon ID: 0x367314
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x0
Process Name: -

Network Information:
Workstation Name: JOSIAH-PC
Source Network Address: 192.168.1.109
Source Port: 49887

Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V1
Key Length: 128

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<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>4624</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T12:07:20.497340500Z" />
<EventRecordID>66521</EventRecordID>
<Correlation />
<Execution ProcessID="596" ThreadID="6136" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-5-7</Data>
<Data Name="TargetUserName">ANONYMOUS LOGON</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0x367314</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">JOSIAH-PC</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">NTLM V1</Data>
<Data Name="KeyLength">128</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">192.168.1.109</Data>
<Data Name="IpPort">49887</Data>
</EventData>
</Event>
*********************LSASS>EXE ********is important bmr Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:56:58 AM
Event ID: 4905
Task Category: Audit Policy Change
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An attempt was made to unregister a security event source.

Subject
Security ID: SYSTEM
Account Name: BRUCE-PC$
Account Domain: WORKGROUP
Logon ID: 0x3e7

Process:
Process ID: 0x470
Process Name: C:\Windows\System32\VSSVC.exe

Event Source:
Source Name: VSSAudit
Event Source ID: 0x17d911
Event Xml:
<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>4905</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>13568</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:56:58.091546900Z" />
<EventRecordID>66288</EventRecordID>
<Correlation />
<Execution ProcessID="624" ThreadID="672" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">BRUCE-PC$</Data>
<Data Name="SubjectDomainName">WORKGROUP</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="AuditSourceName">VSSAudit</Data>
<Data Name="EventSourceId">0x17d911</Data>
<Data Name="ProcessId">0x470</Data>
<Data Name="ProcessName">C:\Windows\System32\VSSVC.exe</Data>
</EventData>
</Event>Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:56:58 AM
Event ID: 4905
Task Category: Audit Policy Change
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An attempt was made to unregister a security event source.

Subject
Security ID: SYSTEM
Account Name: BRUCE-PC$
Account Domain: WORKGROUP
Logon ID: 0x3e7

Process:
Process ID: 0x470
Process Name: C:\Windows\System32\VSSVC.exe

Event Source:
Source Name: VSSAudit
Event Source ID: 0x17d911
Event Xml:
<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>4905</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>13568</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:56:58.091546900Z" />
<EventRecordID>66288</EventRecordID>
<Correlation />
<Execution ProcessID="624" ThreadID="672" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">BRUCE-PC$</Data>
<Data Name="SubjectDomainName">WORKGROUP</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="AuditSourceName">VSSAudit</Data>
<Data Name="EventSourceId">0x17d911</Data>
<Data Name="ProcessId">0x470</Data>
<Data Name="ProcessName">C:\Windows\System32\VSSVC.exe</Data>
</EventData>
</Event>Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:51:53 AM
Event ID: 5058
Task Category: Other System Events
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
Key file operation.

Subject:
Security ID: LOCAL SERVICE
Account Name: LOCAL SERVICE
Account Domain: NT AUTHORITY
Logon ID: 0x3e5

Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: Not Available.
Key Name: 4c91994d-b655-4bf5-9db9-9579ede86cb5
Key Type: Machine key.

Key File Operation Information:
File Path: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\05e42f62f2fc8cce97848e72d434741d_ec2c9ad6-fc11-45d2-a204-e08d5272ca8d
Operation: Read persisted key from file.
Return Code: 0x0
Event Xml:
<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>5058</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12292</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:51:53.987153200Z" />
<EventRecordID>66273</EventRecordID>
<Correlation />
<Execution ProcessID="624" ThreadID="672" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-19</Data>
<Data Name="SubjectUserName">LOCAL SERVICE</Data>
<Data Name="SubjectDomainName">NT AUTHORITY</Data>
<Data Name="SubjectLogonId">0x3e5</Data>
<Data Name="ProviderName">Microsoft Software Key Storage Provider</Data>
<Data Name="AlgorithmName">%%2432</Data>
<Data Name="KeyName">4c91994d-b655-4bf5-9db9-9579ede86cb5</Data>
<Data Name="KeyType">%%2499</Data>
<Data Name="KeyFilePath">C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\05e42f62f2fc8cce97848e72d434741d_ec2c9ad6-fc11-45d2-a204-e08d5272ca8d</Data>
<Data Name="Operation">%%2458</Data>
<Data Name="ReturnCode">0x0</Data>
</EventData>
</Event>Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:51:53 AM
Event ID: 5058
Task Category: Other System Events
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
Key file operation.

Subject:
Security ID: LOCAL SERVICE
Account Name: LOCAL SERVICE
Account Domain: NT AUTHORITY
Logon ID: 0x3e5

Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: Not Available.
Key Name: 4c91994d-b655-4bf5-9db9-9579ede86cb5
Key Type: Machine key.

Key File Operation Information:
File Path: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\05e42f62f2fc8cce97848e72d434741d_ec2c9ad6-fc11-45d2-a204-e08d5272ca8d
Operation: Read persisted key from file.
Return Code: 0x0
Event Xml:
<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>5058</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12292</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:51:53.987153200Z" />
<EventRecordID>66273</EventRecordID>
<Correlation />
<Execution ProcessID="624" ThreadID="672" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-19</Data>
<Data Name="SubjectUserName">LOCAL SERVICE</Data>
<Data Name="SubjectDomainName">NT AUTHORITY</Data>
<Data Name="SubjectLogonId">0x3e5</Data>
<Data Name="ProviderName">Microsoft Software Key Storage Provider</Data>
<Data Name="AlgorithmName">%%2432</Data>
<Data Name="KeyName">4c91994d-b655-4bf5-9db9-9579ede86cb5</Data>
<Data Name="KeyType">%%2499</Data>
<Data Name="KeyFilePath">C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\05e42f62f2fc8cce97848e72d434741d_ec2c9ad6-fc11-45d2-a204-e08d5272ca8d</Data>
<Data Name="Operation">%%2458</Data>
<Data Name="ReturnCode">0x0</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:43:13 AM
Event ID: 4648
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
A logon was attempted using explicit credentials.

Subject:
Security ID: SYSTEM
Account Name: BRUCE-PC$
Account Domain: WORKGROUP
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Account Whose Credentials Were Used:
Account Name: bruce
Account Domain: bruce-PC
Logon GUID: {00000000-0000-0000-0000-000000000000}

Target Server:
Target Server Name: localhost
Additional Information: localhost

Process Information:
Process ID: 0x288
Process Name: C:\Windows\System32\winlogon.exe

Network Information:
Network Address: 127.0.0.1
Port: 0

This event is generated when a process attempts to log on an account by explicitly specifying that account&#8217;s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Event Xml:
<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>4648</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:43:13.500003800Z" />
<EventRecordID>66236</EventRecordID>
<Correlation />
<Execution ProcessID="660" ThreadID="5216" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:43:13 AM
Event ID: 4648
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
A logon was attempted using explicit credentials.

Subject:
Security ID: SYSTEM
Account Name: BRUCE-PC$
Account Domain: WORKGROUP
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Account Whose Credentials Were Used:
Account Name: bruce
Account Domain: bruce-PC
Logon GUID: {00000000-0000-0000-0000-000000000000}

Target Server:
Target Server Name: localhost
Additional Information: localhost

Process Information:
Process ID: 0x288
Process Name: C:\Windows\System32\winlogon.exe

Network Information:
Network Address: 127.0.0.1
Port: 0

This event is generated when a process attempts to log on an account by explicitly specifying that account&#8217;s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Event Xml:
<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>4648</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:43:13.500003800Z" />
<EventRecordID>66236</EventRecordID>
<Correlation />
<Execution ProcessID="660" ThreadID="5216" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">BRUCE-PC$</Data>
<Data Name="SubjectDomainName">WORKGROUP</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetUserName">bruce</Data>
<Data Name="TargetDomainName">bruce-PC</Data>
<Data Name="TargetLogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetServerName">localhost</Data>
<Data Name="TargetInfo">localhost</Data>
<Data Name="ProcessId">0x288</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">127.0.0.1</Data>
<Data Name="IpPort">0</Data>
</EventData>
</Event> </System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">BRUCE-PC$</Data>
<Data Name="SubjectDomainName">WORKGROUP</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetUserName">bruce</Data>
<Data Name="TargetDomainName">bruce-PC</Data>
<Data Name="TargetLogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetServerName">localhost</Data>
<Data Name="TargetInfo">localhost</Data>
<Data Name="ProcessId">0x288</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">127.0.0.1</Data>
<Data Name="IpPort">0</Data>
</EventData>
</Event>Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:43:13 AM
Event ID: 4634
Task Category: Logoff
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An account was logged off.

Subject:
Security ID: bruce-PC\bruce
Account Name: bruce
Account Domain: bruce-PC
Logon ID: 0x76cd34

Logon Type: 7

This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.
Event Xml:
<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>4634</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12545</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:43:13.500003800Z" />
<EventRecordID>66240</EventRecordID>
<Correlation />
<Execution ProcessID="660" ThreadID="5216" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetUserSid">S-1-5-21-1387153333-704987319-685517172-1000</Data>
<Data Name="TargetUserName">bruce</Data>
<Data Name="TargetDomainName">bruce-PC</Data>
<Data Name="TargetLogonId">0x76cd34</Data>
<Data Name="LogonType">7</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:43:13 AM
Event ID: 4634
Task Category: Logoff
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
An account was logged off.

Subject:
Security ID: bruce-PC\bruce
Account Name: bruce
Account Domain: bruce-PC
Logon ID: 0x76cd34

Logon Type: 7

This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.
Event Xml:
<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>4634</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12545</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:43:13.500003800Z" />
<EventRecordID>66240</EventRecordID>
<Correlation />
<Execution ProcessID="660" ThreadID="5216" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetUserSid">S-1-5-21-1387153333-704987319-685517172-1000</Data>
<Data Name="TargetUserName">bruce</Data>
<Data Name="TargetDomainName">bruce-PC</Data>
<Data Name="TargetLogonId">0x76cd34</Data>
<Data Name="LogonType">7</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:43:13 AM
Event ID: 4672
Task Category: Special Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
Special privileges assigned to new logon.

Subject:
Security ID: bruce-PC\bruce
Account Name: bruce
Account Domain: bruce-PC
Logon ID: 0x76cd25

Privileges: SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege
Event Xml:
<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>4672</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12548</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:43:13.500003800Z" />
<EventRecordID>66239</EventRecordID>
<Correlation />
<Execution ProcessID="660" ThreadID="5216" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-1387153333-704987319-685517172-1000</Data>
<Data Name="SubjectUserName">bruce</Data>
<Data Name="SubjectDomainName">bruce-PC</Data>
<Data Name="SubjectLogonId">0x76cd25</Data>
<Data Name="PrivilegeList">SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/8/2011 2:43:13 AM
Event ID: 4672
Task Category: Special Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: bruce-PC
Description:
Special privileges assigned to new logon.

Subject:
Security ID: bruce-PC\bruce
Account Name: bruce
Account Domain: bruce-PC
Logon ID: 0x76cd25

Privileges: SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege
Event Xml:
<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>4672</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12548</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2011-07-08T07:43:13.500003800Z" />
<EventRecordID>66239</EventRecordID>
<Correlation />
<Execution ProcessID="660" ThreadID="5216" />
<Channel>Security</Channel>
<Computer>bruce-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-1387153333-704987319-685517172-1000</Data>
<Data Name="SubjectUserName">bruce</Data>
<Data Name="SubjectDomainName">bruce-PC</Data>
<Data Name="SubjectLogonId">0x76cd25</Data>
<Data Name="PrivilegeList">SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege</Data>
</EventData>
</Event>
 

valis

Moderator
Joined
Sep 24, 2004
Messages
78,159
This is going to take a security expert to go over.

Also, I've edited your post to remove vulgarity; please remember this is a family-oriented site. I'm going to move this to general security, should get a few more hits there.

thanks,

v
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Members online

Top