splunk / splunk/security_content
[BUG] ESCU CS fields LogonType and TargetUserName
@josehelps is already working on this.
Since Jan 23, 2024.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 494
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 25
Description
Describe the bug
There are some CS that are not using the correct field name using the last version of the "Splunk Add-on for Microsoft Windows".
Expected behavior
Some CS need to be change to the correct field names.
Field Original Name > New Name
LogonType > Logon_Type
TargetUserName > Target_User_Name > user
https://github.com/search?q=repo%3Asplunk%2Fsecurity_content+LogonType&type=code
https://github.com/search?q=repo%3Asplunk%2Fsecurity_content+TargetUserName&type=code
https://github.com/search?q=repo%3Asplunk%2Fsecurity_content+Target_User_Name&type=code
App Version:
Splunk Version 9.0.4.1
ES Content Updates 4.12.0
Enterprise Security 7.1.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.