Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cherry-pick #18526 to 7.x: [Winlogbeat] Add Powershell logging module #18819

Merged
merged 1 commit into from
May 28, 2020
Merged

Cherry-pick #18526 to 7.x: [Winlogbeat] Add Powershell logging module #18819

merged 1 commit into from
May 28, 2020

Conversation

marc-gr
Copy link
Contributor

@marc-gr marc-gr commented May 28, 2020 •
edited by zube bot
Loading

Cherry-pick of PR #18526 to 7.x branch. Original message:

What does this PR do?

Adds PowerShell logging module to winlogbeat.

Why is it important?

Add a new Winlogbeat module to collect logs from PowerShell. This will collect information about the scripts and modules that are being executed.

# The module will process events based on this config.
winlogbeat.event_logs:
  - name: Windows PowerShell
    event_ids: 400, 403, 600, 800

  - name: Microsoft-Windows-PowerShell/Operational
    event_ids: 4103, 4104, 4105, 4106

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Module Checklist

  • Supported versions are documented
  • Supported operating systems are documented (if applicable)
  • Automated checks that all fields are documented
  • Documentation
  • Fields follow ECS and naming conventions
  • Dashboards to show the data

Powershell dashboard

Handle events

  • 400 - This event indicates the start of a PowerShell activity, whether local or remote.
  • 403 - This event records the completion of a PowerShell activity.
  • 600 - indicates that providers such as WSMan start to perform a PowerShell activity on the system, for example, “Provider WSMan Is Started”.
  • 800 - Pipeline execution details
  • 4103 - module logging
  • 4104 - script block logging (first time it runs)
  • 4105 - Command started
  • 4106 - Command completed

Related issues

Closes #16262

@marc-gr
Add winlogbeat powershell module (elastic#18526)
7cae739 
Initial support for event ids: 400, 403, 600, 800, 4103, 4014, 4105, 4106
Add fields documentation
Add powershell module dashboard

Closes elastic#16262

(cherry picked from commit f4019d5)
@marc-gr marc-gr requested a review from a team as a code owner May 28, 2020 14:15
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels May 28, 2020
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #18819 opened]

  • Start Time: 2020-05-28T14:15:53.523+0000

  • Duration: 44 min 40 sec

Test stats 🧪

Test Results
Failed 0
Passed 272
Skipped 1
Total 273

@marc-gr marc-gr merged commit f4e97c5 into elastic:7.x May 28, 2020
@marc-gr marc-gr deleted the backport_18526_7.x branch May 28, 2020 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@leehinman leehinman leehinman approved these changes

Assignees
No one assigned
Labels
backport Winlogbeat
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@marc-gr @elasticmachine @leehinman