├── SigmaTopLogSources.png
├── TopSecurityEventIDs.png
├── YamatoSecurityLogo.png
├── WindowsEventsWithSigmaRules.png
├── .gitignore
├── YamatoSecurityConfigureWinEventLogs.bat
├── README-Japanese.md
├── README.md
├── LICENSE
├── ConfiguringSecurityLogAuditPolicies-Japanese.md
└── ConfiguringSecurityLogAuditPolicies.md
/SigmaTopLogSources.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Yamato-Security/EnableWindowsLogSettings/HEAD/SigmaTopLogSources.png
--------------------------------------------------------------------------------
/TopSecurityEventIDs.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Yamato-Security/EnableWindowsLogSettings/HEAD/TopSecurityEventIDs.png
--------------------------------------------------------------------------------
/YamatoSecurityLogo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Yamato-Security/EnableWindowsLogSettings/HEAD/YamatoSecurityLogo.png
--------------------------------------------------------------------------------
/WindowsEventsWithSigmaRules.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Yamato-Security/EnableWindowsLogSettings/HEAD/WindowsEventsWithSigmaRules.png
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | /target
2 | /samples
3 | *.test
4 | /.vscode/
5 | .DS_Store
6 | test_*
7 | .env
8 | /logs
9 | *.csv
10 | *.json
11 | *.jsonl
12 | hayabusa*
13 | *.html
14 | *.htm
15 | *.css
--------------------------------------------------------------------------------
/YamatoSecurityConfigureWinEventLogs.bat:
--------------------------------------------------------------------------------
1 | :: Yamato Security's Configure Windows Event Logs Batch File
2 | :: Author: Zach Mathis (@yamatosecurity), Sachiel Archangel
3 | :: This script is based off the work of Sachiel Archangel's WinEventEnable.bat
4 | :: https://github.com/Sachiel-archangel/WinEventEnable/blob/main/WinEventEnable.bat
5 | ::
6 | :: Warning: Use this batch script as a template and understand what you are enabling!
7 | :: You will need to customize this file to fit your environment.
8 | :: Make sure you test this out thoroughly beforing using in production!!
9 | ::
10 | :: You need to run this with local Administrator or SYSTEM privileges.
11 |
12 | :: Increase or decrease the log sizes as you see fit (in bytes of 64kb blocks):
13 | :: 2 GB: 2147483648
14 | :: 1 GB: 1073741824
15 | :: 512 MB: 536870912
16 | :: 256 MB: 268435456
17 | :: 128 MB: 134217728
18 |
19 | :: Set Security and PowerShell-related logs' maximum file size to 1 GB
20 | :: Note: you should also increase the max. size of the Sysmon log to 1 GB if you use Sysmon.
21 | wevtutil sl Security /ms:1073741824
22 | wevtutil sl Microsoft-Windows-PowerShell/Operational /ms:1073741824
23 | wevtutil sl "Windows PowerShell" /ms:1073741824
24 | wevtutil sl PowerShellCore/Operational /ms:1073741824
25 | ::wevtutil sl Microsoft-Windows-Sysmon/Operational /ms:1073741824
26 |
27 | :: Set all other important logs to 128 MB. Increase or decrease to fit your environment.
28 | wevtutil sl System /ms:134217728
29 | wevtutil sl Application /ms:134217728
30 | wevtutil sl "Microsoft-Windows-Windows Defender/Operational" /ms:134217728
31 | wevtutil sl "Microsoft-Windows-Bits-Client/Operational" /ms:134217728
32 | wevtutil sl "Microsoft-Windows-Windows Firewall With Advanced Security/Firewall" /ms:134217728
33 | wevtutil sl "Microsoft-Windows-NTLM/Operational" /ms:134217728
34 | wevtutil sl "Microsoft-Windows-Security-Mitigations/KernelMode" /ms:134217728
35 | wevtutil sl "Microsoft-Windows-Security-Mitigations/UserMode" /ms:134217728
36 | wevtutil sl "Microsoft-Windows-PrintService/Admin" /ms:134217728
37 | wevtutil sl "Microsoft-Windows-Security-Mitigations/UserMode" /ms:134217728
38 | wevtutil sl "Microsoft-Windows-PrintService/Operational" /ms:134217728
39 | wevtutil sl "Microsoft-Windows-SmbClient/Security" /ms:134217728
40 | wevtutil sl "Microsoft-Windows-AppLocker/MSI and Script" /ms:134217728
41 | wevtutil sl "Microsoft-Windows-AppLocker/EXE and DLL" /ms:134217728
42 | wevtutil sl "Microsoft-Windows-AppLocker/Packaged app-Deployment" /ms:134217728
43 | wevtutil sl "Microsoft-Windows-AppLocker/Packaged app-Execution" /ms:134217728
44 | wevtutil sl "Microsoft-Windows-CodeIntegrity/Operational" /ms:134217728
45 | wevtutil sl "Microsoft-Windows-Diagnosis-Scripted/Operational" /ms:134217728
46 | wevtutil sl "Microsoft-Windows-DriverFrameworks-UserMode/Operational" /ms:134217728
47 | wevtutil sl "Microsoft-Windows-WMI-Activity/Operational" /ms:134217728
48 | wevtutil sl "Microsoft-Windows-TerminalServices-LocalSessionManager/Operational" /ms:134217728
49 | wevtutil sl "Microsoft-Windows-TaskScheduler/Operational" /ms:134217728
50 |
51 | :: Enable any logs that need to be enabled
52 | wevtutil sl Microsoft-Windows-TaskScheduler/Operational /e:true
53 | wevtutil sl Microsoft-Windows-DriverFrameworks-UserMode/Operational /e:true
54 |
55 | :: Enable PowerShell Module logging
56 | reg add HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ModuleLogging /v EnableModuleLogging /f /t REG_DWORD /d 1
57 | reg add HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames /f /v ^* /t REG_SZ /d ^*
58 |
59 | :: Enable PowerShell Script Block logging
60 | reg add HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging /v EnableScriptBlockLogging /f /t REG_DWORD /d 1
61 |
62 | ::
63 | :: Configure Security log
64 | :: Note: subcategory IDs are used instead of the names in order to work in any OS language.
65 |
66 | :: Account Logon
67 | :::: Credential Validation
68 | auditpol /set /subcategory:{0CCE923F-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
69 | :::: Kerberos Authentication Service (disable for clients)
70 | auditpol /set /subcategory:{0CCE9242-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
71 | :::: Kerberos Service Ticket Operations (disable for clients)
72 | auditpol /set /subcategory:{0CCE9240-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
73 |
74 | :: Account Management
75 | :::: Computer Account Management
76 | auditpol /set /subcategory:{0CCE9236-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
77 | :::: Other Account Management Events
78 | auditpol /set /subcategory:{0CCE923A-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
79 | :::: Security Group Management
80 | auditpol /set /subcategory:{0CCE9237-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
81 | :::: User Account Management
82 | auditpol /set /subcategory:{0CCE9235-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
83 |
84 | :: Detailed Tracking
85 | :::: Plug and Play
86 | auditpol /set /subcategory:{0cce9248-69ae-11d9-bed3-505054503030} /success:enable /failure:enable
87 | :::: Process Creation
88 | auditpol /set /subcategory:{0CCE922B-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
89 | :::: Enable command line auditing (Detailed Tracking)
90 | reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit /v ProcessCreationIncludeCmdLine_Enabled /f /t REG_DWORD /d 1
91 | :::: Process Termination (default: disabled)
92 | :: auditpol /set /subcategory:{0CCE922C-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
93 | :::: RPC Events
94 | auditpol /set /subcategory:{0CCE922E-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
95 | :::: Audit Token Right Adjustments (default: disabled)
96 | :: auditpol /set /subcategory:{0CCE924A-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
97 |
98 | :: DS Access
99 | :::: Directory Service Access (disable for clients)
100 | auditpol /set /subcategory:{0CCE923B-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
101 | :::: Directory Service Changes (disable for clients)
102 | auditpol /set /subcategory:{0CCE923C-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
103 |
104 | :: Logon/Logoff
105 | :::: Account Lockout
106 | auditpol /set /subcategory:{0CCE9217-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
107 | :::: Group Membership (disabled due to noise)
108 | :: auditpol /set /subcategory:{0CCE9249-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
109 | :::: Logoff
110 | auditpol /set /subcategory:{0CCE9216-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
111 | :::: Logon
112 | auditpol /set /subcategory:{0CCE9215-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
113 | :::: Network Policy Server (currently disabled while testing)
114 | :: auditpol /set /subcategory:{0CCE9243-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
115 | :::: Other Logon/Logoff Events
116 | auditpol /set /subcategory:{0CCE921C-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
117 | :::: Special Logon
118 | auditpol /set /subcategory:{0CCE921B-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
119 |
120 | :: Object Access
121 | :::: Application Generated (currently disabled while testing)
122 | :: auditpol /set /subcategory:{0CCE9222-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
123 | :::: Certification Services (disable for client OSes)
124 | auditpol /set /subcategory:{0CCE9221-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
125 | :::: Detailed File Share (disabled due to noise)
126 | :: auditpol /set /subcategory:{0CCE9244-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
127 | :::: File Share (disable if too noisy)
128 | auditpol /set /subcategory:{0CCE9224-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
129 | :::: File System (disabled due to noise)
130 | :: auditpol /set /subcategory:{0CCE921D-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
131 | :::: Filtering Platform Connection (disable if too noisy)
132 | auditpol /set /subcategory:{0CCE9226-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
133 | :::: Filtering Platform Packet Drop (disabled due to noise)
134 | :: auditpol /set /subcategory:{0CCE9225-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
135 | :::: Kernel Object (disabled due to noise)
136 | :: auditpol /set /subcategory:{0CCE921F-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
137 | :::: Other Object Access Events
138 | auditpol /set /subcategory:{0CCE9227-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
139 | :::: Registry (currently disabled due to noise)
140 | :: auditpol /set /subcategory:{0CCE921E-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
141 | :::: Removable Storage
142 | auditpol /set /subcategory:{0CCE9245-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
143 | :::: SAM
144 | auditpol /set /subcategory:{0CCE9220-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
145 |
146 | :: Policy Change
147 | :::: Audit Policy Change
148 | auditpol /set /subcategory:{0CCE922F-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
149 | :::: Authentication Policy Change
150 | auditpol /set /subcategory:{0CCE9230-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
151 | :::: Authorization Policy Change (currently disabled while testing)
152 | :: auditpol /set /subcategory:{0CCE9231-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
153 | :::: Filtering Platform Policy Change (currently disabled while testing)
154 | :: auditpol /set /subcategory:{0CCE9233-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
155 | :::: MPSSVC Rule-Level Policy Change (currently disabled while testing)
156 | :: auditpol /set /subcategory:{0CCE9232-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
157 | :::: Other Policy Change Events
158 | auditpol /set /subcategory:{0CCE9234-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
159 |
160 | :: Privilege Use
161 | :::: Sensitive Privilege Use (disable if too noisy)
162 | auditpol /set /subcategory:{0CCE9228-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
163 |
164 | :: System
165 | :::: Other System Events (needs testing)
166 | auditpol /set /subcategory:{0CCE9214-69AE-11D9-BED3-505054503030} /success:disable /failure:enable
167 | :::: Security State Change
168 | auditpol /set /subcategory:{0CCE9210-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
169 | :::: Security System Extension
170 | auditpol /set /subcategory:{0CCE9211-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
171 | :::: System Integrity
172 | auditpol /set /subcategory:{0CCE9212-69AE-11D9-BED3-505054503030} /success:enable /failure:enable
173 |
--------------------------------------------------------------------------------
/README-Japanese.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | 
4 |
5 |
6 | 大和セキュリティによる、DFIRと脅威ハンティングのためのWindowsイベントログ設定のガイド
7 |
8 | [
English] | [
日本語]
9 |
11 |
12 | Windowsのイベントログの設定と監視に関するガイドで、Sigmaルールが何かを検出するために、また正しいDFIR調査のために適切なログを有効にすることに重点を置いています。
13 |
14 | # TLDR
15 |
16 | * Windowsのデフォルトの監査設定では[sigma](https://github.com/SigmaHQ/sigma)ルールの10~20%程度しか利用できません。
17 | * Windowsのログが有効になっていても、デフォルトではログの最大サイズがたった1〜20MBなので、すぐに証拠が上書きされてしまう可能性が高いです。
18 | * Sigmaルールの約75%まで利用可能にし、必要なだけログを保持するように[YamatoSecurityConfigureWinEventLogs.bat](YamatoSecurityConfigureWinEventLogs.bat)もしくは[WELA (Windows Event Log Auditor)](https://github.com/Yamato-Security/WELA/blob/main/README-Japanese.md)の導入で適切な監査設定を行いましょう。
19 | - **注意: 必要に応じてスクリプトをカスタマイズし、本番環境で導入する前に必ずテストしてください！**
20 | * 100%のSigmaルールを利用したい方は、[sysmon](https://learn.microsoft.com/en-us/sysinternals/downloads/sysmon)を導入する必要があります。（お勧め！）
21 |
22 | # 関連プロジェクト
23 |
24 | * [Hayabusa](https://github.com/Yamato-Security/hayabusa/blob/main/README-Japanese.md) - Sigmaベースの脅威ハンティングと、Windowsイベントログのファストフォレンジックタイムライン生成ツール。
25 | * [Hayabusa Rules](https://github.com/Yamato-Security/hayabusa-rules/blob/main/README-Japanese.md) - Hayabusaのための検知ルール。
26 | * [Hayabusa Sample EVTXs](https://github.com/Yamato-Security/hayabusa-sample-evtx) - Hayabusa/Sigma検出ルールをテストするためのサンプルevtxファイル。
27 | * [Takajo](https://github.com/Yamato-Security/takajo/blob/main/README-Japanese.md) - Hayabusa結果の解析ツール。
28 | * [WELA (Windows Event Log Auditor)](https://github.com/Yamato-Security/WELA/blob/main/README-Japanese.md) - Windowsイベントログ設定の監査ツール。
29 |
30 | ## 目次
31 |
32 | - [TLDR](#tldr)
33 | - [関連プロジェクト](#関連プロジェクト)
34 | - [目次](#目次)
35 | - [作者](#作者)
36 | - [コントリビュータ](#コントリビュータ)
37 | - [Acknowledgements](#acknowledgements)
38 | - [デフォルトの Windows ログ設定の問題](#デフォルトの-windows-ログ設定の問題)
39 | - [注意: 端末の設定変更は自己責任で！](#注意-端末の設定変更は自己責任で)
40 | - [重要な Windowsイベントログ](#重要な-windowsイベントログ)
41 | - [Sigmaのトップログソース](#sigmaのトップログソース)
42 | - [上位のSigmaログソース](#上位のsigmaログソース)
43 | - [上位のSecurityイベントID](#上位のsecurityイベントid)
44 | - [最大ファイル サイズの増加](#最大ファイル-サイズの増加)
45 | - [オプション 1: イベントビューアー(手動)](#オプション-1-イベントビューアー手動)
46 | - [オプション 2: Windowsビルトインツール](#オプション-2-windowsビルトインツール)
47 | - [オプション 3: PowerShell](#オプション-3-powershell)
48 | - [オプション 4: グループポリシー](#オプション-4-グループポリシー)
49 | - [ログ設定を改善するスクリプト](#ログ設定を改善するスクリプト)
50 | - [ログ設定の改善](#ログ設定の改善)
51 | - [Sysmonログ (Sigmaルール1382件)](#sysmonログ-sigmaルール1382件)
52 | - [Securityログ (Sigmaルール 1045件(process creationルール903件 + その他ルール142件))](#securityログ-sigmaルール-1045件process-creationルール903件--その他ルール142件)
53 | - [Powershellログ (Sigmaルール 175件)](#powershellログ-sigmaルール-175件)
54 | - [モジュールログ (Sigmaルール 30件)](#モジュールログ-sigmaルール-30件)
55 | - [モジュールログの有効化](#モジュールログの有効化)
56 | - [オプション 1: グループポリシーによる有効化](#オプション-1-グループポリシーによる有効化)
57 | - [オプション 2: レジストリによる有効化](#オプション-2-レジストリによる有効化)
58 | - [スクリプトブロックログ (Sigmaルール 134件)](#スクリプトブロックログ-sigmaルール-134件)
59 | - [スクリプトブロックログの有効化](#スクリプトブロックログの有効化)
60 | - [オプション 1: グループポリシーによる有効化](#オプション-1-グループポリシーによる有効化-1)
61 | - [オプション 2: レジストリによる有効化](#オプション-2-レジストリによる有効化-1)
62 | - [トランスクリプションログ](#トランスクリプションログ)
63 | - [トランスクリプションログの有効化](#トランスクリプションログの有効化)
64 | - [オプション 1: グループポリシーによる有効化](#オプション-1-グループポリシーによる有効化-2)
65 | - [オプション 2: レジストリによる有効化](#オプション-2-レジストリによる有効化-2)
66 | - [参考記事](#参考記事)
67 | - [Systemログ (Sigmaルール 55件)](#systemログ-sigmaルール-55件)
68 | - [Applicationログ (Sigmaルール 16件)](#applicationログ-sigmaルール-16件)
69 | - [Windows Defender Operationalログ (Sigmaルール 10件)](#windows-defender-operationalログ-sigmaルール-10件)
70 | - [Bits-Client Operationalログ (Sigmaルール 6件)](#bits-client-operationalログ-sigmaルール-6件)
71 | - [Firewallログ (Sigmaルール 6件)](#firewallログ-sigmaルール-6件)
72 | - [NTLM Operationalログ (Sigmaルール 3件)](#ntlm-operationalログ-sigmaルール-3件)
73 | - [Security-Mitigations KernelModeとUserModeログ (Sigmaルール 2件)](#security-mitigations-kernelmodeとusermodeログ-sigmaルール-2件)
74 | - [PrintServiceログ (Sigmaルール 2件)](#printserviceログ-sigmaルール-2件)
75 | - [Adminログ (Sigmaルール 1件)](#adminログ-sigmaルール-1件)
76 | - [Operationalログ (Sigmaルール 1件)](#operationalログ-sigmaルール-1件)
77 | - [SMBClient Securityログ (Sigmaルール 2件)](#smbclient-securityログ-sigmaルール-2件)
78 | - [AppLockerログ (Sigmaルール 1件)](#applockerログ-sigmaルール-1件)
79 | - [CodeIntegrity Operationalログ (Sigmaルール 1件)](#codeintegrity-operationalログ-sigmaルール-1件)
80 | - [Diagnosis-Scripted Operationalログ (Sigmaルール 1件)](#diagnosis-scripted-operationalログ-sigmaルール-1件)
81 | - [DriverFrameworks-UserMode Operationalログ (Sigmaルール 1件)](#driverframeworks-usermode-operationalログ-sigmaルール-1件)
82 | - [WMI-Activity Operationalログ (Sigmaルール 1件)](#wmi-activity-operationalログ-sigmaルール-1件)
83 | - [TerminalServices-LocalSessionManager Operationalログ (Sigmaルール 1件)](#terminalservices-localsessionmanager-operationalログ-sigmaルール-1件)
84 | - [TaskScheduler Operationalログ (Sigmaルール 1件)](#taskscheduler-operationalログ-sigmaルール-1件)
85 |
86 | # 作者
87 |
88 | 田中ザック (Zaku / [@yamatosecurity](https://twitter.com/yamatosecurity))。
89 | より多くの研究とテストを行い、(検知ルールとドキュメンテーションの)改善の余地があるため、定期的に更新していく予定です。
90 | PRは歓迎され、喜んでコントリビューターとして追加させていただきます。
91 |
92 | もし、このガイドが役に立つのであれば、GitHubで星を付けてください。更新し続けるモチベーションが上がります。
93 |
94 | # コントリビュータ
95 |
96 | * DustInDark: 日本語版の修正。
97 | * Fukusuke Takahashi (fukusuket): 和訳と修正。
98 | * LasseKrache: Batchスクリプトのバグの指摘。
99 |
100 | # Acknowledgements
101 |
102 | 多くの情報はマイクロソフトの[詳細なセキュリティ監査に関するFAQ](https://learn.microsoft.com/ja-jp/windows/security/threat-protection/auditing/advanced-security-auditing-faq), [sigma](https://github.com/SigmaHQ/sigma)ルール, [ACSCのガイド](https://www.cyber.gov.au/acsc/view-all-content/publications/windows-event-logging-and-forwarding)、そして私自身の調査/テストから得たものです。特に[Sigmaコミュニティ](https://github.com/SigmaHQ/sigma/graphs/contributors)には、世の中のすべての防衛者のために脅威検知能力をオープンソースかつフリーにしてくれたことに感謝しています。
103 |
104 | # デフォルトの Windows ログ設定の問題
105 |
106 | デフォルトでは、Windows は悪意のあるアクティビティの検出と、フォレンジック調査の実行に必要な多くのイベントをログに記録しません。
107 | また、イベントファイルのデフォルトの最大サイズは、クラッシックイベントログ(`Security`、`System`、`Application`)ではわずか20MB、PowerShellでは15MB、その他のほとんどすべてのログではわずか1MBであるため、証拠がすぐ上書きされる可能性が高くなります。
108 | システム管理者が Windows端末を簡単に設定できるように、このリポジトリにはシンプルな[バッチスクリプト](YamatoSecurityConfigureWinEventLogs.bat)が用意されており、インシデントが発生したときに必要なログを取得できます。
109 | 大規模なネットワークの場合は、このドキュメントを参照として使用し、グループポリシーやInTuneを使用して端末を設定することをお勧めします。
110 |
111 | # 注意: 端末の設定変更は自己責任で！
112 |
113 | Windowsのデフォルトのイベントログ設定を改善することを強く推奨します。設定を改善することで最も正確な情報を提供できるようになります。
114 | しかし、あまりにも多くのログを有効にすることによる悪影響や、このリポジトリ内の何かの正確性について、一切の責任を負いません。
115 | 本番環境に導入する前に、設定変更を十分理解した上で、テスト端末で十分テストすることは、システム管理者の責任です。
116 | 環境を模倣したテスト端末で、少なくとも1週間はできるだけ多くのログ記録を有効にしてから、ノイズが多すぎるイベントがないか、必要なイベントが記録されているかどうかを確認することをお勧めします。
117 |
118 | [Hayabusa](https://github.com/Yamato-Security/hayabusa)のイベントID集計機能を使用して、evtxファイル内のイベントIDの総数と割合を確認できます。
119 |
120 | 例：`hayabusa.exe eid-metrics -f path/to/Security.evtx`
121 |
122 | # 重要な Windowsイベントログ
123 |
124 | 1. 有効にするべき最も重要なイベントログは、おそらく`Process Creation`(プロセス作成)のイベントで、システムで実行されているプロセスを追跡するものです。
125 | 現在、Sigmaルールの約半分がこのイベントに依存しています。
126 | Sysmonをインストールして、イベントID`1`を有効にするか、ビルトインログ (SecurityイベントID`4688`)を有効にすることで記録できます。
127 | `Sysmon 1`に、実行ファイルのハッシュ値やメタデータなどの詳細情報も記録されるので理想的ですが、Sysmonをインストールできない場合は、Windowsのビルトインログの`Security 4688`が使えます。
128 | ただし、多くの検知ルールがコマンドライン情報にあるシグネチャを探すため、コマンドライン情報も記録されるように設定すべきです。
129 | 残念ながら`Security 4688`は、Sysmonプロセス作成ログほど詳細な情報は記録されないので、`Security 4688`に対応していない`Process Creation`検知ルールもあります。
130 | 2. 2番目に重要なイベントログは、適切に設定されたSecurityログです。
131 | 3. 攻撃者はPowerShellを悪用することが多いため、3番目に重要なのはおそらくPowerShellモジュールログとスクリプトブロックログです。
132 | 4. 4番目は、おそらく他のすべてのSysmonイベントです。
133 | 5. これらの他に、「アプリケーションとサービスログ」フォルダには、非常に重要な他の多くのログもあります:
134 | AppLocker, Bits-Client, NTLM, PowerShell, PrintService, Security-Mitigations, Windows Defender, Windows Firewall With Advanced Security, WMI-Activity等々。
135 |
136 | ## Sigmaのトップログソース
137 |
138 | 
139 |
140 | デフォルトのWindows監査設定で使用できるSigmaルールは、約10〜20%です。
141 |
142 | ### 上位のSigmaログソース
143 |
144 | 
145 |
146 | ### 上位のSecurityイベントID
147 |
148 | 
149 |
150 | # 最大ファイル サイズの増加
151 |
152 | ## オプション 1: イベントビューアー(手動)
153 |
154 | これを大規模に行うのは現実的ではありませんが、ログの有効、無効を変更し、最大ファイル サイズを確認および構成する最も簡単な方法は、イベントビューアーでログを右クリックし、`プロパティ`を開くことです。
155 |
156 | ## オプション 2: Windowsビルトインツール
157 |
158 | ビルトインツールのwevtutilコマンドを使用できます。
159 |
160 | 例: `wevtutil sl Security /ms:1073741824` (セキュリティログの最大ファイルサイズを1GBに増やす)
161 |
162 | ## オプション 3: PowerShell
163 |
164 | 例:
165 | ```powershell
166 | $sysmon = Get-WinEvent -ListLog Microsoft-Windows-Sysmon/Operational
167 | $sysmon.MaximumSizeInBytes = 2048000000 #2GB
168 | $sysmon.SaveChanges()
169 | ```
170 |
171 | ## オプション 4: グループポリシー
172 |
173 | `Security`、`System`、`Application`などのクラッシックイベントログの最大ファイルサイズを増やすのは簡単ですが、他のイベントログの最大ファイルサイズを変更するには、残念ながら、管理用テンプレートをインストールするか、レジストリを直接変更する必要があります。
174 | 起動時に`.bat`スクリプトを使用して最大ファイルサイズを増やした方が簡単な場合があります。
175 |
176 | # ログ設定を改善するスクリプト
177 |
178 | 最大ファイルサイズを増やして適切なログを有効にするスクリプトが、[YamatoSecurityConfigureWinEventLogs.bat](YamatoSecurityConfigureWinEventLogs.bat)で提供されています。
179 |
180 | # ログ設定の改善
181 |
182 | ## Sysmonログ (Sigmaルール1382件)
183 |
184 | ファイル: `Microsoft-Windows-Sysmon%4Operational.evtx`
185 |
186 | デフォルトの設定: `インストールされていない`
187 |
188 | sysmonをインストールして設定することは、Windows端末での可視性を高めるための最善の方法ですが、計画、テスト、およびメンテナンスが必要になります。
189 |
190 | Sysmonはそれ自体大きなトピックなので、現時点ではこのドキュメントの範囲外です。
191 | 次のリソースを確認することをお勧めします。
192 |
193 | * [TrustedSecのSysmonコミュニティガイド](https://github.com/trustedsec/SysmonCommunityGuide)
194 | * [Sysmon Modular](https://github.com/olafhartong/sysmon-modular)
195 | * [Florian Roth氏によるSwift On SecurityのSysmon設定ファイルを更新しているフォーク](https://github.com/Neo23x0/sysmon-config)
196 | * [Ion-storm氏によるSwift On SecurityのSysmon設定ファイルを更新しているフォーク](https://github.com/ion-storm/sysmon-config)
197 | * [Cyb3rWard0g氏のsysmon設定ファイル](https://github.com/OTRF/Blacksmith/blob/master/resources/configs/sysmon/sysmon.xml)
198 |
199 | ## Securityログ (Sigmaルール 1045件(process creationルール903件 + その他ルール142件))
200 |
201 | ファイル: `Security.evtx`
202 |
203 | デフォルトの設定: `一部有効`
204 |
205 | Securityログの設定が最も複雑なため、別のドキュメントを用意しました: [ConfiguringSecurityLogAuditPolicies-Japanese.md](ConfiguringSecurityLogAuditPolicies-Japanese.md)
206 |
207 | ## Powershellログ (Sigmaルール 175件)
208 |
209 | ファイル: `Microsoft-Windows-PowerShell%4Operational.evtx`
210 |
211 | ### モジュールログ (Sigmaルール 30件)
212 |
213 | モジュールログを有効にすると、イベントID`4103`が記録されます。
214 | モジュールログには、古いOSやバージョンのPowerShellでも動作する利点がある: PowerShell 3.0 (Win 7+)。
215 | また、実行したPowerShellコマンドとその結果の両方をログに残すことができるのも利点です。
216 | デメリットは、イベント数が極端に多くなってしまうことです。
217 | 例えば、攻撃者がMimikatzを実行した場合、2000以上のイベントを含む7MBのログが作成されます！
218 |
219 | #### モジュールログの有効化
220 |
221 | デフォルトの設定: `監査なし`
222 |
223 | ##### オプション 1: グループポリシーによる有効化
224 |
225 | グループポリシーエディター(`gpedit.msc`)で、`コンピューターの構成 > 管理用テンプレート > Windowsコンポーネント > Windows PowerShell`を開き、`モジュールログを有効にする`を有効にします。
226 | `オプション`ペインで、`表示...`ボタンをクリックすると、ログを記録するモジュールを設定できます。
227 | すべてのモジュールを記録するには、`値`テキストボックスに`*`を入力します。
228 |
229 | ##### オプション 2: レジストリによる有効化
230 |
231 | ```
232 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ModuleLogging → EnableModuleLogging = 1
233 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames → * = *
234 | ```
235 |
236 | ### スクリプトブロックログ (Sigmaルール 134件)
237 |
238 | デフォルトの設定: `Win 10/2016以降では、PowerShellスクリプトがAMSIによって疑わしいと判定された場合、警告レベルでログに記録されるが、その他のログは記録されない`
239 |
240 | スクリプトブロックログを有効にすると、イベントID`4104`が記録されます。`スクリプトブロックの呼び出し開始/停止イベントをログに記録する`も有効にすると イベントID`4105`と`4106`も有効になりますが、ノイズが増えるだけなので推奨されません。
241 | PowerShell 5.0+ (Win 10+)ではデフォルトでサポートされていますが、.NET 4.5とWMF 4.0+をインストールすれば、古いOS (Win 7+)でも有効にすることができます。
242 | 残念ながら、1つのWindowsイベントログの最大サイズは32KBなので、これより大きいPowerShellスクリプトは32KBサイズのブロックに分割されます。
243 | もし、元々の`PowerShell Operational.evtx`ファイルがあれば、[block-parser](https://github.com/matthewdunwoody/block-parser)ツールを使って、これらのログを読みやすい一つのテキストファイルにもとめることができます。
244 | スクリプトブロックログの良い点は、悪意のあるスクリプトがXOR、Base 64、ROT13などで難読化されていても、解読されたスクリプトが記録されるため、解析が非常に容易になる点です。
245 | 攻撃者がMimikatzを実行した場合、7MBで2000以上のイベントが発生するのに比べ、5MBで約100件のイベントが発生するだけなので、モジュールログよりも解析しやすいです。
246 | ただし、スクリプトブロックログでは、コマンドの出力は記録されません。
247 |
248 | #### スクリプトブロックログの有効化
249 |
250 | #### オプション 1: グループポリシーによる有効化
251 |
252 | グループポリシーエディターで、`コンピューターの構成 > 管理用テンプレート > Windowsコンポーネント > Windows PowerShell`を開き、`PowerShellスクリプトブロックのログ記録を有効にする`を有効にします。
253 |
254 | #### オプション 2: レジストリによる有効化
255 |
256 | `HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging → EnableScriptBlockLogging = 1`
257 |
258 | ### トランスクリプションログ
259 |
260 | デフォルトの設定: `監査なし`
261 |
262 | トランスクリプションログを有効にすることでPowerShellログをローカル端末のテキストファイルに保存することも可能です。
263 | 攻撃者は通常、アンチフォレンジックのためにトランスクリプションログを簡単に削除することができますが、攻撃者がすべてのイベントログを消去しても、トランスクリプションログを検索して削除しないシナリオもあるかもしれません。
264 | そのため、可能であればトランスクリプションログも有効にすることをお勧めします。
265 | デフォルトでは、ユーザのドキュメントフォルダに保存されます。
266 | 理想的には、トランスクリプトログは書き込み専用のネットワークファイル共有に保存されるべきであるが、実際にはこれを実施することは難しいです。
267 | トランスクリプションログの利点は、各コマンドのタイムスタンプとメタデータを含み、Mimikatz実行時に6KB以下と非常にストレージ効率が良いことです。
268 | 欠点は、トランスクリプションログがPowerShellのターミナルに表示されるテキストしか記録されないことです。
269 |
270 | #### トランスクリプションログの有効化
271 |
272 | ##### オプション 1: グループポリシーによる有効化
273 |
274 | グループポリシーエディターで、`コンピューターの構成 > 管理用テンプレート > Windowsコンポーネント > Windows PowerShell`を開き、`PowerShellトランスクリプションを有効にする`を有効にします。
275 | その後、出力ディレクトリを指定します。
276 |
277 | ##### オプション 2: レジストリによる有効化
278 |
279 | ```
280 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\Transcription → EnableTranscripting = 1
281 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\Transcription → EnableInvocationHeader = 1
282 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\Transcription → OutputDirectory = “” (パスを入力する。空白の場合はデフォルトのパス。)
283 | ```
284 |
285 | ### 参考記事
286 |
287 | * [Mandiant Blog: Greater Visibility Through PowerShell Logging](https://www.mandiant.com/resources/blog/greater-visibilityt)
288 |
289 | ## Systemログ (Sigmaルール 55件)
290 |
291 | ファイル: `System.evtx`
292 |
293 | デフォルトの設定: `有効。20 MB`
294 |
295 | マルウェアはしばしば、永続化、ローカル特権昇格などのためにサービスをインストールします。その痕跡がこのログに残ります。
296 | また、このログから様々な脆弱性が悪用されていることを検出することが可能です。
297 |
298 | ## Applicationログ (Sigmaルール 16件)
299 |
300 | ファイル: `Application.evtx`
301 |
302 | デフォルトの設定: `有効。20 MB`
303 |
304 | このログはほとんどノイズですが、ここに重要な証拠を見つけることができるかもしれません。
305 | 注意点としては、異なるベンダーが異なるイベントに同じイベントIDを使用するため、イベントIDだけでなくプロバイダ名でもフィルタリングする必要があることです。
306 |
307 | ## Windows Defender Operationalログ (Sigmaルール 10件)
308 |
309 | ファイル: `Microsoft-Windows-Windows Defender%4Operational.evtx`
310 |
311 | デフォルトの設定: `有効。1 MB`
312 |
313 | （重要な監視項目の）Windows Defenderのアラートだけでなく、除外項目が追加された、改ざん防止機能が無効になった、履歴が削除された、などのイベントも検出できます。
314 |
315 | ## Bits-Client Operationalログ (Sigmaルール 6件)
316 |
317 | ファイル: `Microsoft-Windows-Bits-Client%4Operational.evtx`
318 |
319 | デフォルトの設定: `有効。1 MB`
320 |
321 | Bitsadmin.exeは、攻撃者がマルウェアのダウンロードや実行に悪用する一般的な[lolbin](https://lolbas-project.github.io/lolbas/Binaries/Bitsadmin/)です。
322 | このログを見れば、その証拠が見つかるかもしれません。
323 | ただし、誤検出が多いので、注意が必要です。
324 |
325 | ## Firewallログ (Sigmaルール 6件)
326 |
327 | ファイル: `Microsoft-Windows-Windows Firewall With Advanced Security%4Firewall.evtx`
328 |
329 | デフォルトの設定: `有効？ 1 MB`
330 |
331 | ファイアウォールのルールが追加/変更/削除された形跡は、こちらで確認できます。
332 | マルウェアはしばしば、C2サーバと通信できるようにファイアウォールルールを追加したり、横展開するためにプロキシルールを追加したりします。
333 |
334 | ## NTLM Operationalログ (Sigmaルール 3件)
335 |
336 | ファイル: `Microsoft-Windows-NTLM%4Operational.evtx`
337 |
338 | デフォルトの設定: `ログ自体は有効になっているが、監査設定は無効になっている。1 MB`
339 |
340 | NTLM認証を無効にしたい場合、このログを有効にすることをお勧めします。
341 | NTLMを無効にすると、ほとんどの場合、一部の端末が接続できなくなるため、まずDCや他のサーバでこのログを監視して、誰がまだNTLMを使用しているかを確認し、それらのユーザから徐々にNTLMを無効にしてから、グローバルに無効にすることを推奨します。
342 | 4624などのログオンイベントで、内向きの接続にNTLMが使用されていることを確認できますが、誰がNTLMで外向きに接続をしているかを監視したい場合は、このログを有効にする必要があります。
343 |
344 | 監査設定を有効にするために、グループポリシーで`コンピューターの構成 > Windowsの設定 > セキュリティの設定 > ローカルポリシー > セキュリティオプション`配下の`ネットワークセキュリティ: NTLMを制限する:`の様々な設定を正しく設定する必要があります。
345 |
346 | 参考記事: [Farewell NTLM](https://www.scip.ch/en/?labs.20210909)
347 |
348 | ## Security-Mitigations KernelModeとUserModeログ (Sigmaルール 2件)
349 |
350 | ファイル: `Microsoft-Windows-Security-Mitigations%4KernelMode.evtx`, `Microsoft-Windows-Security-Mitigations%4UserMode.evtx`
351 |
352 | デフォルトの設定: `有効。1 MB`
353 |
354 | 現時点では、これらのログに対して2件のSigmaルールしかありませんが、エクスプロイト保護、ネットワーク保護、コントロールされたフォルダーアクセス、攻撃面の縮小(ASR)のすべてのログ（約40以上のイベントID）を収集し、監視すべきです。
355 | 残念ながら、攻撃面の縮小(ASR)のログ（以前はWDEG(Windows Defender Exploit Guard)とEMET）は複数のログに分散しており、検索するには複雑なXMLクエリが必要です。
356 |
357 | 詳細: [攻撃面の縮小機能を理解して使用する](https://learn.microsoft.com/ja-jp/microsoft-365/security/defender-endpoint/overview-attack-surface-reduction?view=o365-worldwide)
358 |
359 | ## PrintServiceログ (Sigmaルール 2件)
360 |
361 | 印刷スプーラーへの攻撃を検知するために、Operationalログを有効にすることを推奨します。(例: PrintNightmare等々)
362 |
363 | ### Adminログ (Sigmaルール 1件)
364 |
365 | ファイル: `Microsoft-Windows-PrintService%4Admin.evtx`
366 |
367 | デフォルトの設定: `有効。1 MB`
368 |
369 | ### Operationalログ (Sigmaルール 1件)
370 |
371 | ファイル: `Microsoft-Windows-PrintService%4Operational.evtx`
372 |
373 | デフォルトの設定: `無効。1 MB`
374 |
375 | ## SMBClient Securityログ (Sigmaルール 2件)
376 |
377 | ファイル: `Microsoft-Windows-SmbClient%4Security.evtx`
378 |
379 | デフォルトの設定: `有効。8 MB`
380 |
381 | PrintNightmare攻撃 (ルール: `Suspicious Rejected SMB Guest Logon From IP`)や隠し共有をマウントするユーザを検出できます。
382 |
383 | ## AppLockerログ (Sigmaルール 1件)
384 |
385 | ファイル: `Microsoft-Windows-AppLocker%4MSI and Script.evtx`, `Microsoft-Windows-AppLocker%4EXE and DLL.evtx`, `Microsoft-Windows-AppLocker%4Packaged app-Deployment.evtx`, `Microsoft-Windows-AppLocker%4Packaged app-Execution.evtx`
386 |
387 | デフォルトの設定: `AppLockerが有効の場合、有効？ 1 MB`
388 |
389 | AppLockerを使用している場合、有効になっているか確認し、監視することが重要です。
390 |
391 | ## CodeIntegrity Operationalログ (Sigmaルール 1件)
392 |
393 | ファイル: `Microsoft-Windows-CodeIntegrity%4Operational.evtx`
394 |
395 | デフォルトの設定: `有効。1 MB`
396 |
397 | このログを確認すると、Windowsのコード整合性チェックでブロックされたドライバーのロードイベントを検出することができます。そのため、ロードに失敗した悪意のあるドライバーを示すことがあります。
398 |
399 | ## Diagnosis-Scripted Operationalログ (Sigmaルール 1件)
400 |
401 | ファイル: `Microsoft-Windows-Diagnosis-Scripted%4Operational.evtx`
402 |
403 | デフォルトの設定: `有効。1 MB`
404 |
405 | diagcabパッケージが悪用された証拠は、こちらで確認できます。
406 |
407 | ## DriverFrameworks-UserMode Operationalログ (Sigmaルール 1件)
408 |
409 | ファイル: `Microsoft-Windows-DriverFrameworks-UserMode%4Operational.evtx`
410 |
411 | デフォルトの設定: `監査なし。1 MB`
412 |
413 | 接続されたUSBデバイスの痕跡がここで記録されます。
414 |
415 | ## WMI-Activity Operationalログ (Sigmaルール 1件)
416 |
417 | ファイル: `Microsoft-Windows-WMI-Activity%4Operational.evtx`
418 |
419 | デフォルトの設定: `Win10以降では有効になっている。1 MB`
420 |
421 | 攻撃者はしばしばWMIを悪用して永続化や横展開するので、このログを監視することは重要です。
422 |
423 | ## TerminalServices-LocalSessionManager Operationalログ (Sigmaルール 1件)
424 |
425 | ファイル: `Microsoft-Windows-TerminalServices-LocalSessionManager%4Operational.evtx`
426 |
427 | デフォルトの設定: `有効。1 MB`
428 |
429 | リバースプロキシツールであるngrokが、ファイアウォールを迂回するためにローカルRDPポートに通信を転送した場合に検出します。
430 |
431 | リンク: [Bypassing Network Restrictions Through RDP Tunneling](https://www.mandiant.com/resources/blog/bypassing-network-restrictions-through-rdp-tunneling)
432 |
433 | ## TaskScheduler Operationalログ (Sigmaルール 1件)
434 |
435 | ファイル: `Microsoft-Windows-TaskScheduler%4Operational.evtx`
436 |
437 | デフォルトの設定: `無効。1 MB`
438 |
439 | 攻撃者は、しばしば永続化や横展開するためにタスクを悪用するので、このログを有効にした方が良いです。
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
Yamato Security's Windows Event Log Configuration Guide For DFIR And Threat Hunting
6 | [
English ] | [
日本語]
7 |
9 |
10 | This is yet another guide on properly configuring and monitoring Windows event logs with an emphasis on logging for [sigma](https://github.com/SigmaHQ/sigma) rules.
11 |
12 | > This is a work in progress, so check back please periodically for updates.
13 |
14 | # TLDR
15 |
16 | * You can only use around 10~20% of [sigma](https://github.com/SigmaHQ/sigma) detection rules with the default Windows audit settings.
17 | * Even if a Windows log is enabled, by default, the maximum size for logs is between 1~20 MB so there is a good chance that evidence gets quickly overwritten.
18 | * Enable the proper audit settings with [YamatoSecurityConfigureWinEventLogs.bat](YamatoSecurityConfigureWinEventLogs.bat) or [WELA (Windows Event Log Auditor)](https://github.com/Yamato-Security/WELA) to use up to around 75% of sigma rules and retain logs for as long as you need them.
19 | - **Warning: make sure you customize the script to your needs and test before using in production!**
20 | * Install [sysmon](https://learn.microsoft.com/en-us/sysinternals/downloads/sysmon) to get full coverage. (**Highly recommended!**)
21 |
22 | # Companion Projects
23 |
24 | * [Hayabusa](https://github.com/Yamato-Security/hayabusa) - sigma-based threat hunting and fast forensics timeline generator for Windows event logs.
25 | * [Hayabusa Rules](https://github.com/Yamato-Security/hayabusa-rules) - detection rules for hayabusa.
26 | * [Hayabusa Sample EVTXs](https://github.com/Yamato-Security/hayabusa-sample-evtx) - Sample evtx files to use for testing hayabusa/sigma detection rules.
27 | * [Takajo](https://github.com/Yamato-Security/takajo) - Analyzer for hayabusa results.
28 | * [WELA (Windows Event Log Auditor)](https://github.com/Yamato-Security/WELA) - A tool for auditing Windows event log settings.
29 |
30 | # Table of Contents
31 |
32 | - [TLDR](#tldr)
33 | - [Companion Projects](#companion-projects)
34 | - [Table of Contents](#table-of-contents)
35 | - [Author](#author)
36 | - [Contributors](#contributors)
37 | - [Acknowledgements](#acknowledgements)
38 | - [Problems with the default Windows log settings](#problems-with-the-default-windows-log-settings)
39 | - [Warning: Make changes to your systems at your own risk!](#warning-make-changes-to-your-systems-at-your-own-risk)
40 | - [Important Windows event logs](#important-windows-event-logs)
41 | - [Sigma's top log sources](#sigmas-top-log-sources)
42 | - [Top sigma log sources](#top-sigma-log-sources)
43 | - [Top Security Event IDs](#top-security-event-ids)
44 | - [Increasing the maximum file size](#increasing-the-maximum-file-size)
45 | - [Option 1: Manually through Event Viewer](#option-1-manually-through-event-viewer)
46 | - [Option 2: Windows built-in tool](#option-2-windows-built-in-tool)
47 | - [Option 3: PowerShell](#option-3-powershell)
48 | - [Option 4: Group Policy](#option-4-group-policy)
49 | - [Configuration script](#configuration-script)
50 | - [Configuring log settings](#configuring-log-settings)
51 | - [Sysmon log (1382 sigma rules)](#sysmon-log-1382-sigma-rules)
52 | - [Security log (1045 sigma rules (903 process creation rules + 142 other rules))](#security-log-1045-sigma-rules-903-process-creation-rules--142-other-rules)
53 | - [Powershell logs (175 sigma rules)](#powershell-logs-175-sigma-rules)
54 | - [Module logging (30 sigma rules)](#module-logging-30-sigma-rules)
55 | - [Enabling module logging](#enabling-module-logging)
56 | - [Option 1: Enabling through group policy](#option-1-enabling-through-group-policy)
57 | - [Option 2: Enabling through the registry](#option-2-enabling-through-the-registry)
58 | - [Script Block Logging (134 sigma rules)](#script-block-logging-134-sigma-rules)
59 | - [Enabling Script Block logging](#enabling-script-block-logging)
60 | - [Option 1: Enabling through group policy](#option-1-enabling-through-group-policy-1)
61 | - [Option 2: Enabling through the registry](#option-2-enabling-through-the-registry-1)
62 | - [Transcription logging](#transcription-logging)
63 | - [Enabling Transcription logging](#enabling-transcription-logging)
64 | - [Option 1: Enabling through group policy](#option-1-enabling-through-group-policy-2)
65 | - [Option 2: Enabling through the registry](#option-2-enabling-through-the-registry-2)
66 | - [References](#references)
67 | - [System log (55 sigma rules)](#system-log-55-sigma-rules)
68 | - [Application log (16 sigma rules)](#application-log-16-sigma-rules)
69 | - [Windows Defender Operational log (10 sigma rules)](#windows-defender-operational-log-10-sigma-rules)
70 | - [Bits-Client Operational log (6 sigma rules)](#bits-client-operational-log-6-sigma-rules)
71 | - [Firewall log (6 sigma rules)](#firewall-log-6-sigma-rules)
72 | - [NTLM Operational log (3 sigma rules)](#ntlm-operational-log-3-sigma-rules)
73 | - [Security-Mitigations KernelMode and UserMode logs (2 sigma rules)](#security-mitigations-kernelmode-and-usermode-logs--2-sigma-rules)
74 | - [PrintService logs (2 sigma rules)](#printservice-logs-2-sigma-rules)
75 | - [Admin (1 sigma rule)](#admin-1-sigma-rule)
76 | - [Operational (1 sigma rule)](#operational-1-sigma-rule)
77 | - [SMBClient Security log (2 sigma rules)](#smbclient-security-log-2-sigma-rules)
78 | - [AppLocker logs (1 sigma rule)](#applocker-logs-1-sigma-rule)
79 | - [CodeIntegrity Operational log (1 sigma rule)](#codeintegrity-operational-log-1-sigma-rule)
80 | - [Diagnosis-Scripted Operational log (1 sigma rule)](#diagnosis-scripted-operational-log-1-sigma-rule)
81 | - [DriverFrameworks-UserMode Operational log (1 sigma rule)](#driverframeworks-usermode-operational-log--1-sigma-rule)
82 | - [WMI-Activity Operational log (1 sigma rule)](#wmi-activity-operational-log--1-sigma-rule)
83 | - [TerminalServices-LocalSessionManager Operational log (1 sigma rule)](#terminalservices-localsessionmanager-operational-log--1-sigma-rule)
84 | - [TaskScheduler Operational log (1 sigma rule)](#taskscheduler-operational-log--1-sigma-rule)
85 |
86 | # Author
87 |
88 | Zach Mathis ([@yamatosecurity](https://twitter.com/yamatosecurity)). As I do more research and testing, I plan on periodically updating this as there is much room for improvement (both in the documentation as well as in creating more detection rules.) PRs are welcome and will gladly add you as a contributor. If you find any errors in this documentation, please let me know and I will fix them as soon as possible.
89 |
90 | If you find any of this useful, please give a star on GitHub as it will probably help motivate me to continue updating this.
91 |
92 | # Contributors
93 |
94 | * DustInDark (hitenkoku): Japanese translation fixes.
95 | * Fukusuke Takahashi (fukusuket): Japanese translations and fixes.
96 | * LasseKrache: Pointing out a bug in the batch script.
97 |
98 | # Acknowledgements
99 |
100 | Most of the information comes from Microsoft's [Advanced security auditing FAQ](https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/advanced-security-auditing-faq), [sigma](https://github.com/SigmaHQ/sigma) rules, the [ACSC Event Logging Guide](https://www.cyber.gov.au/acsc/view-all-content/publications/windows-event-logging-and-forwarding) and my own research/testing. I would like to thank the [sigma community](https://github.com/SigmaHQ/sigma/graphs/contributors) in particular for making threat detection open source and free for the benefit of all of the defenders out there.
101 |
102 | # Problems with the default Windows log settings
103 |
104 | By default, Windows will not log many events necessary for detecting malicious activity and performing forensics investigations.
105 | Also, the default maxium size for event files is only 20 MB for the classic event logs (`Security`, `System`, `Application`), 15 MB for PowrShell and a mere 1 MB for almost all of the other logs so there is a good chance that evidence is overwritten over time.
106 | A simple [batch script](YamatoSecurityConfigureWinEventLogs.bat) in this repository have been provided to let systems administrators easily configure their Windows machines so that they will have the logs that they need when an incident occurs. For large networks, you probably want to use this document as a reference and configure your endpoints with Group Policy and/or InTune.
107 |
108 | # Warning: Make changes to your systems at your own risk!
109 |
110 | I highly recommend to improve the default Windows event logging settings and try my best to provide the most accurate information. However, I do not take any responsibility for any adverse effects of enabling too much logging or the accuracy of anything in this repository.
111 | It is your responsibility to understand and test out any changes you make to your systems on test machines before rolling out to production.
112 | I recommend turning on as much logging as possible on test machines that mimic your environment for at least a week and then confirm if there are any events that are generating too much noise or if there are events that you want but are not being generated.
113 |
114 | You can view the total number and percent of Event IDs in an `evtx` file with [Hayabusa](https://github.com/Yamato-Security/hayabusa)'s event ID metrics command.
115 |
116 | Example: `hayabusa.exe eid-metrics -f path/to/Security.evtx`
117 |
118 | # Important Windows event logs
119 |
120 | 1. The most important event log to turn on is probably `Process Creation` which tracks what processes are run on a system.
121 | Currently, about half of [Sigma](https://github.com/SigmaHQ/sigma)'s detection rules rely on this event.
122 | This can be accomplished by installing Sysmon (Event ID `1`) or enabling the built-in Security log Event ID `4688`.
123 | `Sysmon 1` will provide detailed information such as hashes and metadata of the executable so is ideal but in the case that Sysmon cannot be installed it is possible use built-in `Security 4688` logs. However, it is important that command line logging is also enabled as many detection rules rely on this. Unfortunately `Security 4688` does not provide as detailed information as the Sysmon process creation logs, so not all `Process Creation` rules work with `Security 4688`.
124 | 2. The second most important event log is a properly tuned Security log.
125 | 3. The third most important are probably PowerShell Module logging and ScriptBlock logging as attackers will often abuse PowerShell.
126 | 4. The forth are probably all of the other Sysmon events.
127 | 5. After these, there are many other logs under the "Application and Services Logs" folder that are also very important: AppLocker, Bits-Client, NTLM, PowerShell, PrintService, Security-Mitigations, Windows Defender, Windows Firewall With Advanced Security, WMI-Activity, etc...
128 |
129 | ## Sigma's top log sources
130 |
131 | 
132 |
133 | Approximately only 10~20% of sigma rules can be used with the default Windows audit settings!
134 |
135 | ### Top sigma log sources
136 |
137 | 
138 |
139 | ### Top Security Event IDs
140 |
141 | 
142 |
143 | # Increasing the maximum file size
144 |
145 | ## Option 1: Manually through Event Viewer
146 |
147 | This is not practical to do at scale, but the easiest way to enable/disable logs and check and/or configure their maximum file size is by right-clicking on the log in Event Viewer and opening up `Properties`.
148 |
149 | ## Option 2: Windows built-in tool
150 |
151 | You can use the built-in `wevtutil` command.
152 |
153 | Example: `wevtutil sl Security /ms:1073741824` to increase the maximum file size for the Security log to 1 GB.
154 |
155 | ## Option 3: PowerShell
156 |
157 | Example:
158 | ```powershell
159 | $sysmon = Get-WinEvent -ListLog Microsoft-Windows-Sysmon/Operational
160 | $sysmon.MaximumSizeInBytes = 2048000000 #2GB
161 | $sysmon.SaveChanges()
162 | ```
163 |
164 | ## Option 4: Group Policy
165 |
166 | It is straightforward to increase the maximum file size for the classic event logs such as `Security`, `System`, and `Application`, however, unfortunately you need to install Administrative Templates and/or directly modify the registry in order to change the maximum file size for the other logs. It may just be easier to increase the file size with a batch or PowerShell script on startup.
167 |
168 | # Configuration script
169 |
170 | A script to increase the maximum file size and enable the proper logs has been provided here: [YamatoSecurityConfigureWinEventLogs.bat](YamatoSecurityConfigureWinEventLogs.bat)
171 |
172 | # Configuring log settings
173 |
174 | ## Sysmon log (1382 sigma rules)
175 |
176 | File: `Microsoft-Windows-Sysmon%4Operational.evtx`
177 |
178 | Default settings: `Not installed`
179 |
180 | Installing and configuring sysmon is the single best thing you can do to increase your visibility on Windows endpoints but it will require planning, testing and maintenance.
181 | This is a big topic in itself so it is out of scope of this document at the moment.
182 | Please check out the following resources:
183 | * [TrustedSec Sysmon Community Guide](https://github.com/trustedsec/SysmonCommunityGuide)
184 | * [Sysmon Modular](https://github.com/olafhartong/sysmon-modular)
185 | * [Florian Roth's updated fork of the Swift On Security's sysmon config file](https://github.com/Neo23x0/sysmon-config)
186 | * [Ion-storm's updated fork of the Swift On Security's sysmon config file](https://github.com/ion-storm/sysmon-config)
187 | * [Cyb3rWard0g's sysmon config file](https://github.com/OTRF/Blacksmith/blob/master/resources/configs/sysmon/sysmon.xml)
188 |
189 | ## Security log (1045 sigma rules (903 process creation rules + 142 other rules))
190 |
191 | File: `Security.evtx`
192 |
193 | Default settings: `Partially enabled`
194 |
195 | The Security log is the most complex to configure so I have created a seperate document for it: [ConfiguringSecurityLogAuditPolicies.md](ConfiguringSecurityLogAuditPolicies.md)
196 |
197 | ## Powershell logs (175 sigma rules)
198 |
199 | File: `Microsoft-Windows-PowerShell%4Operational.evtx`
200 |
201 | ### Module logging (30 sigma rules)
202 |
203 | Turning on module logging will enable event ID `4103`.
204 | Module logging has the advantage that it can run on older OSes and versions of PowerShell: PowerShell 3.0 (Win 7+).
205 | Another benefit is that it logs both the PowerShell command executed as well as the results.
206 | The disadvantage is that it will create an extremely high number of events.
207 | For example, if an attacker runs Mimikatz, it will create 7 MB of logs with over 2000 events!
208 |
209 | #### Enabling module logging
210 |
211 | Default settings: `No Auditing`
212 |
213 | ##### Option 1: Enabling through group policy
214 | In the Group Policy editor (`gpedit.msc`), open `Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell` and enable `Turn on Module Logging`.
215 | In the `Options` pane, click the `Show...` button to configure what modules to log.
216 | Enter `*` in the `Value` textbox to record all modules.
217 |
218 | ##### Option 2: Enabling through the registry
219 | ```
220 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ModuleLogging → EnableModuleLogging = 1
221 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames → * = *
222 | ```
223 |
224 | ### Script Block Logging (134 sigma rules)
225 |
226 | Default settings: `On Win 10/2016+, if a PowerShell script is flagged as suspicious by AMSI, it will be logged with a level of Warning.`
227 |
228 | Turning on Script Block logging will enable event ID `4104`. If you enable `Log script block invocation start / stop events`, EID `4105` and `4106` will also be enabled, however, this is not recommended as it will just create noise.
229 | Script Block logging is supported by default in PowerShell 5.0+ (Win 10+), however you can enable this on older OSes (Win 7+) if you install .NET 4.5 and WMF 4.0+.
230 | Unfortunately, the maximum size of a single Windows event log is 32 KB so any PowerShell scripts greater than this will be fragmented in 32 KB sized blocks.
231 | If you have the original `PowerShell Operational.evtx` file, you can use the [block-parser](https://github.com/matthewdunwoody/block-parser) tool to un-fragment these logs into a single easily readable text file.
232 | One good thing about Script Block logging is that even if a malicious script is obfuscated with XOR, Base 64, ROT13, etc... the decoded script will be logged making analysis much easier.
233 | The logs are more reasonable to work with than module logging as if an attacker runs Mimikatz, only 5 MB and 100 events will generated compared to the 7 MB and over 2000 events.
234 | However, the output of the commands are not recorded with Script Block logging.
235 |
236 | #### Enabling Script Block logging
237 |
238 | #### Option 1: Enabling through group policy
239 |
240 | In the Group Policy editor, open `Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell` and enable `Turn on PowerShell Script Block Logging`.
241 |
242 | #### Option 2: Enabling through the registry
243 |
244 | `HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging → EnableScriptBlockLogging = 1`
245 |
246 | ### Transcription logging
247 |
248 | Default settings: `No Auditing`
249 |
250 | It is possible to also save PowerShell logs to text files on the local computer with transcription logs.
251 | While an attacker can usually easily delete the transcription logs for anti-forensics, there may be scenarios where the attacker clears all of the event logs but does not search for transcription logs to delete.
252 | Therefore, it is recommended to also enable transcription logs if possible.
253 | By default, they are saved to the user's documents folder.
254 | Ideally transcript logs should be saved to a write-only network file share, however, this may be difficult to implement in practice.
255 | A benefit of transcription logs is they include the timestamp and metadata for each command and are very storage efficient with less than 6 KB for Mimikatz execution.
256 | The downside is that the transcription logs only record what appears in the PowerShell terminal.
257 |
258 | #### Enabling Transcription logging
259 |
260 | ##### Option 1: Enabling through group policy
261 |
262 | In the Group Policy editor, open `Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell` and enable `Turn on PowerShell Transcription`.
263 | Then, specify the output directory.
264 |
265 | ##### Option 2: Enabling through the registry
266 | ```
267 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\Transcription → EnableTranscripting = 1
268 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\Transcription → EnableInvocationHeader = 1
269 | HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\PowerShell\Transcription → OutputDirectory = “” (Enter path. Empty = default)
270 | ```
271 |
272 | ### References
273 |
274 | * [Mandiant Blog: Greater Visibility Through PowerShell Logging](https://www.mandiant.com/resources/blog/greater-visibilityt)
275 |
276 | ## System log (55 sigma rules)
277 |
278 | File: `System.evtx`
279 |
280 | Default settings: `Enabled. 20 MB`
281 |
282 | Recommended settings: `Enabled. 128 MB+`
283 |
284 | Malware will often install services for persistence, local privilege esclation, etc... which can be found in this log.
285 | It is also possible to detect various vulnerabilities being exploited here.
286 |
287 | > **Note: One thing to watch out specific to the System log is that parameters in fields are sometimes translated to the local language so signatures that use only English may not detect on non-English systems. For example, on an English system in the parameters for EID 7045, it will record `Enabled` while in Japanese it might record `有効`.**
288 |
289 | > **Note: Just like the `Application` log, multiple providers will log to the same event ID so you may need to filter on provider name as well as the channel. An example is event ID `1` which gets used by various providers for different events.**
290 |
291 | Important Event IDs:
292 |
293 | | Event ID | Description | Sigma Rules | Hayabusa Rules | Level | Notes |
294 | | :---: | :---: | :---: | :---: | :---: | :---: |
295 | | 1 | System Sleep/Hibernation | 0 | Not Yet. | Info | Provider: `Power-Troubleshooter` |
296 | | 1 | System Time Changed | 0 | Not Yet. | Info | Provider: `Kernel-General` |
297 | | 12 | OS Startup | 0 | Not Yet. | Info | |
298 | | 13 | OS Shutdown | 0 | Not Yet. | Info | |
299 | | 16 | Registry Hive Access History Cleared | 2 | Not Yet. | High~Crit | Password dumpers may clear access history after dumping passwords hashes from the SAM registry key. This also happens normally though so need to filter out FPs. |
300 | | 55 | NTFS Filesystem Corrupted | 1 | No | High | Can detect attacks against NTFS vulnerabilities. |
301 | | 104 | System Event Log Cleared | 1 | Yes | Med | |
302 | | 6005 | Event Log Service Started | 0 | Yes | Info | |
303 | | 6006 | Event Log Service Stopped | 0 | Yes | Info | |
304 | | 6008 | Unexpected Shutdown | 0 | Yes | Info | |
305 | | 6038 | NTLMv1 Was Used | 1 | No | Low | |
306 | | 7031 | Service Crashed | 0 | Yes | Low | |
307 | | 7034 | Service Crashed | 0 | Yes | Low | |
308 | | 7036 | Service Started/Stopped | 2 | Yes | Info~High | Can be used to detect someone stopping Defender, etc... |
309 | | 7040 | Service Startup Type Changed | 0 | Yes | Info | Can indicate an attacker disabled a service. |
310 | | 7045 | Service Installation | 37 | Yes | Info~Crit | This is the most important System event ID as malware often installs itself as a service or abuses services. |
311 | | 20001 | New PNP Device | 0 | Yes | Info~? | Level will depend on if USB devices are allowed or not. Logs only the first time a device has been plugged in. Non-USB PNP device events are very noisy so should probably be filtered out. |
312 |
313 | ## Application log (16 sigma rules)
314 |
315 | This log is mostly noise but you may be able to find some important evidence here.
316 | Some 3rd-party anti-virus software will log to here.
317 | One thing to be careful about with the Application log is that different vendors will use the same event IDs for different events so you should also filter on not just Event IDs but Provider Names as well.
318 |
319 | File: `Application.evtx`
320 |
321 | Default settings: `Enabled. 20 MB`
322 |
323 | Recommended settings: `Enabled. 128 MB+`
324 |
325 | Important Event IDs:
326 |
327 | | Event ID | Provider | Description | Sigma Rules | Hayabusa Rules | Level | Notes |
328 | | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
329 | | 1 | `Audit-CVE`, `Microsoft-Windows-Audit-CVE` | Known Vulnerability (CVE) Exploit Attempt | 1 | No | Critical | Detects events generated by user-mode applications when they call the CveEventWrite API when a known vulnerability is trying to be exploited. MS started using this log in 2020/01 with CVE-2020-0601 (a Windows CryptoAPI vulnerability). Unfortunately, that is about the only instance of CVEs being written to this log. |
330 | | 325 | `ESENT` | ESE DB Created | 2 | No | Info~Crit | Detects when a process creates an ESE database. This is used by a variety of things such as for Exchange, AD, Certificate Services, SRUM, etc... The most important ESE DB for security is NTDS.dit, the file of all domain users' password hashes located on domain controllers. There are two sigma rules to detect dumping of NTDS.dit, however, it may be a false positive if an administrator uses ntdsutil for backups or when shadow copies are created. |
331 | | 326 | `ESENT` | ESE DB Attached | 1 | No | Info~Crit | May be able to detect access to NTDS.dit. |
332 | | 1000, 1001 | `Application Error`, `Windows Error Reporting` | Application Error | 1 | No | Info~High | |
333 | | 1034, 11724 | `MsiInstaller` | Application Uninstalled | 1 | No | Info~Low | |
334 | | 1040 | `MsiInstaller` | Application Installation | 1 | No | Info~Med | |
335 | | 33205 | `MSSQLSERVER` | SQL Audit Event | 6 | No | Info~High | Can detect MSSQL backdoors, SQL/command injection, etc... |
336 |
337 |
338 | ## Windows Defender Operational log (10 sigma rules)
339 |
340 | File: `Microsoft-Windows-Windows Defender%4Operational.evtx`
341 |
342 | Default settings: `Enabled. 1 MB`
343 |
344 | Recommended settings: `Enabled. 128 MB+`
345 |
346 | You can detect not only Windows Defender alerts (which are important to monitor), but also exclusions being added, tamper protection being disabled, history deleted, etc...
347 |
348 | ## Bits-Client Operational log (6 sigma rules)
349 |
350 | File: `Microsoft-Windows-Bits-Client%4Operational.evtx`
351 |
352 | Default settings: `Enabled. 1 MB`
353 |
354 | Recommended settings: `Enabled. 128 MB+`
355 |
356 | Bitsadmin.exe is a popular [lolbin](https://lolbas-project.github.io/lolbas/Binaries/Bitsadmin/) that attackers will abuse for downloading and executing malware.
357 | You may find evidence of that in this log, although there will be a lot of false positives to watch out for.
358 |
359 | ## Firewall log (6 sigma rules)
360 |
361 | File: `Microsoft-Windows-Windows Firewall With Advanced Security%4Firewall.evtx`
362 |
363 | Default settings: `Enabled? 1 MB`
364 |
365 | Recommended settings: `Enabled. 256 MB+`
366 |
367 | You can find evidence of firewall rules being added/modified/deleted here.
368 | Malware will often add firewall rules to make sure they can communicate with their C2 server, add proxy rules for lateral movement, etc...
369 |
370 | ## NTLM Operational log (3 sigma rules)
371 |
372 | File: `Microsoft-Windows-NTLM%4Operational.evtx`
373 |
374 | Default settings: `Enabled but Auditing is disabled. 1 MB`
375 |
376 | This log is recommended to enable if you want to disable NTLM authentication.
377 | Disabling NTLM will most likely break some communication, so you can monitor this log on the DCs and other servers to see who is still using NTLM and disable NTLM gradually starting with those users before disabling it globally.
378 | It is possible to detect NTLM being used for incoming connections in logon events such as 4624 but you need to enable this log if you want to monitor who is making outgoing NTLM connections.
379 |
380 | To enable auditing, in Group Policy open `Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options` and configure the proper various `Network security: Restrict NTLM:` settings.
381 |
382 | Reference: [Farewell NTLM](https://www.scip.ch/en/?labs.20210909)
383 |
384 | ## Security-Mitigations KernelMode and UserMode logs (2 sigma rules)
385 |
386 | Files: `Microsoft-Windows-Security-Mitigations%4KernelMode.evtx`, `Microsoft-Windows-Security-Mitigations%4UserMode.evtx`
387 |
388 | Default settings: `Enabled. 1 MB`
389 |
390 | Recommended settings: `Enabled. 128 MB+`
391 |
392 | At the moment there are only 2 sigma rules for these logs but you should probably be collecting and monitoring all of the Exploit Protection, Network Protection, Controlled Folder Access and Attack Surface Reduction logs (About 40+ Event IDs).
393 |
394 | Unfortunately the Attack Surface Reduction logs (previously WDEG(Windows Defender Exploit Guard) and EMET) are spread across multiple logs and require complex XML queries to search them.
395 |
396 | Details: [Understand and use attack surface reduction capabilities](https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/overview-attack-surface-reduction?view=o365-worldwide)
397 |
398 | ## PrintService logs (2 sigma rules)
399 |
400 | It is recommended to enable the Operational log as well to detect Print Spooler attackers. (Ex: PrintNightmare, etc...)
401 |
402 | ### Admin (1 sigma rule)
403 |
404 | File: `Microsoft-Windows-PrintService%4Admin.evtx`
405 |
406 | Default settings: `Enabled. 1 MB`
407 |
408 | Recommended settings: `Enabled. 128 MB+`
409 |
410 | ### Operational (1 sigma rule)
411 |
412 | File: `Microsoft-Windows-PrintService%4Operational.evtx`
413 |
414 | Default settings: `Disabled. 1 MB`
415 |
416 | Recommended settings: `Enabled. 128 MB+`
417 |
418 | ## SMBClient Security log (2 sigma rules)
419 |
420 | File: `Microsoft-Windows-SmbClient%4Security.evtx`
421 |
422 | Default settings: `Enabled. 8 MB`
423 |
424 | Recommended settings: `Enabled. 128 MB+`
425 |
426 | Used to attempt to detect PrintNightmare (Suspicious Rejected SMB Guest Logon From IP) and users mounting hidden shares.
427 |
428 | ## AppLocker logs (1 sigma rule)
429 |
430 | Files: `Microsoft-Windows-AppLocker%4MSI and Script.evtx`, `Microsoft-Windows-AppLocker%4EXE and DLL.evtx`, `Microsoft-Windows-AppLocker%4Packaged app-Deployment.evtx`, `Microsoft-Windows-AppLocker%4Packaged app-Execution.evtx`
431 |
432 | Default settings: `Enabled if AppLocker is enabled? 1 MB`
433 |
434 | Recommended settings: `Enabled. 256 MB+`
435 |
436 | This is important to make sure is enabled and monitored if you are using AppLocker.
437 |
438 | ## CodeIntegrity Operational log (1 sigma rule)
439 |
440 | File: `Microsoft-Windows-CodeIntegrity%4Operational.evtx`
441 |
442 | Default settings: `Enabled. 1 MB`
443 |
444 | Recommended settings: `Enabled. 128 MB+`
445 |
446 | Check this log to detect driver load events that get blocked by Windows code integrity checks, which may indicate a malicious driver that faild to load.
447 |
448 | ## Diagnosis-Scripted Operational log (1 sigma rule)
449 |
450 | File: `Microsoft-Windows-Diagnosis-Scripted%4Operational.evtx`
451 |
452 | Default settings: `Enabled. 1 MB`
453 |
454 | Recommended settings: `Enabled. 128 MB+`
455 |
456 | Evidence of diagcab packages being used for exploitation may be found here.
457 |
458 | ## DriverFrameworks-UserMode Operational log (1 sigma rule)
459 |
460 | Files: `Microsoft-Windows-DriverFrameworks-UserMode%4Operational.evtx`
461 |
462 | Default settings: `No Auditing. 1 MB`
463 |
464 | Recommended settings: `Enabled. 128 MB+`
465 |
466 | Detects plugged in USB devices.
467 |
468 | ## WMI-Activity Operational log (1 sigma rule)
469 |
470 | File: `Microsoft-Windows-WMI-Activity%4Operational.evtx`
471 |
472 | Default settings: `Enabled on Win10/2016+. 1 MB`
473 |
474 | Recommended settings: `Enabled. 128 MB+`
475 |
476 | This is important to monitor as attackers will often exploit WMI for persistence and lateral movement.
477 |
478 | ## TerminalServices-LocalSessionManager Operational log (1 sigma rule)
479 |
480 | File: `Microsoft-Windows-TerminalServices-LocalSessionManager%4Operational.evtx`
481 |
482 | Default settings: `Enabled. 1 MB`
483 |
484 | Recommended settings: `Enabled. 128 MB+`
485 |
486 | Detects when ngrok, a reverse proxy tool, forwards traffic to the local RDP port to bypass firewalls.
487 |
488 | Link: [Bypassing Network Restrictions Through RDP Tunneling](https://www.mandiant.com/resources/blog/bypassing-network-restrictions-through-rdp-tunneling)
489 |
490 | ## TaskScheduler Operational log (1 sigma rule)
491 |
492 | File: `Microsoft-Windows-TaskScheduler%4Operational.evtx`
493 |
494 | Default settings: `Disabled. 1 MB`
495 |
496 | Recommended settings: `Enabled. 128 MB+`
497 |
498 | Attackers will often abuse tasks for persistence and lateral movement so this should be enabled.
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 |
635 | Copyright (C)
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Copyright (C)
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/ConfiguringSecurityLogAuditPolicies-Japanese.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Securityログ設定について
7 |
8 | [
English] | [
日本語]
9 |
2 |
3 |
4 |
5 |
6 | Configuring Security Log Audit Settings
7 |
8 | [
English ] | [
日本語]
9 |