Skip to content

Conversation

tccontre
Copy link
Contributor

@tccontre tccontre commented Aug 14, 2025

New

  • windows_certutil_certificate_addition_in_temp_path.yml
  • windows_certutil_root_certificate_addition.yml
  • windows_firewallapi_dll_load_from_temp.yml
  • windows_firewallapi_dll_load_from_unusual_path.yml
  • windows_set_private_network_profile_via_registry.yml

analytic story

    new file:   stories/secret_blizzard.yml

What does this PR have in it? Screenshots are worth 1000 words 😄

Checklist

  • Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
  • CI/CD jobs passed ✔️
  • Validated SPL logic.
  • Validated tags, description, and how to implement.
  • Verified references match analytic.
  • Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

  • If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
  • Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.
  • Updates to existing lookup files can be tricky, because of how Splunk handles application updates and the differences between existing lookup files being updated vs new lookups. You can read more here but the short version is that any changes to lookup files need to bump the the date and version in the associated YAML file.

@tccontre tccontre added the WIP DO NOT MERGE Work in Progress label Aug 14, 2025
@tccontre tccontre removed the WIP DO NOT MERGE Work in Progress label Aug 20, 2025
Comment on lines +11 to +13
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime values(Processes.process)
as process max(_time) as lastTime from datamodel=Endpoint.Processes
where `process_certutil` Processes.process=*-addstore* Processes.process=*root*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also covered by Attempt To Add Certificate To Untrusted Store. If you say that the store name root is unique and must be monitored then you can add this analytic but you have to take care of the description and explaining why it is important to monitor it.

Comment on lines +11 to +12
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Endpoint.Registry
WHERE (Registry.registry_value_name= "Category" Registry.registry_path = "*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\NetworkList\\Profiles*") Registry.registry_value_data = 0x00000000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know if the adversary used reg or PowerShell in this case? Because perhaps the default behavior of this is that svchost make that change but an attacker might use a tool.

Of course a GUI could still be used but just thinking out loud to try and make this more accurate.

Perhaps a VT search for this registry change would bring good results.

@nasbench nasbench self-assigned this Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants