我的电脑解锁了吗?


8

尽管中午记得将其锁定并且此后未使用过,但我还是在中午醒来发现我的计算机已解锁。我检查了安全日志,并从11:16 AM看到了“登录”事件。唯一的事情是,那时我睡着了,没有其他可以访问我的计算机的人知道我的密码。为了安全起见,我正在运行病毒扫描,但是到目前为止,它没有发现任何东西。会发生什么事?

事件日志条目的文本如下。

顺便说一句,我检查有围绕我想起昨晚锁我的电脑的时候了“注销”事件。

日志条目:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          1/29/2014 11:16:10 AM
Event ID:      4624
Task Category: Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      FLARNDT
Description:
An account was successfully logged on.

Subject:
        Security ID:            SYSTEM
        Account Name:           FLARNDT$
        Account Domain:         WORKGROUP
        Logon ID:               0x3E7

Logon Type:                     5

Impersonation Level:            Impersonation

New Logon:
        Security ID:            SYSTEM
        Account Name:           SYSTEM
        Account Domain:         NT AUTHORITY
        Logon ID:               0x3E7
        Logon GUID:             {00000000-0000-0000-0000-000000000000}

Process Information:
        Process ID:             0x188
        Process Name:           C:\Windows\System32\services.exe

Network Information:
        Workstation Name:      
        Source Network Address: -
        Source Port:            -

Detailed Authentication Information:
        Logon Process:          Advapi  
        Authentication Package: Negotiate
        Transited Services:     -
        Package Name (NTLM only):       -
        Key Length:             0

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 impersonation level field indicates the extent to which a process in the logon session can impersonate.

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>1</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8020000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-29T16:16:10.375881200Z" />
    <EventRecordID>96945</EventRecordID>
    <Correlation />
    <Execution ProcessID="380" ThreadID="8756" />
    <Channel>Security</Channel>
    <Computer>FLARNDT</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">FLARNDT$</Data>
    <Data Name="SubjectDomainName">WORKGROUP</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-5-18</Data>
    <Data Name="TargetUserName">SYSTEM</Data>
    <Data Name="TargetDomainName">NT AUTHORITY</Data>
    <Data Name="TargetLogonId">0x3e7</Data>
    <Data Name="LogonType">5</Data>
    <Data Name="LogonProcessName">Advapi  </Data>
    <Data Name="AuthenticationPackageName">Negotiate</Data>
    <Data Name="WorkstationName">
    </Data>
    <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x188</Data>
    <Data Name="ProcessName">C:\Windows\System32\services.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
    <Data Name="ImpersonationLevel">%%1833</Data>
  </EventData>
</Event>

您的计算机上只能访问一个帐户吗?
2014年

在这里没有太多的研究,看来“ services.exe”会在您的日志中弹出几次。查找时发现:bleepingcomputer.com/startups/services.exe-11447.html,这使我相信它可能是病毒或类似病毒。
卡伦L


2
“登录类型5” =服务。这是(作为SYSTEM)登录的服务。它(可能)是良性的,并且绝对不会将您登录到您的桌面,因此它不是这样做的。您实际上是在前一天晚上“注销”了,还是只是说了“锁定”?
Ƭᴇcʜιᴇ007

1
而且,只要services.exe不被劫持和替换(如今这很难做到),那么它C:\Windows\System32\services.exe便是OS所需的有效且完全正常的Windows实用程序。
Ƭᴇcʜιᴇ007

Answers:


5

我不知道从正在运行的程序(如病毒,除非它严重危害了Windows安全堆栈)来解锁工作站的任何编程方式。除了键盘上的人以外,还可以使用远程控制软件发送击键,该击键有时包含在病毒中。即使在这种情况下,攻击者仍然需要知道您的密码。

专门查找由“安全审核”来源的事件ID为4800(锁定)和4801(解锁)的事件。这些将与会话的实际锁定和解锁直接相关。其他登录/注销事件通常在后台生成,这些都是您不必要的事情。

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.