Nos últimos dias, temos recebido muitas falhas de auditoria no visualizador de eventos > segurança. Suspeito que sejam hackers tentando obter acesso ao servidor, mas eles se enquadram em 2 tipos:
Aquele em que um endereço IP está sendo capturado
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.
Nesse caso, estou adicionando esses endereços IP a uma regra de bloqueio no firewall.
O segundo tipo é assim:
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.
Onde não há endereço IP capturado. Sempre parece ser o Caller Process ID: 0x630, mas quando olho no gerenciador de tarefas nunca há um PID de 630 em processos ou serviços, mesmo mostrando processos de todos os usuários.
Ambos os tipos de falha usam nomes de usuário com erros ortográficos de administrador, nomes de usuário genéricos, como test123, convidado, fred etc, ou variações de sites que hospedamos, como no segundo exemplo,[e-mail protegido].
Não há problema em lidar com o primeiro tipo de falha, mas não tenho ideia de como abordar o segundo tipo de falha ou o que isso implica.
Eu realmente apreciaria qualquer ajuda. Desde já, obrigado.