«просмотр событий» — история выключений
События связанные с выключениями системы (включая дату и время) могут быть просмотрены с помощью программы «Просмотр событий».
Запустить «Просмотр событий» и найти события связанные с выключениями:
- Нажмите клавишу
Win, наберите
eventvwr и запустите
Просмотрсобытий - В панели слева разверните
ЖурналыWindows и перейдите в
Система - Щелкните правой кнопкой мыши на
Система и выберите
Фильтртекущегожурнала... - Введите следующие коды в поле
<Всекодысобытий> и нажмите
OK:41,1074,1076,6005,6006,6008,6009,6013
Анализ журнала ошибок
После того как «Просмотр событий» будет запущен, вы увидите на экране следующее окно.
В левой его части находится древовидная система с разделами. Нас интересует вкладка «Журналы Windows». Нажмите на ее названии один раз ЛКМ. В результате вы увидите список вложенных подразделов и общую статистику в центральной части окна.
Для дальнейшего анализа необходимо зайти в подраздел «Система». В нем находится большой список событий, которые ранее происходили на компьютере. Всего можно выделить четыре типа событий: критическое, ошибка, предупреждение и сведения. Мы вкратце расскажем вам о каждом из них.
Критическое событие
Данное событие помечено в журнале красным кругом с крестиком внутри и соответствующей припиской. Кликнув по названию такой ошибки из списка, немного ниже вы сможете увидеть общие сведения происшествия.
Зачастую представленной информации достаточно для того, чтобы найти решение проблемы. В данном примере система сообщает о том, что компьютер был резко выключен. Для того чтобы ошибка не появлялась вновь, достаточно просто корректно выключать ПК.
Подробнее: Выключение системы Windows 10
Для более продвинутого пользователя есть специальная вкладка «Подробности», где все событие представлены с кодами ошибок и последовательно расписаны.
Ошибка
Этот тип событий второй по важности. Каждая ошибка помечена в журнале красным кругом с восклицательным знаком. Как и в случае с критическим событием, достаточно нажать ЛКМ по названию ошибки для просмотра подробностей.
Если из сообщения в поле «Общие» вы ничего не поняли, можно попробовать найти информацию об ошибке в сети. Для этого используйте название источника и код события. Они указаны в соответствующих графах напротив названия самой ошибки. Для решения проблемы в нашем случае необходимо попросту повторно инсталлировать обновление с нужным номером.
Подробнее: Устанавливаем обновления для Windows 10 вручную
Предупреждение
Сообщения данного типа возникают в тех ситуациях, когда проблема не носит серьезный характер. В большинстве случаев их можно игнорировать, но если событие повторяется раз за разом, стоит уделить ему внимание.
Чаще всего причиной появления предупреждения служит DNS-сервер, вернее, неудачная попытка какой-либо программы подключиться к нему. В таких ситуациях софт или утилита попросту обращается к запасному адресу.
Сведения
Этот тип событий самый безобидный и создан лишь для того, чтобы вы могли быть в курсе всего происходящего. Как понятно из его названия, в сообщение содержатся сводные данные о всех инсталлированных обновлениях и программах, созданных точках восстановления и т.д.
Подобная информация будет очень кстати для тех пользователей, которые не хотят устанавливать сторонний софт для просмотра последних действий Windows 10.
Как видите, процесс активации, запуска и анализа журнала ошибок очень прост и не требует от вас глубоких познаний ПК. Помните, что таким образом можно узнать информацию не только о системе, но и о других ее компонентах. Для этого достаточно в утилите «Просмотр событий» выбрать другой раздел.
Включение логирования
Для того чтобы система могла записывать все события в журнал, необходимо включить его. Для этого выполните следующие действия:
- Нажмите в любом пустом месте «Панели задач» правой кнопкой мышки. Из контекстного меню выберите пункт «Диспетчер задач».
- В открывшемся окне перейдите во вкладку «Службы», а затем на самой странице в самом низу нажмите кнопку «Открыть службы».
- Далее в перечне служб нужно найти «Журнал событий Windows». Убедитесь, что она запущена и работает в автоматическом режиме. Об этом должны свидетельствовать надписи в графах «Состояние» и «Тип запуска».
- Если значение указанных строк отличается от тех, что вы видите на скриншоте выше, откройте окно редактора службы. Для этого кликните два раза левой кнопкой мыши на ее названии. Затем переключите «Тип запуска» в режим «Автоматически», и активируйте саму службу путем нажатия кнопки «Запустить». Для подтверждения нажмите «OK».
После этого остается проверить, активирован ли на компьютере файл подкачки. Дело в том, что при его выключении система попросту не сможет вести учет всех событий. Поэтому очень важно установить значение виртуальной памяти хотя бы 200 Мб. Об этом напоминает сама Windows 10 в сообщении, которое возникает при полной деактивации файла подкачки.
О том, как задействовать виртуальную память и изменить ее размер, мы уже писали ранее в отдельной статье. Ознакомьтесь с ней при необходимости.
Подробнее: Включение файла подкачки на компьютере с Windows 10
С включением логирования разобрались. Теперь двигаемся дальше.
Политики аудита windows
Пройдем последовательно по настройкам, эффективным для решения задач аудита ИБ и выработки целостной политики аудита безопасности.
Категория аудита | Подкатегория аудита | События аудита | EventID | Комментарии |
Вход учетной записи | Аудит проверки учетных данных | Успех, Отказ | 4776 | Целесообразно контролировать на домен-контроллерах при использовании NTLM-аутентификации. |
Аудит службы проверки подлинности Kerberos | Успех, Отказ | 4771 | Неуспешная аутентификация учетной записи на контроллере домена с использованием Kerberos-аутентификации. | |
4768 | Запрос билета Kerberos, при этом следует анализировать коды ответа сервера. | |||
Примечание: Данный тип аудита следует включать на контроллерах домена, при этом для детального изучения попыток подключения и получения IP-адреса подключающегося устройства на контроллере домена следует выполнить команду nltest /dbflag:2080ffff и проводить аудит текстового лог-файла %windir%debugnetlogon.log | ||||
Управление учетными записями | Аудит управления учетными записями компьютеров | Успех | 4741 | Заведение устройства в домен Active Directory; может использоваться злоумышленниками, поскольку любой пользователь домена по умолчанию может завести в домен 10 устройств, на которых может быть установлено неконтролируемое компанией ПО, в том числе вредоносное. |
Аудит управления группами безопасности | Успех, Отказ | 4728 | Добавление члена глобальной группы. | |
4732 | Добавление члена локальной группы. | |||
4756 | Добавление члена универсальной группы. | |||
Аудит управления учетными записями пользователей | Успех, Отказ | 4720 | Создание учетной записи. | |
4725 | Отключение учетной записи. | |||
4740 | Блокировка учетной записи. | |||
4723 | Смена пароля. | |||
4724 | Сброс пароля. | |||
Подробное отслеживание | Аудит создания процессов | Успех | 4688 | При создании процесса. |
4689 | При завершении процесса. | |||
Примечание: Чтобы для командного интерпретатора велась запись введенных команд, следует включить политику «Конфигурация компьютера — Конфигурация Windows — Административные шаблоны — Система — Аудит создания процессов -> Включать командную строку в события создания процессов». Примечание: Чтобы велась запись выполняемых PowerShell-команд и загруженных PowerShell-модулей, следует включить в каталоге «Конфигурация компьютера — Конфигурация Windows — Административные шаблоны — Компоненты Windows — Windows PowerShell» политики «Включить ведение журнала модулей» (в настройках политики указать все модули символом «*») и «Включить регистрацию блоков сценариев PowerShell» (в настройках политики отметить check-box «Регистрация начала или остановки вызова блоков сценариев»). Работа PowerShell-скриптов регистрируется с EventID=4104,4105,4106 в журнале Microsoft-Windows-PowerShell/Operational, а загрузка PowerShell-модулей регистрируется с EventID=800 в журнале Windows PowerShell. | ||||
Вход/выход | Аудит выхода из системы | Успех | 4634 | Для неинтерактивных сессий. |
4647 | Для интерактивных сессий и RDP-подключений. | |||
Примечание: При этом следует обращать внимание на код Logon Type, который показывает тип подключения (интерактивное, сетевое, с закэшированными учетными данными, с предоставлением учетных данных в открытом виде и т.д.). | ||||
Аудит входа в систему | Успех, Отказ | 4624 | При успешной попытке аутентификации, создается на локальном ПК и на домен-контроллере при использовании NTLM и Kerberos-аутентификации. | |
4625 | При неуспешной попытке аутентификации, создается на локальном ПК и на домен-контроллере при использовании NTLM аутентификации; при Kerberos-аутентификации на контроллере домена создается EventID=4771. | |||
4648 | При попытке входа с явным указанием учетных данных, например, при выполнении команды runas, а также при работе «хакерской» утилиты Mimikatz. | |||
Примечание: При этом следует обращать внимание на код входа (Logon Type), который показывает тип подключения (интерактивное, сетевое, с закэшированными учетными данными, с предоставлением учетных данных в открытом виде и т.д.). Целесообразно также обращать внимание на код ошибки (Status/SubStatus), который также сохраняется в событии аудита и характеризует причину неуспешного входа — несуществующее имя учетной записи, недействительный пароль, попытка входа с заблокированной учетной записью и т.д. | ||||
Аудит других событий входа и выхода | Успех, Отказ | 4778 | RDP-подключение было установлено. | |
4779 | RDP-подключение было разорвано. | |||
Аудит специального входа | Успех | 4672 | При входе с административными полномочиями. | |
Доступ к объектам | Аудит сведений об общем файловом ресурсе | Успех, Отказ | 5145 | При доступе к системных сетевым ресурсам, таким как \C$ . Данное событие будет создаваться при работе ransomware, нацеленного на горизонтальное перемещение по сети. |
Аудит других событий доступа к объектам | Успех, Отказ | 4698 | При создании задания в «Планировщике задач», что часто используется злоумышленниками как метод закрепления и скрытия активности в атакованной системе. | |
Изменение политики | Аудит изменения политики аудита | Успех | 4719 | Изменение политики аудита. |
4906 | Изменение настройки CrashOnAuditFail. | |||
Примечание: Изменить реакцию ОС на невозможность вести журнал аудита безопасности (настройка CrashOnAuditFail) можно в каталоге «Конфигурация компьютера — Конфигурация Windows — Параметры безопасности — Локальные политики — Параметры безопасности» в политике «Аудит: немедленное отключение системы, если невозможно внести в журнал записи об аудите безопасности». | ||||
Система | Аудит расширения системы безопасности | Успех | 4610 4614 4622 | При появлении в системе новых пакетов аутентификации, что не должно происходить несанкционированно. |
4697 | При создании нового сервиса, что часто используется злоумышленниками как метод закрепления и скрытия активности в атакованной системе. | |||
Кроме описанных выше настроек, имеет смысл также контролировать появление в журнале безопасности события с EventID=1102, которое формируется сразу после очистки журнала безопасности, что может говорить о вредоносной активности. Более того, разумно будет включить в каталоге «Конфигурация компьютера — Конфигурация Windows — Параметры безопасности — Локальные политики — Параметры безопасности» политику «Сетевая безопасность:
ограничения NTLM: исходящий трафик NTLM к удаленным серверам» в значение «Аудит всего». После этого EventID=8001 в журнале Microsoft-Windows-NTLM/Operational будет содержать информацию об автоматической аутентификации на веб-ресурсах с учетной записью пользователя.
Следующим шагом станет allow list с перечнем веб-ресурсов, которые легитимно могут запрашивать учетные записи, а указанную политику можно будет перевести в режим блокировки. Это не позволит вредоносным ресурсам получать NTLM-хэши пользователей, которые кликнули на ссылку из фишингового письма.
Обратим внимание и на то, что подсистема журналирования Windows весьма гибка и позволяет настроить аудит произвольных папок и веток реестра — следует лишь выбрать критичные для ИТ-инфраструктуры объекты аудита и включить данные опции.
Работа с журналами
Службы и приложения могут генерировать огромное количество самых разнообразных событий. Для простоты доступа к нужным записям журнала можно использовать функцию фильтрации журнала:
Правый клик по журналу – Фильтр текущего журнала… (>Filter Current Log…), либо выбрать данную функцию в панели быстрых действий. Открывшееся окно позволяет настроить фильтр и отобразить только те события, которые необходимы в данный момент:
Можно задать временной период, уровни события, выбрать журналы и конкретные источники событий. Если известны коды событий, которые нужно включить или исключить из фильтра, их также можно указать.
Когда необходимость в фильтрации событий отпадет, ее можно отключить действием Очистить фильтр (Clear Filter):
Приложение Просмотр событий (Event Viewer) позволяет также настроить дополнительные свойства журналов. Доступ к настройкам можно получить через панель быстрых действий, либо через контекстное меню журнала – правый клик по журналу – Свойства (Properties):
В открывшемся окне настроек можно увидеть путь, по которому сохраняется файл журнала, текущий размер, а также можно задать максимальный размер файла:
В нижней части окна можно выбрать вариант действия при достижении журналом максимального значения:
- Переписывать события при необходимости (Overwrite events as needed) – новое событие будет записываться поверх самого старого события в журнале, таким образом будут доступны события только за определенный диапазон времени.
- Архивировать журнал при заполнении (Overwrite the log when full) – заполненный журнал будет сохранен, последующие события будут записываться в новый файл журнала. При необходимости доступа к старым событиям, архивный файл можно будет открыть в приложении Просмотр событий (Event Viewer).
- Не переписывать события (Do not overwrite events) – при заполнении журнала выдается системное сообщение о необходимости очистить журнал, старые события не перезаписываются.
Appendix l: events to monitor
The following table lists events that you should monitor in your environment, according to the recommendations provided in Monitoring Active Directory for Signs of Compromise. In the following table, the “Current Windows Event ID” column lists the event ID as it is implemented in versions of Windows and Windows Server that are currently in mainstream support.
The “Legacy Windows Event ID” column lists the corresponding event ID in legacy versions of Windows such as client computers running Windows XP or earlier and servers running Windows Server 2003 or earlier. The “Potential Criticality” column identifies whether the event should be considered of low, medium, or high criticality in detecting attacks, and the “Event Summary” column provides a brief description of the event.
A potential criticality of High means that one occurrence of the event should be investigated. Potential criticality of Medium or Low means that these events should only be investigated if they occur unexpectedly or in numbers that significantly exceed the expected baseline in a measured period of time.
All organizations should test these recommendations in their environments before creating alerts that require mandatory investigative responses. Every environment is different, and some of the events ranked with a potential criticality of High may occur due to other harmless events.
| Current Windows Event ID | Legacy Windows Event ID | Potential Criticality | Event Summary |
|---|---|---|---|
| 4618 | N/A | High | A monitored security event pattern has occurred. |
| 4649 | N/A | High | A replay attack was detected. May be a harmless false positive due to misconfiguration error. |
| 4719 | 612 | High | System audit policy was changed. |
| 4765 | N/A | High | SID History was added to an account. |
| 4766 | N/A | High | An attempt to add SID History to an account failed. |
| 4794 | N/A | High | An attempt was made to set the Directory Services Restore Mode. |
| 4897 | 801 | High | Role separation enabled: |
| 4964 | N/A | High | Special groups have been assigned to a new logon. |
| 5124 | N/A | High | A security setting was updated on the OCSP Responder Service |
| N/A | 550 | Medium to High | Possible denial-of-service (DoS) attack |
| 1102 | 517 | Medium to High | The audit log was cleared |
| 4621 | N/A | Medium | Administrator recovered system from CrashOnAuditFail. Users who are not administrators will now be allowed to log on. Some auditable activity might not have been recorded. |
| 4675 | N/A | Medium | SIDs were filtered. |
| 4692 | N/A | Medium | Backup of data protection master key was attempted. |
| 4693 | N/A | Medium | Recovery of data protection master key was attempted. |
| 4706 | 610 | Medium | A new trust was created to a domain. |
| 4713 | 617 | Medium | Kerberos policy was changed. |
| 4714 | 618 | Medium | Encrypted data recovery policy was changed. |
| 4715 | N/A | Medium | The audit policy (SACL) on an object was changed. |
| 4716 | 620 | Medium | Trusted domain information was modified. |
| 4724 | 628 | Medium | An attempt was made to reset an account’s password. |
| 4727 | 631 | Medium | A security-enabled global group was created. |
| 4735 | 639 | Medium | A security-enabled local group was changed. |
| 4737 | 641 | Medium | A security-enabled global group was changed. |
| 4739 | 643 | Medium | Domain Policy was changed. |
| 4754 | 658 | Medium | A security-enabled universal group was created. |
| 4755 | 659 | Medium | A security-enabled universal group was changed. |
| 4764 | 667 | Medium | A security-disabled group was deleted |
| 4764 | 668 | Medium | A group’s type was changed. |
| 4780 | 684 | Medium | The ACL was set on accounts which are members of administrators groups. |
| 4816 | N/A | Medium | RPC detected an integrity violation while decrypting an incoming message. |
| 4865 | N/A | Medium | A trusted forest information entry was added. |
| 4866 | N/A | Medium | A trusted forest information entry was removed. |
| 4867 | N/A | Medium | A trusted forest information entry was modified. |
| 4868 | 772 | Medium | The certificate manager denied a pending certificate request. |
| 4870 | 774 | Medium | Certificate Services revoked a certificate. |
| 4882 | 786 | Medium | The security permissions for Certificate Services changed. |
| 4885 | 789 | Medium | The audit filter for Certificate Services changed. |
| 4890 | 794 | Medium | The certificate manager settings for Certificate Services changed. |
| 4892 | 796 | Medium | A property of Certificate Services changed. |
| 4896 | 800 | Medium | One or more rows have been deleted from the certificate database. |
| 4906 | N/A | Medium | The CrashOnAuditFail value has changed. |
| 4907 | N/A | Medium | Auditing settings on object were changed. |
| 4908 | N/A | Medium | Special Groups Logon table modified. |
| 4912 | 807 | Medium | Per User Audit Policy was changed. |
| 4960 | N/A | Medium | IPsec dropped an inbound packet that failed an integrity check. If this problem persists, it could indicate a network issue or that packets are being modified in transit to this computer. Verify that the packets sent from the remote computer are the same as those received by this computer. This error might also indicate interoperability problems with other IPsec implementations. |
| 4961 | N/A | Medium | IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer. |
| 4962 | N/A | Medium | IPsec dropped an inbound packet that failed a replay check. The inbound packet had too low a sequence number to ensure it was not a replay. |
| 4963 | N/A | Medium | IPsec dropped an inbound clear text packet that should have been secured. This is usually due to the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt. |
| 4965 | N/A | Medium | IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by malfunctioning hardware that is corrupting packets. If these errors persist, verify that the packets sent from the remote computer are the same as those received by this computer. This error may also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored. |
| 4976 | N/A | Medium | During Main Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation. |
| 4977 | N/A | Medium | During Quick Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation. |
| 4978 | N/A | Medium | During Extended Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation. |
| 4983 | N/A | Medium | An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted. |
| 4984 | N/A | Medium | An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted. |
| 5027 | N/A | Medium | The Windows Firewall Service was unable to retrieve the security policy from the local storage. The service will continue enforcing the current policy. |
| 5028 | N/A | Medium | The Windows Firewall Service was unable to parse the new security policy. The service will continue with currently enforced policy. |
| 5029 | N/A | Medium | The Windows Firewall Service failed to initialize the driver. The service will continue to enforce the current policy. |
| 5030 | N/A | Medium | The Windows Firewall Service failed to start. |
| 5035 | N/A | Medium | The Windows Firewall Driver failed to start. |
| 5037 | N/A | Medium | The Windows Firewall Driver detected critical runtime error. Terminating. |
| 5038 | N/A | Medium | Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error. |
| 5120 | N/A | Medium | OCSP Responder Service Started |
| 5121 | N/A | Medium | OCSP Responder Service Stopped |
| 5122 | N/A | Medium | A configuration entry changed in OCSP Responder Service |
| 5123 | N/A | Medium | A configuration entry changed in OCSP Responder Service |
| 5376 | N/A | Medium | Credential Manager credentials were backed up. |
| 5377 | N/A | Medium | Credential Manager credentials were restored from a backup. |
| 5453 | N/A | Medium | An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started. |
| 5480 | N/A | Medium | IPsec Services failed to get the complete list of network interfaces on the computer. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem. |
| 5483 | N/A | Medium | IPsec Services failed to initialize RPC server. IPsec Services could not be started. |
| 5484 | N/A | Medium | IPsec Services has experienced a critical failure and has been shut down. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks. |
| 5485 | N/A | Medium | IPsec Services failed to process some IPsec filters on a plug-and-play event for network interfaces. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem. |
| 6145 | N/A | Medium | One or more errors occurred while processing security policy in the Group Policy objects. |
| 6273 | N/A | Medium | Network Policy Server denied access to a user. |
| 6274 | N/A | Medium | Network Policy Server discarded the request for a user. |
| 6275 | N/A | Medium | Network Policy Server discarded the accounting request for a user. |
| 6276 | N/A | Medium | Network Policy Server quarantined a user. |
| 6277 | N/A | Medium | Network Policy Server granted access to a user but put it on probation because the host did not meet the defined health policy. |
| 6278 | N/A | Medium | Network Policy Server granted full access to a user because the host met the defined health policy. |
| 6279 | N/A | Medium | Network Policy Server locked the user account due to repeated failed authentication attempts. |
| 6280 | N/A | Medium | Network Policy Server unlocked the user account. |
| – | 640 | Medium | General account database changed |
| – | 619 | Medium | Quality of Service Policy changed |
| 24586 | N/A | Medium | An error was encountered converting volume |
| 24592 | N/A | Medium | An attempt to automatically restart conversion on volume %2 failed. |
| 24593 | N/A | Medium | Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume |
| 24594 | N/A | Medium | Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume. |
| 4608 | 512 | Low | Windows is starting up. |
| 4609 | 513 | Low | Windows is shutting down. |
| 4610 | 514 | Low | An authentication package has been loaded by the Local Security Authority. |
| 4611 | 515 | Low | A trusted logon process has been registered with the Local Security Authority. |
| 4612 | 516 | Low | Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits. |
| 4614 | 518 | Low | A notification package has been loaded by the Security Account Manager. |
| 4615 | 519 | Low | Invalid use of LPC port. |
| 4616 | 520 | Low | The system time was changed. |
| 4622 | N/A | Low | A security package has been loaded by the Local Security Authority. |
| 4624 | 528,540 | Low | An account was successfully logged on. |
| 4625 | 529-537,539 | Low | An account failed to log on. |
| 4634 | 538 | Low | An account was logged off. |
| 4646 | N/A | Low | IKE DoS-prevention mode started. |
| 4647 | 551 | Low | User initiated logoff. |
| 4648 | 552 | Low | A logon was attempted using explicit credentials. |
| 4650 | N/A | Low | An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used. |
| 4651 | N/A | Low | An IPsec Main Mode security association was established. Extended Mode was not enabled. A certificate was used for authentication. |
| 4652 | N/A | Low | An IPsec Main Mode negotiation failed. |
| 4653 | N/A | Low | An IPsec Main Mode negotiation failed. |
| 4654 | N/A | Low | An IPsec Quick Mode negotiation failed. |
| 4655 | N/A | Low | An IPsec Main Mode security association ended. |
| 4656 | 560 | Low | A handle to an object was requested. |
| 4657 | 567 | Low | A registry value was modified. |
| 4658 | 562 | Low | The handle to an object was closed. |
| 4659 | N/A | Low | A handle to an object was requested with intent to delete. |
| 4660 | 564 | Low | An object was deleted. |
| 4661 | 565 | Low | A handle to an object was requested. |
| 4662 | 566 | Low | An operation was performed on an object. |
| 4663 | 567 | Low | An attempt was made to access an object. |
| 4664 | N/A | Low | An attempt was made to create a hard link. |
| 4665 | N/A | Low | An attempt was made to create an application client context. |
| 4666 | N/A | Low | An application attempted an operation: |
| 4667 | N/A | Low | An application client context was deleted. |
| 4668 | N/A | Low | An application was initialized. |
| 4670 | N/A | Low | Permissions on an object were changed. |
| 4671 | N/A | Low | An application attempted to access a blocked ordinal through the TBS. |
| 4672 | 576 | Low | Special privileges assigned to new logon. |
| 4673 | 577 | Low | A privileged service was called. |
| 4674 | 578 | Low | An operation was attempted on a privileged object. |
| 4688 | 592 | Low | A new process has been created. |
| 4689 | 593 | Low | A process has exited. |
| 4690 | 594 | Low | An attempt was made to duplicate a handle to an object. |
| 4691 | 595 | Low | Indirect access to an object was requested. |
| 4694 | N/A | Low | Protection of auditable protected data was attempted. |
| 4695 | N/A | Low | Unprotection of auditable protected data was attempted. |
| 4696 | 600 | Low | A primary token was assigned to process. |
| 4697 | 601 | Low | Attempt to install a service |
| 4698 | 602 | Low | A scheduled task was created. |
| 4699 | 602 | Low | A scheduled task was deleted. |
| 4700 | 602 | Low | A scheduled task was enabled. |
| 4701 | 602 | Low | A scheduled task was disabled. |
| 4702 | 602 | Low | A scheduled task was updated. |
| 4704 | 608 | Low | A user right was assigned. |
| 4705 | 609 | Low | A user right was removed. |
| 4707 | 611 | Low | A trust to a domain was removed. |
| 4709 | N/A | Low | IPsec Services was started. |
| 4710 | N/A | Low | IPsec Services was disabled. |
| 4711 | N/A | Low | May contain any one of the following: PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer. PAStore Engine applied Active Directory storage IPsec policy on the computer. PAStore Engine applied local registry storage IPsec policy on the computer. PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer. PAStore Engine failed to apply Active Directory storage IPsec policy on the computer. PAStore Engine failed to apply local registry storage IPsec policy on the computer. PAStore Engine failed to apply some rules of the active IPsec policy on the computer. PAStore Engine failed to load directory storage IPsec policy on the computer. PAStore Engine loaded directory storage IPsec policy on the computer. PAStore Engine failed to load local storage IPsec policy on the computer. PAStore Engine loaded local storage IPsec policy on the computer.PAStore Engine polled for changes to the active IPsec policy and detected no changes. |
| 4712 | N/A | Low | IPsec Services encountered a potentially serious failure. |
| 4717 | 621 | Low | System security access was granted to an account. |
| 4718 | 622 | Low | System security access was removed from an account. |
| 4720 | 624 | Low | A user account was created. |
| 4722 | 626 | Low | A user account was enabled. |
| 4723 | 627 | Low | An attempt was made to change an account’s password. |
| 4725 | 629 | Low | A user account was disabled. |
| 4726 | 630 | Low | A user account was deleted. |
| 4728 | 632 | Low | A member was added to a security-enabled global group. |
| 4729 | 633 | Low | A member was removed from a security-enabled global group. |
| 4730 | 634 | Low | A security-enabled global group was deleted. |
| 4731 | 635 | Low | A security-enabled local group was created. |
| 4732 | 636 | Low | A member was added to a security-enabled local group. |
| 4733 | 637 | Low | A member was removed from a security-enabled local group. |
| 4734 | 638 | Low | A security-enabled local group was deleted. |
| 4738 | 642 | Low | A user account was changed. |
| 4740 | 644 | Low | A user account was locked out. |
| 4741 | 645 | Low | A computer account was changed. |
| 4742 | 646 | Low | A computer account was changed. |
| 4743 | 647 | Low | A computer account was deleted. |
| 4744 | 648 | Low | A security-disabled local group was created. |
| 4745 | 649 | Low | A security-disabled local group was changed. |
| 4746 | 650 | Low | A member was added to a security-disabled local group. |
| 4747 | 651 | Low | A member was removed from a security-disabled local group. |
| 4748 | 652 | Low | A security-disabled local group was deleted. |
| 4749 | 653 | Low | A security-disabled global group was created. |
| 4750 | 654 | Low | A security-disabled global group was changed. |
| 4751 | 655 | Low | A member was added to a security-disabled global group. |
| 4752 | 656 | Low | A member was removed from a security-disabled global group. |
| 4753 | 657 | Low | A security-disabled global group was deleted. |
| 4756 | 660 | Low | A member was added to a security-enabled universal group. |
| 4757 | 661 | Low | A member was removed from a security-enabled universal group. |
| 4758 | 662 | Low | A security-enabled universal group was deleted. |
| 4759 | 663 | Low | A security-disabled universal group was created. |
| 4760 | 664 | Low | A security-disabled universal group was changed. |
| 4761 | 665 | Low | A member was added to a security-disabled universal group. |
| 4762 | 666 | Low | A member was removed from a security-disabled universal group. |
| 4767 | 671 | Low | A user account was unlocked. |
| 4768 | 672,676 | Low | A Kerberos authentication ticket (TGT) was requested. |
| 4769 | 673 | Low | A Kerberos service ticket was requested. |
| 4770 | 674 | Low | A Kerberos service ticket was renewed. |
| 4771 | 675 | Low | Kerberos pre-authentication failed. |
| 4772 | 672 | Low | A Kerberos authentication ticket request failed. |
| 4774 | 678 | Low | An account was mapped for logon. |
| 4775 | 679 | Low | An account could not be mapped for logon. |
| 4776 | 680,681 | Low | The domain controller attempted to validate the credentials for an account. |
| 4777 | N/A | Low | The domain controller failed to validate the credentials for an account. |
| 4778 | 682 | Low | A session was reconnected to a Window Station. |
| 4779 | 683 | Low | A session was disconnected from a Window Station. |
| 4781 | 685 | Low | The name of an account was changed: |
| 4782 | N/A | Low | The password hash an account was accessed. |
| 4783 | 667 | Low | A basic application group was created. |
| 4784 | N/A | Low | A basic application group was changed. |
| 4785 | 689 | Low | A member was added to a basic application group. |
| 4786 | 690 | Low | A member was removed from a basic application group. |
| 4787 | 691 | Low | A nonmember was added to a basic application group. |
| 4788 | 692 | Low | A nonmember was removed from a basic application group. |
| 4789 | 693 | Low | A basic application group was deleted. |
| 4790 | 694 | Low | An LDAP query group was created. |
| 4793 | N/A | Low | The Password Policy Checking API was called. |
| 4800 | N/A | Low | The workstation was locked. |
| 4801 | N/A | Low | The workstation was unlocked. |
| 4802 | N/A | Low | The screen saver was invoked. |
| 4803 | N/A | Low | The screen saver was dismissed. |
| 4864 | N/A | Low | A namespace collision was detected. |
| 4869 | 773 | Low | Certificate Services received a resubmitted certificate request. |
| 4871 | 775 | Low | Certificate Services received a request to publish the certificate revocation list (CRL). |
| 4872 | 776 | Low | Certificate Services published the certificate revocation list (CRL). |
| 4873 | 777 | Low | A certificate request extension changed. |
| 4874 | 778 | Low | One or more certificate request attributes changed. |
| 4875 | 779 | Low | Certificate Services received a request to shut down. |
| 4876 | 780 | Low | Certificate Services backup started. |
| 4877 | 781 | Low | Certificate Services backup completed. |
| 4878 | 782 | Low | Certificate Services restore started. |
| 4879 | 783 | Low | Certificate Services restore completed. |
| 4880 | 784 | Low | Certificate Services started. |
| 4881 | 785 | Low | Certificate Services stopped. |
| 4883 | 787 | Low | Certificate Services retrieved an archived key. |
| 4884 | 788 | Low | Certificate Services imported a certificate into its database. |
| 4886 | 790 | Low | Certificate Services received a certificate request. |
| 4887 | 791 | Low | Certificate Services approved a certificate request and issued a certificate. |
| 4888 | 792 | Low | Certificate Services denied a certificate request. |
| 4889 | 793 | Low | Certificate Services set the status of a certificate request to pending. |
| 4891 | 795 | Low | A configuration entry changed in Certificate Services. |
| 4893 | 797 | Low | Certificate Services archived a key. |
| 4894 | 798 | Low | Certificate Services imported and archived a key. |
| 4895 | 799 | Low | Certificate Services published the CA certificate to Active Directory Domain Services. |
| 4898 | 802 | Low | Certificate Services loaded a template. |
| 4902 | N/A | Low | The Per-user audit policy table was created. |
| 4904 | N/A | Low | An attempt was made to register a security event source. |
| 4905 | N/A | Low | An attempt was made to unregister a security event source. |
| 4909 | N/A | Low | The local policy settings for the TBS were changed. |
| 4910 | N/A | Low | The Group Policy settings for the TBS were changed. |
| 4928 | N/A | Low | An Active Directory replica source naming context was established. |
| 4929 | N/A | Low | An Active Directory replica source naming context was removed. |
| 4930 | N/A | Low | An Active Directory replica source naming context was modified. |
| 4931 | N/A | Low | An Active Directory replica destination naming context was modified. |
| 4932 | N/A | Low | Synchronization of a replica of an Active Directory naming context has begun. |
| 4933 | N/A | Low | Synchronization of a replica of an Active Directory naming context has ended. |
| 4934 | N/A | Low | Attributes of an Active Directory object were replicated. |
| 4935 | N/A | Low | Replication failure begins. |
| 4936 | N/A | Low | Replication failure ends. |
| 4937 | N/A | Low | A lingering object was removed from a replica. |
| 4944 | N/A | Low | The following policy was active when the Windows Firewall started. |
| 4945 | N/A | Low | A rule was listed when the Windows Firewall started. |
| 4946 | N/A | Low | A change has been made to Windows Firewall exception list. A rule was added. |
| 4947 | N/A | Low | A change has been made to Windows Firewall exception list. A rule was modified. |
| 4948 | N/A | Low | A change has been made to Windows Firewall exception list. A rule was deleted. |
| 4949 | N/A | Low | Windows Firewall settings were restored to the default values. |
| 4950 | N/A | Low | A Windows Firewall setting has changed. |
| 4951 | N/A | Low | A rule has been ignored because its major version number was not recognized by Windows Firewall. |
| 4952 | N/A | Low | Parts of a rule have been ignored because its minor version number was not recognized by Windows Firewall. The other parts of the rule will be enforced. |
| 4953 | N/A | Low | A rule has been ignored by Windows Firewall because it could not parse the rule. |
| 4954 | N/A | Low | Windows Firewall Group Policy settings have changed. The new settings have been applied. |
| 4956 | N/A | Low | Windows Firewall has changed the active profile. |
| 4957 | N/A | Low | Windows Firewall did not apply the following rule: |
| 4958 | N/A | Low | Windows Firewall did not apply the following rule because the rule referred to items not configured on this computer: |
| 4979 | N/A | Low | IPsec Main Mode and Extended Mode security associations were established. |
| 4980 | N/A | Low | IPsec Main Mode and Extended Mode security associations were established. |
| 4981 | N/A | Low | IPsec Main Mode and Extended Mode security associations were established. |
| 4982 | N/A | Low | IPsec Main Mode and Extended Mode security associations were established. |
| 4985 | N/A | Low | The state of a transaction has changed. |
| 5024 | N/A | Low | The Windows Firewall Service has started successfully. |
| 5025 | N/A | Low | The Windows Firewall Service has been stopped. |
| 5031 | N/A | Low | The Windows Firewall Service blocked an application from accepting incoming connections on the network. |
| 5032 | N/A | Low | Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network. |
| 5033 | N/A | Low | The Windows Firewall Driver has started successfully. |
| 5034 | N/A | Low | The Windows Firewall Driver has been stopped. |
| 5039 | N/A | Low | A registry key was virtualized. |
| 5040 | N/A | Low | A change has been made to IPsec settings. An Authentication Set was added. |
| 5041 | N/A | Low | A change has been made to IPsec settings. An Authentication Set was modified. |
| 5042 | N/A | Low | A change has been made to IPsec settings. An Authentication Set was deleted. |
| 5043 | N/A | Low | A change has been made to IPsec settings. A Connection Security Rule was added. |
| 5044 | N/A | Low | A change has been made to IPsec settings. A Connection Security Rule was modified. |
| 5045 | N/A | Low | A change has been made to IPsec settings. A Connection Security Rule was deleted. |
| 5046 | N/A | Low | A change has been made to IPsec settings. A Crypto Set was added. |
| 5047 | N/A | Low | A change has been made to IPsec settings. A Crypto Set was modified. |
| 5048 | N/A | Low | A change has been made to IPsec settings. A Crypto Set was deleted. |
| 5050 | N/A | Low | An attempt to programmatically disable the Windows Firewall using a call to InetFwProfile.FirewallEnabled(False) |
| 5051 | N/A | Low | A file was virtualized. |
| 5056 | N/A | Low | A cryptographic self test was performed. |
| 5057 | N/A | Low | A cryptographic primitive operation failed. |
| 5058 | N/A | Low | Key file operation. |
| 5059 | N/A | Low | Key migration operation. |
| 5060 | N/A | Low | Verification operation failed. |
| 5061 | N/A | Low | Cryptographic operation. |
| 5062 | N/A | Low | A kernel-mode cryptographic self test was performed. |
| 5063 | N/A | Low | A cryptographic provider operation was attempted. |
| 5064 | N/A | Low | A cryptographic context operation was attempted. |
| 5065 | N/A | Low | A cryptographic context modification was attempted. |
| 5066 | N/A | Low | A cryptographic function operation was attempted. |
| 5067 | N/A | Low | A cryptographic function modification was attempted. |
| 5068 | N/A | Low | A cryptographic function provider operation was attempted. |
| 5069 | N/A | Low | A cryptographic function property operation was attempted. |
| 5070 | N/A | Low | A cryptographic function property modification was attempted. |
| 5125 | N/A | Low | A request was submitted to the OCSP Responder Service |
| 5126 | N/A | Low | Signing Certificate was automatically updated by the OCSP Responder Service |
| 5127 | N/A | Low | The OCSP Revocation Provider successfully updated the revocation information |
| 5136 | 566 | Low | A directory service object was modified. |
| 5137 | 566 | Low | A directory service object was created. |
| 5138 | N/A | Low | A directory service object was undeleted. |
| 5139 | N/A | Low | A directory service object was moved. |
| 5140 | N/A | Low | A network share object was accessed. |
| 5141 | N/A | Low | A directory service object was deleted. |
| 5152 | N/A | Low | The Windows Filtering Platform blocked a packet. |
| 5153 | N/A | Low | A more restrictive Windows Filtering Platform filter has blocked a packet. |
| 5154 | N/A | Low | The Windows Filtering Platform has permitted an application or service to listen on a port for incoming connections. |
| 5155 | N/A | Low | The Windows Filtering Platform has blocked an application or service from listening on a port for incoming connections. |
| 5156 | N/A | Low | The Windows Filtering Platform has allowed a connection. |
| 5157 | N/A | Low | The Windows Filtering Platform has blocked a connection. |
| 5158 | N/A | Low | The Windows Filtering Platform has permitted a bind to a local port. |
| 5159 | N/A | Low | The Windows Filtering Platform has blocked a bind to a local port. |
| 5378 | N/A | Low | The requested credentials delegation was disallowed by policy. |
| 5440 | N/A | Low | The following callout was present when the Windows Filtering Platform Base Filtering Engine started. |
| 5441 | N/A | Low | The following filter was present when the Windows Filtering Platform Base Filtering Engine started. |
| 5442 | N/A | Low | The following provider was present when the Windows Filtering Platform Base Filtering Engine started. |
| 5443 | N/A | Low | The following provider context was present when the Windows Filtering Platform Base Filtering Engine started. |
| 5444 | N/A | Low | The following sublayer was present when the Windows Filtering Platform Base Filtering Engine started. |
| 5446 | N/A | Low | A Windows Filtering Platform callout has been changed. |
| 5447 | N/A | Low | A Windows Filtering Platform filter has been changed. |
| 5448 | N/A | Low | A Windows Filtering Platform provider has been changed. |
| 5449 | N/A | Low | A Windows Filtering Platform provider context has been changed. |
| 5450 | N/A | Low | A Windows Filtering Platform sublayer has been changed. |
| 5451 | N/A | Low | An IPsec Quick Mode security association was established. |
| 5452 | N/A | Low | An IPsec Quick Mode security association ended. |
| 5456 | N/A | Low | PAStore Engine applied Active Directory storage IPsec policy on the computer. |
| 5457 | N/A | Low | PAStore Engine failed to apply Active Directory storage IPsec policy on the computer. |
| 5458 | N/A | Low | PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer. |
| 5459 | N/A | Low | PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer. |
| 5460 | N/A | Low | PAStore Engine applied local registry storage IPsec policy on the computer. |
| 5461 | N/A | Low | PAStore Engine failed to apply local registry storage IPsec policy on the computer. |
| 5462 | N/A | Low | PAStore Engine failed to apply some rules of the active IPsec policy on the computer. Use the IP Security Monitor snap-in to diagnose the problem. |
| 5463 | N/A | Low | PAStore Engine polled for changes to the active IPsec policy and detected no changes. |
| 5464 | N/A | Low | PAStore Engine polled for changes to the active IPsec policy, detected changes, and applied them to IPsec Services. |
| 5465 | N/A | Low | PAStore Engine received a control for forced reloading of IPsec policy and processed the control successfully. |
| 5466 | N/A | Low | PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory cannot be reached, and will use the cached copy of the Active Directory IPsec policy instead. Any changes made to the Active Directory IPsec policy since the last poll could not be applied. |
| 5467 | N/A | Low | PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, and found no changes to the policy. The cached copy of the Active Directory IPsec policy is no longer being used. |
| 5468 | N/A | Low | PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, found changes to the policy, and applied those changes. The cached copy of the Active Directory IPsec policy is no longer being used. |
| 5471 | N/A | Low | PAStore Engine loaded local storage IPsec policy on the computer. |
| 5472 | N/A | Low | PAStore Engine failed to load local storage IPsec policy on the computer. |
| 5473 | N/A | Low | PAStore Engine loaded directory storage IPsec policy on the computer. |
| 5474 | N/A | Low | PAStore Engine failed to load directory storage IPsec policy on the computer. |
| 5477 | N/A | Low | PAStore Engine failed to add quick mode filter. |
| 5479 | N/A | Low | IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks. |
| 5632 | N/A | Low | A request was made to authenticate to a wireless network. |
| 5633 | N/A | Low | A request was made to authenticate to a wired network. |
| 5712 | N/A | Low | A Remote Procedure Call (RPC) was attempted. |
| 5888 | N/A | Low | An object in the COM Catalog was modified. |
| 5889 | N/A | Low | An object was deleted from the COM Catalog. |
| 5890 | N/A | Low | An object was added to the COM Catalog. |
| 6008 | N/A | Low | The previous system shutdown was unexpected |
| 6144 | N/A | Low | Security policy in the Group Policy objects has been applied successfully. |
| 6272 | N/A | Low | Network Policy Server granted access to a user. |
| N/A | 561 | Low | A handle to an object was requested. |
| N/A | 563 | Low | Object open for delete |
| N/A | 625 | Low | User Account Type Changed |
| N/A | 613 | Low | IPsec policy agent started |
| N/A | 614 | Low | IPsec policy agent disabled |
| N/A | 615 | Low | IPsec policy agent |
| N/A | 616 | Low | IPsec policy agent encountered a potential serious failure |
| 24577 | N/A | Low | Encryption of volume started |
| 24578 | N/A | Low | Encryption of volume stopped |
| 24579 | N/A | Low | Encryption of volume completed |
| 24580 | N/A | Low | Decryption of volume started |
| 24581 | N/A | Low | Decryption of volume stopped |
| 24582 | N/A | Low | Decryption of volume completed |
| 24583 | N/A | Low | Conversion worker thread for volume started |
| 24584 | N/A | Low | Conversion worker thread for volume temporarily stopped |
| 24588 | N/A | Low | The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume |
| 24595 | N/A | Low | Volume %2 contains bad clusters. These clusters will be skipped during conversion. |
| 24621 | N/A | Low | Initial state check: Rolling volume conversion transaction on %2. |
| 5049 | N/A | Low | An IPsec Security Association was deleted. |
| 5478 | N/A | Low | IPsec Services has started successfully. |
Refer to Windows security audit events for a list of many security event IDs and their meanings.
Run wevtutil gp Microsoft-Windows-Security-Auditing /ge /gm:true to get a very detailed listing of all security event IDs
For more information about Windows security event IDs and their meanings, see the Microsoft Support article Description of security events in Windows 7 and in Windows Server 2008 R2. You can also download Security Audit Events for Windows 7 and Windows Server 2008 R2 and Windows 8 and Windows Server 2022 Security Event Details, which provide detailed event information for the referenced operating systems in spreadsheet format.
Источник
