За последние несколько дней мы получили множество сбоев аудита в безопасности средства просмотра событий. Я подозреваю, что они хакеры пытаются получить доступ к серверу, но они делятся на 2 типа:
Тот, где 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: test@casamiadumfries.com
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-адрес. Кажется, что это всегда Идентификатор процесса вызывающего абонента: 0x630, но когда я смотрю в диспетчере задач, там никогда не бывает PID 630 для процессов или служб, даже показывая процессы всех пользователей.
В обоих типах сбоев используются имена пользователей, которые являются либо неправильным написанием имени администратора, общих имен пользователей, таких как test123, guest, fred и т.д., Либо разновидностями веб-сайтов, которые мы размещаем, как во втором примере, test@casamiadumfries.com.
Я хорошо справляюсь с первым типом неудачи, но я не знаю, как подходить ко второму типу неудачи или что это подразумевает.
Был бы очень признателен за любую помощь на всех. Заранее спасибо.