Collect the two pre-session RDP logs - #86
Merged
Merged
Conversation
Adds Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational (261, 1149) and Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational (131, 140) as Core channels, 128 MB, kept enabled. Both are on by default at 1 MB and wrap within hours on an exposed host. Event IDs and log locations checked against the providers' own event definitions. Kit additions (no Yamato Y on the Reference page); role presets select them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 41 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository: spydisec/WinLogKit/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From the review of darkoperator/Windows-Auditing-Guide, which relies on these logs for RDP.
Added (Core, all roles, 1 MB -> 128 MB, kept enabled, may be absent)
Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational: 261 (listener received a connection), 1149 (Remote Desktop Services: user authentication succeeded, with user and source address).Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational: 131 (server accepted a new connection from client address), 140 (connection failed because the user name or password is incorrect).Event IDs and which log each lands in were checked with
Get-WinEvent -ListProvideron Windows 11: the darkoperator catalogue files 131/140 under RemoteConnectionManager and describes 140 as a success; both are wrong, and the kit follows the providers. Both logs were confirmed enabled at 1 MB by default.Kit additions (no Yamato "Y" on the Reference page); role presets select them, ASD stays faithful. Reference, Settings catalog and Group Policy pages regenerated (no CSP / template for either log). ATT&CK coverage unchanged (no analytics name these logs; Core + HighVolume still 283). Disk check on this machine: 25 kit logs, 2.6 GB growth headroom.
Checks: Pester 70/70 on PowerShell 7 and 5.1; PSScriptAnalyzer clean for the kit;
mkdocs build --strictpasses.🤖 Generated with Claude Code