mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Branch was auto-updated.
This commit is contained in:
@@ -1,12 +1,18 @@
|
||||
# PR Template for new Detections
|
||||
|
||||
For Authors:
|
||||
- [ ] Make sure that CI/CD [detection-testing and build-and-validate](https://github.com/splunk/security_content/actions) jobs passed ✔️.
|
||||
### Details
|
||||
|
||||
*_what does this PR have in it, screenshots are nice 😄_
|
||||
|
||||
### Author Checklist
|
||||
|
||||
For Reviewers:
|
||||
- [ ] Verify CI/CD jobs have passed without errors.
|
||||
- [ ] Validate SPL logic.
|
||||
- [ ] Validate tags, description, and how to implement.
|
||||
- [ ] Validate name matches `<platform>_<mitre att&ck technique>_<short description>`
|
||||
- [ ] Verify references match analytic.
|
||||
- [ ] Is there an Atomic Test?
|
||||
- [ ] Make sure that CI/CD [detection-testing and build-and-validate](https://github.com/splunk/security_content/actions) jobs passed ✔️
|
||||
- [ ] Is there an Atomic Test? Is GUID on the test file under array: `atomic_test_guid`, [example]()?
|
||||
|
||||
|
||||
### Review Checklist
|
||||
|
||||
- [ ] Validated SPL logic.
|
||||
- [ ] Validated tags, description, and how to implement.
|
||||
- [ ] Verified references match analytic.
|
||||
|
||||
Reference in New Issue
Block a user