登录类型 8 (NetworkCleartext) 的数千个 4625 登录失败错误的来源是什么？

Question

我有一个 Windows Server 2008 R2 系统，它每天在 Windows 日志的安全部分显示数千个登录类型 8 (NetworkCleartext) 的 4625 登录失败错误。源网络地址中没有列出试图获得访问权限的系统的 IP 地址，因此我构建的用于阻止经常失败的 IP 的脚本无法找到它们。

这些登录尝试可能来自哪些服务？

以下是其中之一的示例：

An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:       server-name$
    Account Domain:     example
    Logon ID:       0x3e7

Logon Type:         8

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

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

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

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

Detailed Authentication Information:
    Logon Process:      Advapi  
    Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    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.

Answer 1

有多个登录源可能会产生这些错误：

1. FTP 登录 - 检查您的 FTP 日志以查看是否同时出现登录失败。这是我的案例的来源，我花了很长时间才弄明白，这就是我发布这个的原因。
2. 通过 http 或 https 上的基本身份验证登录（简单但可能危险的密码保护网站的方法）
3. ASP脚本
4. 可能还有其他我不知道的

WindowsSecurity.com 上提到了数字 2 和 3：

此登录类型表示类似于登录类型 3 的网络登录，但密码以明文形式通过网络发送。Windows 服务器不允许使用明文身份验证连接到共享文件或打印机。我知道的唯一情况是使用 ADVAPI 从 ASP 脚本中登录，或者当用户使用 IIS 的基本身份验证模式登录到 IIS 时。在这两种情况下，事件描述中的登录过程都将列出 advapi。基本身份验证只有在未包含在 SSL 会话（即 https）中时才具有危险性。至于由 ASP 生成的登录，脚本记住在源代码中嵌入密码对于维护目的来说是一种不好的做法，并且存在恶意查看源代码从而获得密码的风险。