Hello, Diego
This is due to the fact that the rule you are referencing, 18107, checks for event ids that do not include the ones that you are looking for, so those ids would not trigger this rule in the first place and so your new custom rules would also never trigger (since they are child rules of 18104).
<rule id="18107" level="3">
<if_sid>18104</if_sid>
<id>^528$|^540$|^673$|^4624$|^4769$</id>
<description>Windows Logon Success.</description>
<mitre>
<id>T1078</id>
</mitre>
<group>authentication_success,pci_dss_10.2.5,gpg13_7.1,gpg13_7.2,gdpr_IV_32.2,hipaa_164.312.b,nist_800_53_AU.14,nist_800_53_AC.7,tsc_CC6.8,tsc_CC7.2,tsc_CC7.3,</group>
</rule>
The solution for this is to reference rule 18107's parent instead, so in your custom rules, replace <if_sid>18107</if_sid> with <if_sid>18104</if_sid> and they should now work as expected.