Some ATT&CK techniques are mapped to the same PBAs. For example, T1053 (Scheduled task) and T1168 (Local job scheduling) are both mapped to the "Job scheduling" PBA. The way our PBA telemetry is processed in

causes issues in such cases which in turn leads to a buggy ATT&CK report.

Example (reported by @ilija-lazoroski):

1. There were no Windows machines in the network.
2. Crontab does not exist on Windows.

Tasks

• Fix it! (0.75d)