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.
Summary
Detecting when an user is being created is important not only because it can be an indicator that the system is compromised and an attacker is trying to increase access to a system/domain but also when legal activities needs to be audited for compliance
There is one detection rule for windows "User Account Creation" that is base on the analysis of process execution and process execution arguments.
This rule is cross-plataform and it is based on ECS event fields (category, type and outcome) and it works well for the standard winlogbeat logs, auditbeat logs and also for custom logs mapped into ECS (example Fortinet's logid 0100032132)