事件查看器中出现大量审核失败 > Windows Server 2008 R2 上的安全性

事件查看器中出现大量审核失败 > Windows Server 2008 R2 上的安全性

在过去的几天里,我们在事件查看器 > 安全性中收到大量审核失败。我怀疑他们是试图访问服务器的黑客,但他们分为两种类型:

捕获 IP 地址的情况

    An account failed to log on.

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

Logon Type:         3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:       Administrateur
    Account Domain:     FXNB

Failure Information:
    Failure Reason:     Unknown user name or bad password.
    Status:         0xc000006d
    Sub Status:     0xc0000064

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

Network Information:
    Workstation Name:   FXNB
    Source Network Address: 119.245.156.11
    Source Port:        40924

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

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

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 was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information 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.
    - 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.

在这种情况下,我会将这些 IP 地址添加到防火墙的阻止规则中。

第二种是这样的:

An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:       DEDICAT-93I3U5A$
    Account Domain:     WORKGROUP
    Logon ID:       0x3e7

Logon Type:         8

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:       [email protected]
    Account Domain:     

Failure Information:
    Failure Reason:     Unknown user name or bad password.
    Status:         0xc000006d
    Sub Status:     0xc0000064

Process Information:
    Caller Process ID:  0x630
    Caller Process Name:    C:\Windows\System32\svchost.exe

Network Information:
    Workstation Name:   DEDICAT-93I3U5A
    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 request fails. It is generated on the computer where access was attempted.

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 was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information 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.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.

未捕获 IP 地址。它似乎始终是调用方进程 ID:0x630,但当我在任务管理器下查看时,进程或服务下从未出现 630 的 PID,甚至显示来自所有用户的进程。

两种类型的失败都使用错误的管理员用户名、通用用户名(如 test123、guest、fred 等)或我们托管的网站的变体(如第二个示例所示)。[电子邮件保护]

我可以处理第一种类型的失败,但我不知道如何处理第二种类型的失败或它意味着什么。

非常感谢您的帮助。提前致谢。

相关内容