Fix Windows File Path for RTA schtask_escalation

[shashank-elastic]

Pull Request

Issue link(s): Reported in Community Slack

Summary - What I changed

• Add concatenate str to the file_path

How To Test

• Run the RTA with the fix to check it executes with no errors

(venv) PS C:\Users\shashank_suryanaraya\detection-rules> python -m rta -n schtask_escalation
[+] Scheduled Task Privilege Escalation
shashank_suryanaraya @ e2e-release-windows-server-2022 > schtasks.exe /query /tn test-task-rta
ERROR: The system cannot find the file specified.
exit code = 1

shashank_suryanaraya @ e2e-release-windows-server-2022 > schtasks.exe /create /tn test-task-rta /ru system /tr "cmd.exe /c whoami.exe > task.log" /sc onlogon
SUCCESS: The scheduled task "test-task-rta" has successfully been created.

shashank_suryanaraya @ e2e-release-windows-server-2022 > schtasks.exe /run /tn test-task-rta
SUCCESS: Attempted to run the scheduled task "test-task-rta".

task.log
--- NOT FOUND ----

shashank_suryanaraya @ e2e-release-windows-server-2022 > schtasks.exe /delete /tn test-task-rta /f
SUCCESS: The scheduled task "test-task-rta" was successfully deleted.

(venv) PS C:\Users\shashank_suryanaraya\detection-rules>

Checklist

• [x] Added a label for the type of pr: bug, enhancement, schema, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
• [x] Added the meta:rapid-merge label if planning to merge within 24 hours
• [ ] Secret and sensitive material has been managed correctly
• [ ] Automated testing was updated or added to match the most common scenarios
• [ ] Documentation and comments were added for features that require explanation

Contributor checklist

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?

[protectionsmachine]

Bug - Guidelines

These guidelines serve as a reminder set of considerations when addressing a bug in the code.

Documentation and Context

• [ ] Provide detailed documentation (description, screenshots, reproducing the bug, etc.) of the bug if not already documented in an issue.
• [ ] Include additional context or details about the problem.
• [ ] Ensure the fix includes necessary updates to the release documentation and versioning.

Code Standards and Practices

• [ ] Code follows established design patterns within the repo and avoids duplication.
• [ ] Code changes do not introduce new warnings or errors.
• [ ] Variables and functions are well-named and descriptive.
• [ ] Any unnecessary / commented-out code is removed.
• [ ] Ensure that the code is modular and reusable where applicable.
• [ ] Check for proper exception handling and messaging.

Testing

• [ ] New unit tests have been added to cover the bug fix or edge cases.
• [ ] Existing unit tests have been updated to reflect the changes.
• [ ] Provide evidence of testing and detecting the bug fix (e.g., test logs, screenshots).
• [ ] Validate that any rules affected by the bug are correctly updated.
• [ ] Ensure that performance is not negatively impacted by the changes.
• [ ] Verify that any release artifacts are properly generated and tested.

Additional Checks

• [ ] Ensure that the bug fix does not break existing functionality.
• [ ] Review the bug fix with a peer or team member for additional insights.
• [ ] Verify that the bug fix works across all relevant environments (e.g., different OS versions).
• [ ] Confirm that all dependencies are up-to-date and compatible with the changes.